Uploaded image for project: 'Help-Coaches-Desk'
  1. Help-Coaches-Desk
  2. HELC-831

FIWARE.Request.Coach.FINODEX.PEP-Proxy-Steelskin deployment with rpm

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Component/s: FINODEX
    • Labels:
      None

      Description

      Hello,

      I am a developer for SAPIN (FINODEX012) and I am experimenting an issue with PEP-Proxy-Steelskin deployment.

      I am developing in a CentOS 6.5 instance the PEP-Proxy-Steelskin, and I am trying to do it according to the documentation found in the repository: https://github.com/telefonicaid/fiware-pep-steelskin <https://github.com/telefonicaid/fiware-pep-steelskin>
      I do not know what the error is, because the script that I should execute is complying about the non existence of npm, but actually after typing “npm -v” it gives me its version (1.4.28).

      So I will tell you what procedure I am following in case I am missing something:

      1) First of all, I install git (yum install git) without errors, and clone the repository in the home directory (git clone https://github.com/telefonicaid/fiware-pep-steelskin <https://github.com/telefonicaid/fiware-pep-steelskin>).
      2) I move into the directory /fiware-pep-proxy/rpm and I change permissions to the create-rpm.sh script.
      3) I install dependencies:
      3.1) yum update
      3.1.1) It ends with an error "xorg-x11-font-utils is needed by ghostscript-fonts-5.50-23.2.el6.noarch” so I install it: yum install xorg-x11-font-utils
      3.1.2) yum update
      3.2) curl -sL https://rpm.nodesource.com/setup <https://rpm.nodesource.com/setup> | bash - and then yum install -y nodejs
      3.2.1) Ends without errors
      3.3) yum install rpm-build
      3.3.1) Ends without errors
      4)I proceed to run the script: ./create-rpm.sh -v 0.7.0 -r c86719e
      4.1) error: entries %changelog must start with *
      4.1.1) I fixed the error because in SPECS/pepProxy.conf below the %changelog line, the next line began with ======, and should be the one that begins with *
      5) Run again the script:
      5.1)error: Failed building dependencies:
      npm is needed to pep-proxy-0.7.0-c86719e.noarch
      5.1.1) This is weird, I have npm installed and updated. So I go again to pepProxy.conf and comment the line BuildRequires: npm
      5.1.2) I think that here might be the problem, but I cannot figure out what might be
      6)Run once again the script:
      6.1) Build succeeded
      7) Going to the directory /RPMS/noarch and executing yum --nogpgcheck localinstall pep-proxy-0.7.0-c86719e.noarch.rpm
      7.1) Error: Package: pep-proxy-0.7.0-c86719e.noarch (/pep-proxy-0.7.0-c86719e.noarch)
      Needs: npm

      I really don’t know how to follow.

      I would appreciate if you could help me here.

      Thanks in advance

      Jose Benítez
      Cofounder Secmotic Innovation S.L.
      http://www.secmotic.com <http://www.secmotic.com/>

      _______________________________________________
      Fiware-finodex-coaching mailing list
      Fiware-finodex-coaching@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-finodex-coaching

      [Created via e-mail received from: =?utf-8?Q?Jose_Ben=C3=ADtez?= <jose@secmotic.com>]

        Issue Links

          Activity

          Hide
          aalonsog Alvaro Alonso added a comment -

          Sorry but I'm not the responsible of that component. My component is pep-proxy (and not PEP-Proxy-Steelskin). It is owned by TID

          Show
          aalonsog Alvaro Alonso added a comment - Sorry but I'm not the responsible of that component. My component is pep-proxy (and not PEP-Proxy-Steelskin). It is owned by TID
          Hide
          fermin Fermín Galán added a comment -

          Daniel Moran (Steelskin main developer but without JIRA account to answer himself) has told me that the problem has been solved. Thus I'm closing this issue.

          Show
          fermin Fermín Galán added a comment - Daniel Moran (Steelskin main developer but without JIRA account to answer himself) has told me that the problem has been solved. Thus I'm closing this issue.

            People

            • Assignee:
              pasquale.vitale Pasquale Vitale
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: