| 1 |
> > On second thought this does make sense. Portage 2.1.2 allows an upgrade |
| 2 |
> > within the same slot despite the block. And the reason it doesn't get |
| 3 |
> > pulled in by `emerge -pv world` is because dbus isn't in world and the |
| 4 |
> > later version isn't required by anything in world. You need to use --update |
| 5 |
> > to get direct dependencies upgraded or --deep to get all dependencies |
| 6 |
> > upgraded to the latest version. |
| 7 |
> |
| 8 |
> Just to close this entirely dbus-0.62-r2 has had most of it's keywords |
| 9 |
> dropped. This means if you type: |
| 10 |
> |
| 11 |
> # emerge -pv =sys-apps/dbus-0.62-r2 |
| 12 |
> |
| 13 |
> you'll likely get a "masked by: missing keyword" message. So again bug #48195 |
| 14 |
> explains why dbus-0.62-r2 is able to satisfy dependencies on dbus because |
| 15 |
> it's installed with Portage 2.1.2 but isn't able to satisfy it with Portage |
| 16 |
> 2.1.1 because it's not installable. :) |
| 17 |
|
| 18 |
Ok. Now the question is: is the new dbus really installable indeed? I |
| 19 |
think "yes" from your explanation, but I want to be triple-sure. |
| 20 |
(In fact, a self-blocking packages looked very odd to me, but...) |
| 21 |
(and why has been 0.62-r2 been hard masked so fast?) |
| 22 |
|
| 23 |
m. |
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives