* Messages for package app-emulation/emul-linux-x86-baselibs-20131008: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). See * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to * solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/lib32/libtiffxx.so.5.2.0 * /usr/lib32/libusb-0.1.so.4.4.4 * /usr/lib32/libtiff.so.5.2.0 * /usr/lib32/libturbojpeg.so.0.0.0 * /usr/lib32/libusb-0.1.so.4 * /usr/lib32/libturbojpeg.so.0 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-libs/libusb-compat-0.1.5-r2:0::gentoo * /usr/lib32/libusb-0.1.so.4 * /usr/lib32/libusb-0.1.so.4.4.4 * * media-libs/tiff-4.0.3-r5:0::gentoo * /usr/lib32/libtiff.so.5.2.0 * /usr/lib32/libtiffxx.so.5.2.0 * * media-libs/libjpeg-turbo-1.3.0-r2:0::gentoo * /usr/lib32/libturbojpeg.so.0 * /usr/lib32/libturbojpeg.so.0.0.0 * * Package 'app-emulation/emul-linux-x86-baselibs-20131008' NOT merged * due to file collisions. If necessary, refer to your elog messages for * the whole content of the above message.
*** Bug 487368 has been marked as a duplicate of this bug. ***
Please, go ahead and update ${FILESDIR}/remove-native for emul packages, I cannot test both setups (I mean *system-wide* enabled/disabled abi_x86_32) currently
Also, would be risky to replace the exact version numbers by "*" to prevent this in the future? For example, once a jpeg version included multilib support, it's likely that we won't need any libjpeg* from emul set in the future ...
(In reply to Pacho Ramos from comment #2) I'm not actually a maintainer of this package, so I would prefer that you update the files based on the error message I have provided.
(In reply to Pacho Ramos from comment #3) > Also, would be risky to replace the exact version numbers by "*" to prevent > this in the future? For example, once a jpeg version included multilib > support, it's likely that we won't need any libjpeg* from emul set in the > future ... I would replace the minor/patch versions by "*". Meaning I would add, for example, "usr/lib32/libturbojpeg.so.0*" to remove-native.
+*emul-linux-x86-baselibs-20131008-r1 (09 Oct 2013) + + 09 Oct 2013; Alexandre Rostovtsev <tetromino@gentoo.org> + -emul-linux-x86-baselibs-20131008.ebuild, + +emul-linux-x86-baselibs-20131008-r1.ebuild, files/remove-native: + Update remove-native to prevent file collisions (bug #487364, acked by Pacho + Ramos).
