On Friday 16 February 2007 00:44:16 Bo Ørsted Andresen wrote: > On Friday 16 February 2007 01:33:00 b.n. wrote: > > >> 2) I still have to upgrade dbus to 1.0.2 > > >> BEFORE: the dbus upgrade was in the -pv output > > >> AFTER: It seems the dbus upgrade is no more in emerge -pv world. > > > > > > This seems weird. What's the output of `emerge -pv dbus` with portage > > > 2.1.2? > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > [ebuild U ] sys-apps/dbus-1.0.2 [0.62-r2] USE="X -debug -doc > > (-selinux) (-gtk%*) (-mono%) (-python%*) (-qt3%*) (-qt4%*)" 1,368 kB > > > > Total: 1 package (1 upgrade), Size of downloads: 1,368 kB > > > > Note that before dbus 0.62 was somehow blocking, now it is no more > > blocking. Etaoin Shrdlu referred to another bug that may explain this, > > but it's quite unclear to me. > > I'll suggest you file a bug with emerge --info in a comment and > emerge --debug -vp dbus attached. This clearly seems like like something is > wrong and if nothing else at least we'll find an explanation.
On second thought this does make sense. Portage 2.1.2 allows an upgrade within the same slot despite the block. And the reason it doesn't get pulled in by `emerge -pv world` is because dbus isn't in world and the later version isn't required by anything in world. You need to use --update to get direct dependencies upgraded or --deep to get all dependencies upgraded to the latest version. -- Bo Andresen
pgpUugGLZWkBv.pgp
Description: PGP signature
