similar to: NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation

Hi, I have built dependent packages of nodejs010 and npm successfully using mock and copy these RPMS to our ISO, anaconada installer fails to install due to dependency errors: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch requires nodejs010-npm(readable-stream) < 2 nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch requires nodejs010-npm(graceful-fs) < 4

On Thu, Sep 1, 2016 at 5:30 PM, <centos-request at centos.org> wrote: > Send CentOS mailing list submissions to > centos at centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos > or, via email, send a message with subject or body 'help' to > centos-request at

Hi, I am trying to built an ISO with nodejs010 packages but when I run the command "repoclosure -a x86_64 -r <local-repository-name>" to check its further dependencies, it is giving unresolved dependencies error. Example: package: nodejs010-node-gyp-3.2.0-2.el7.centos.noarch from Harman (it's a local repo name) unresolved deps: npm(minimatch) < 0:4

I am pleased to announce the immediate availability of version 0.10 of the NodeJS on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install nodejs010 $ scl enable

I am pleased to announce the immediate availability of version 0.10 of the NodeJS on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install nodejs010 $ scl enable nodejs010

Hi, (This is happening on CentOS 6) during a machine's kickstart I install several yum repositories which are contained in an RPM. During the %post phase I install an RPM which has a dependency to nodejs. That package with all of its dependencies can be found in EPEL. On the other hand I have the Softwarecollections repository, which also contains nodejs with the same version. Now nodejs

Hello, ?With SCL and epel repositories enabled, some dependencies for the package name 'nodejs' get satisfied with libs from SCL which are placed in paths that are not part of my user's environment. Is there a method to make sure that nodeJS from epel dependencies are only satisfied from epel? For example, the http parser dependency gets satisfied by

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Using ```puppetlabs/apt``` in a puppet provisioner for vagrant. the module is installed in puppet/modules and I''m getting a strange Dependency cycle error. the code in the manifest file: # Run apt-get update when anything beneath /etc/apt/ changes #taken from https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/ exec { "apt-get

(NPM: new pass manager; LPM: legacy pass manager) In a first quick experiment today I compared code-size of the LMP vs. the NMP for the CSiBE benchmark (and some other), and this shows code-size increases with the NPM that would probably be unacceptable for us. So, now I am wondering how/if we need to mitigate this, and have a bunch of questions. As I've noticed quite some activity around

Im using a parameterized class in my site.pp: class development($user) { class{"basenode": user => $user} class{"nodejs": user => $user} include "coffeescript" include "ruby" } This class defines nodejs class that epects a user as input: class nodejs($user) { class {"nodejs::npm": user => $user} $node_ver =

I am pleased to announce the immediate availability of NodeJS in version 4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install rh-nodejs4 $ scl

I am pleased to announce the immediate availability of NodeJS in version 8 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl-rh $ sudo yum install rh-nodejs8 $ scl enable

I am pleased to announce the immediate availability of NodeJS in version 10 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: # 1. Install a package with repository for your system: $ sudo yum install

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

A friend passed along this interesting link: http://incolumitas.com/2016/06/08/typosquatting-package-managers/ about the strategy of using "typosquatting" (packages with very similar names to existing packages) to trick users into downloading/installing packages with malicious code). They made fake trojans (with empty payloads) for Ruby, Python and NodeJS and experimented to see how

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hello LLVM community, I was trying to port a target specific loop transformation pass (HexagonVectorLoopCarriedReusePass) to the New Pass Manager. However, I could not figure out a way to register this pass with opt. I can see that llvm/lib/Passes/PassRegistry.def is the registry for target independent passes. Can anyone point me to an example/API which can help me in registering this pass so

Hi, I'm interested in the sort of pass where you write `-passes=print<pass-name>` and it calls the `print()` function of the pass. I have seen some other passes that can invoke `-passes=print<>` but the implementation seems to be in the wrapper pass for the old pass manager. Thanks, Stefanos Baziotis -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi All, I was following the instructions for installing nodejs version 14. https://github.com/nodesource/distributions First thing was: curl -sL https://rpm.nodesource.com/setup_14.x | bash - After that : yum -y install nodejs ---> Package nodejs.x86_64 2:12.16.2-1nodesource will be installed --> Finished Dependency Resolution You can see its installing the OLD Version 12. not the 14.