It seems that sys-libs/db used to be slotted (I previously had 3 or 4 versions installed). But todays update is failing becuase Python wants libdb-4.7 and Perl wants libdb-4.3. They won't both install because of file collisions.
Is libdb no longer slotted? How does one deal with applications that require different versions of libdb? Neither google nor bugzilla have been helpful... >>> Failed to install sys-libs/db-4.3.29_p1-r1, Log file: >>> '/var/tmp/portage/sys-libs/db-4.3.29_p1-r1/temp/build.log' * Messages for package sys-libs/db-4.3.29_p1-r1: * 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). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/bin/db_archive * /usr/bin/db_checkpoint * /usr/bin/db_deadlock * /usr/bin/db_dump * /usr/bin/db_load * /usr/bin/db_printlog * /usr/bin/db_recover * /usr/bin/db_stat * /usr/bin/db_upgrade * /usr/bin/db_verify * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-libs/db-4.7.25_p4 * /usr/bin/db_archive * /usr/bin/db_checkpoint * /usr/bin/db_deadlock * /usr/bin/db_dump * /usr/bin/db_load * /usr/bin/db_printlog * /usr/bin/db_recover * /usr/bin/db_stat * /usr/bin/db_upgrade * /usr/bin/db_verify * * Package 'sys-libs/db-4.3.29_p1-r1' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message.
