Collection nodejs010 seems to provide unprefixed RPM providers, which can be also caused by shipping the same libraries as could be shipped outside of SCL environment. Refer to tracker bug #1042837 for more info why this can be problem and check/fix all suspicious provides, please. General discussions about the issues and why unprefixed symbols/libraries are problem should take place in the tracker bug #1042837. Components checked for collection nodejs010: nodejs010 nodejs010-build nodejs010-c-ares nodejs010-c-ares-devel nodejs010-gyp nodejs010-http-parser nodejs010-http-parser-devel nodejs010-libuv nodejs010-libuv-devel nodejs010-node-gyp nodejs010-nodejs nodejs010-nodejs-abbrev nodejs010-nodejs-ansi nodejs010-nodejs-archy nodejs010-nodejs-async nodejs010-nodejs-aws-sign nodejs010-nodejs-block-stream nodejs010-nodejs-boom nodejs010-nodejs-child-process-close nodejs010-nodejs-chmodr nodejs010-nodejs-chownr nodejs010-nodejs-combined-stream nodejs010-nodejs-config-chain nodejs010-nodejs-cookie-jar nodejs010-nodejs-couch-login nodejs010-nodejs-cryptiles nodejs010-nodejs-delayed-stream nodejs010-nodejs-devel nodejs010-nodejs-docs nodejs010-nodejs-editor nodejs010-nodejs-forever-agent nodejs010-nodejs-form-data nodejs010-nodejs-fstream nodejs010-nodejs-fstream-ignore nodejs010-nodejs-fstream-npm nodejs010-nodejs-glob nodejs010-nodejs-graceful-fs nodejs010-nodejs-hawk nodejs010-nodejs-hoek nodejs010-nodejs-http-signature nodejs010-nodejs-inherits nodejs010-nodejs-ini nodejs010-nodejs-init-package-json nodejs010-nodejs-json-stringify-safe nodejs010-nodejs-lockfile nodejs010-nodejs-lru-cache nodejs010-nodejs-mime nodejs010-nodejs-minimatch nodejs010-nodejs-mkdirp nodejs010-nodejs-mute-stream nodejs010-nodejs-node-uuid nodejs010-nodejs-nopt nodejs010-nodejs-normalize-package-data nodejs010-nodejs-npmconf nodejs010-nodejs-npmlog nodejs010-nodejs-npm-registry-client nodejs010-nodejs-npm-user-validate nodejs010-nodejs-oauth-sign nodejs010-nodejs-once nodejs010-nodejs-opener nodejs010-nodejs-osenv nodejs010-nodejs-promzard nodejs010-nodejs-proto-list nodejs010-nodejs-qs nodejs010-nodejs-read nodejs010-nodejs-read-installed nodejs010-nodejs-read-package-json nodejs010-nodejs-request nodejs010-nodejs-retry nodejs010-nodejs-rimraf nodejs010-nodejs-semver nodejs010-nodejs-sha nodejs010-nodejs-sigmund nodejs010-nodejs-slide nodejs010-nodejs-sntp nodejs010-nodejs-tar nodejs010-nodejs-tunnel-agent nodejs010-nodejs-uid-number nodejs010-nodejs-which nodejs010-npm nodejs010-runtime nodejs010-v8 nodejs010-v8-devel Potential problems found in collection nodejs010 by components: ----------------------------------------------------------------- Suspicious provides for package nodejs010-c-ares libcares.so.2()(64bit) Suspicious provides for package nodejs010-c-ares-devel pkgconfig(libcares) = 1.9.1 Suspicious provides for package nodejs010-http-parser libhttp_parser.so.2()(64bit) libhttp_parser_strict.so.2()(64bit) Suspicious provides for package nodejs010-libuv libuv.so.0.10()(64bit) Suspicious provides for package nodejs010-libuv-devel pkgconfig(libuv) = 0.10.19.git5462dab Suspicious provides for package nodejs010-nodejs-cookie-jar nodejs-tobi-cookie = 1:0.3.0 Suspicious provides for package nodejs010-v8 libv8.so.3.14.5()(64bit)
Please, apply for libraries like libperl.so, libruby.so, libv8.so prefix, as documented in http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Software_Collections_Guide/sect-Prefixing_the_Library_Major_soname_with_the_Collection_Name.html.
Node.js is still tech preview, so it should be fixed.
*** Bug 1018078 has been marked as a duplicate of this bug. ***
Fixed for currently-supported collections, let's close out. $ rpm -qp --provides rh-nodejs4-*.rpm 2>/dev/null | grep ^lib libhttp_parser.so.rh-nodejs4-2.7.0()(64bit) libhttp_parser_strict.so.rh-nodejs4-2.7.0()(64bit) libuv.so.rh-nodejs4-1.7.5()(64bit) $ rpm -qp --provides rh-nodejs6-*.rpm 2>/dev/null | grep ^lib libhttp_parser.so.rh-nodejs6-2.7.0()(64bit) libhttp_parser_strict.so.rh-nodejs6-2.7.0()(64bit) libuv.so.rh-nodejs6-1.9.1()(64bit)