On Sunday 03 December 2006 04:33, Mark Knecht wrote: [SNIP] > Thanks for pointing out the bug report. That does look like what I'm > seeing.
On closer inspection this looks more like bug #154919 [1]. > I'm a little unclear about the way Zac finished up at the end of > this report saying 'this has been released'. It is a requirement to > update to testing-level portage, rev. 2.1.2_rc2-r1 or higher before > using the '--with-bdeps y' option? I wrongly assumed you were already on 2.1.2 despite that I really do know better.. ;) Yes, --with-bdeps is a feature that has been added in 2.1.2, however, you really don't need it here. Explanation follows.. > Or do you think it is OK with stable portage 2.1.1-r2? [SNIP] You can stick with stable for now. On Saturday 02 December 2006 19:41, Mark Knecht wrote: > Calculating dependencies... done! > > Dependencies could not be completely resolved due to > the following required packages not being installed: > > =x11-libs/qt-3.3.4-r8 required by kde-base/kdelibs-3.4.3-r1 > virtual/jdk required by sys-libs/db-4.1.25_p1-r4 > ~kde-base/kde-env-3 required by kde-base/kdelibs-3.4.3-r1 > kde-base/kdesu-3.4.1 virtual/jre required by sys-libs/db-4.1.25_p1-r4 > > Have you forgotten to run `emerge --update --deep world` prior to depclean? Bug #4698 is a long standing bug which is fixed in 2.1.2 and causing portage only to consider the highest slot of any given installed package when upgrading world. So since you have kde{libs,su}-3.5.x installed portage < 2.1.2 doesn't notice that you have an older slot which is no longer in the tree. The new --depclean algorithm in 2.1.1, however, does notice as you see above. So the solution is to prune kdelibs and kdesu... [1] https://bugs.gentoo.org/show_bug.cgi?id=154919 [2] https://bugs.gentoo.org/show_bug.cgi?id=4698 -- Bo Andresen
pgpnZm1t6jn7a.pgp
Description: PGP signature