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 nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_6 http-parser-2.0-4.20121128gitcd01361.el6.x86_64 : HTTP request/response parser for C Repo : epel Matched from: Filename : /usr/lib64/libhttp_parser.so.2 Other : libhttp_parser.so.2()(64bit) Filename : /usr/lib64/libhttp_parser.so.2.0 http-parser-2.0-4.20121128gitcd01361.el6.i686 : HTTP request/response parser for C Repo : epel Matched from: Other : libhttp_parser.so.2 Filename : /usr/lib/libhttp_parser.so.2 Filename : /usr/lib/libhttp_parser.so.2.0 nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_64 : HTTP request/response parser for C Repo : scl Matched from: Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2 Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2.0 Other : libhttp_parser.so.2()(64bit)
On Fri, May 30, 2014 at 11:18 AM, Eugene Vilensky <evilensky at gmail.com> wrote:> 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? >Exclude them from the SCL repo? [0] ( Or instead just include what you want from the SCL repo via includepkgs=. ) exclude=*nodejs* [0] http://www.cyberciti.biz/faq/redhat-centos-linux-yum-update-exclude-packages/> > > For example, the http parser dependency gets satisfied by > nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_6 > > http-parser-2.0-4.20121128gitcd01361.el6.x86_64 : HTTP request/response > parser for C > Repo : epel > Matched from: > Filename : /usr/lib64/libhttp_parser.so.2 > Other : libhttp_parser.so.2()(64bit) > Filename : /usr/lib64/libhttp_parser.so.2.0 > > > > http-parser-2.0-4.20121128gitcd01361.el6.i686 : HTTP request/response > parser for C > Repo : epel > Matched from: > Other : libhttp_parser.so.2 > Filename : /usr/lib/libhttp_parser.so.2 > Filename : /usr/lib/libhttp_parser.so.2.0 > > > > nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_64 : HTTP > request/response parser for C > Repo : scl > Matched from: > Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2 > Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2.0 > Other : libhttp_parser.so.2()(64bit) > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-- ---~~.~~--- Mike // SilverTip257 //
On 05/30/2014 10:18 AM, Eugene Vilensky wrote:> 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?EPEL is self-reliant. Nothing in EPEL will depend on another other than Base/Updates. You need to check which repo you're installing the package from, and be careful with the package name itself. There shouldn't be duplicate names. In your example, the nodejs package is coming from SCL, so you would need to use the scl tools to enable that utility (which then appropriately updates your user's environment) For example, 'scl enable nodejs010 bash' would give you a bash shell with the appropriate environment for using the nodejs from SCL.> > > For example, the http parser dependency gets satisfied by > nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_6 > > http-parser-2.0-4.20121128gitcd01361.el6.x86_64 : HTTP request/response > parser for C > Repo : epel > Matched from: > Filename : /usr/lib64/libhttp_parser.so.2 > Other : libhttp_parser.so.2()(64bit) > Filename : /usr/lib64/libhttp_parser.so.2.0 > > > > http-parser-2.0-4.20121128gitcd01361.el6.i686 : HTTP request/response > parser for C > Repo : epel > Matched from: > Other : libhttp_parser.so.2 > Filename : /usr/lib/libhttp_parser.so.2 > Filename : /usr/lib/libhttp_parser.so.2.0 > > > > nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_64 : HTTP > request/response parser for C > Repo : scl > Matched from: > Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2 > Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2.0 > Other : libhttp_parser.so.2()(64bit) > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77
Top posting: Seems someone's already filed this as a bug. You can keep an eye on the progress via -> https://bugzilla.redhat.com/show_bug.cgi?id=1042879 Similar bug impacting SSSD -> https://bugzilla.redhat.com/show_bug.cgi?id=1089090 On 05/30/2014 10:18 AM, Eugene Vilensky wrote:> 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 > nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_6 > > http-parser-2.0-4.20121128gitcd01361.el6.x86_64 : HTTP request/response > parser for C > Repo : epel > Matched from: > Filename : /usr/lib64/libhttp_parser.so.2 > Other : libhttp_parser.so.2()(64bit) > Filename : /usr/lib64/libhttp_parser.so.2.0 > > > > http-parser-2.0-4.20121128gitcd01361.el6.i686 : HTTP request/response > parser for C > Repo : epel > Matched from: > Other : libhttp_parser.so.2 > Filename : /usr/lib/libhttp_parser.so.2 > Filename : /usr/lib/libhttp_parser.so.2.0 > > > > nodejs010-http-parser-2.0-5.20121128gitcd01361.el6.centos.alt.x86_64 : HTTP > request/response parser for C > Repo : scl > Matched from: > Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2 > Filename : /opt/rh/nodejs010/root/usr/lib64/libhttp_parser.so.2.0 > Other : libhttp_parser.so.2()(64bit) > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77
Possibly Parallel Threads
- Announcing release for NodeJS 0.10 on CentOS Linux 7 x86_64 SCL
- Announcing release for NodeJS 0.10 on CentOS Linux 6 x86_64 SCL
- NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation
- Nodejs010 Packages giving unresolved dependency error when building the nodejs packages
- CentOS Digest, Vol 140, Issue 1