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@centos.org http://lists.centos.org/mailman/listinfo/centos