| 1 |
On Friday 16 February 2007 02:00:26 Bo Ørsted Andresen wrote: |
| 2 |
> On Friday 16 February 2007 00:44:16 Bo Ørsted Andresen wrote: |
| 3 |
> > On Friday 16 February 2007 01:33:00 b.n. wrote: |
| 4 |
> > > >> 2) I still have to upgrade dbus to 1.0.2 |
| 5 |
> > > >> BEFORE: the dbus upgrade was in the -pv output |
| 6 |
> > > >> AFTER: It seems the dbus upgrade is no more in emerge -pv world. |
| 7 |
[SNIP] |
| 8 |
> On second thought this does make sense. Portage 2.1.2 allows an upgrade |
| 9 |
> within the same slot despite the block. And the reason it doesn't get |
| 10 |
> pulled in by `emerge -pv world` is because dbus isn't in world and the |
| 11 |
> later version isn't required by anything in world. You need to use --update |
| 12 |
> to get direct dependencies upgraded or --deep to get all dependencies |
| 13 |
> upgraded to the latest version. |
| 14 |
|
| 15 |
Just to close this entirely dbus-0.62-r2 has had most of it's keywords |
| 16 |
dropped. This means if you type: |
| 17 |
|
| 18 |
# emerge -pv =sys-apps/dbus-0.62-r2 |
| 19 |
|
| 20 |
you'll likely get a "masked by: missing keyword" message. So again bug #48195 |
| 21 |
explains why dbus-0.62-r2 is able to satisfy dependencies on dbus because |
| 22 |
it's installed with Portage 2.1.2 but isn't able to satisfy it with Portage |
| 23 |
2.1.1 because it's not installable. :) |
| 24 |
|
| 25 |
-- |
| 26 |
Bo Andresen |
Archives