On 26/01/2017 12:10, Peter Humphrey wrote:
> Hello list,
>
> Today I have a block that I can't see a way out of.
>
> [blocks B ] <dev-util/gdbus-codegen-2.50.2 ("<dev-util/gdbus-
> codegen-2.50.2" is blocking dev-libs/glib-2.50.2)
> [...]
> (dev-util/gdbus-codegen-2.48.2:0/0::gentoo, ebuild scheduled for merge)
> pulled in by
> dev-util/gdbus-codegen required by (gnome-base/dconf-0.26.0-
> r1:0/0::gentoo, installed)
> dev-util/gdbus-codegen required by (net-print/cups-
> filters-1.13.3:0/0::gentoo, installed)
> >=dev-util/gdbus-codegen-2.32 required by (sys-fs/
> udisks-2.1.8:2/2::gentoo, installed)
> >=dev-util/gdbus-codegen-2.48 required by (x11-libs/gtk
> +-3.22.5:3/3::gentoo, installed)
> dev-util/gdbus-codegen required by (sys-apps/
> accountsservice-0.6.43:0/0::gentoo, installed)
>
> Then a lot of pages listing all the packages that want dev-libs/glib-2.50.2.
>
> Grepping for util and libs under /etc/portage shows nothing, so I don't
> think this is self-inflicted.
>
> Before I go rushing off to b.g.o. (which doesn't have anything relevant
> yet), am I the only one seeing this? I also have a slot conflict with x11-
> base/xorg-server and x11-drivers/xf86-video-amdgpu, but one thing at a time.
>
gdbus-codegen-2.50.2 has been around since mid-Nov, so I can't see why
portage wants to give you 2.48.2.
Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
emerge give a different result?
--
Alan McKinnon
[email protected]
