It doesn't — I guess gdm should have used [consolekit?,systemd(-)?].
Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/ On Mon, Dec 31, 2012 at 4:22 PM, Leho Kraav <l...@kraav.com> wrote: > Hi all > > > Just bumped into something I haven't encountered before. Running amd64. > > Already had sys-auth/pambase-20101024-r2 (stable) installed. Then > installed gnome-base/gdm-3.4.1-r3 binpkg, binhost had newer pambase, which > is why this didn't surface before. > > Everything is fine for runtime, but emerge --depclean pukes with > "sys-auth/pambase[consolekit] is not installed". Looking at this from all > angles, this condition *is* most certainly fulfilled. > > Trying to re-emerge gdm from source revealed that only >=pambase-20120417 > seems to fulfill its requirements. Initially I couldn't figure out why. > > Poking around in gdm-3.4.1-r3.ebuild L56 reveals [1]: > > sys-auth/pambase[consolekit?,**systemd?] > > This lead me to check the pambase-2010 ebuild and sure enough there is no > IUSE="systemd" flag. > Adding "systemd" to /var/db/pkg/sys-auth/pambase-**20101024-r2/IUSE made > emerge --depclean work just fine. > > Now, my question is: why does portage-2.1.11.31 not calculate a missing > IUSE=systemd in ebuild for being the same as just USE="-systemd"? It feels > like pambase-20101024-r2.ebuild [2] should fulfill gdm-3.4.1 requirements > just fine, but it doesn't, at least not for this portage version. > > Am I missing anything known and obvious? > > [1]: http://sources.gentoo.org/cgi-**bin/viewvc.cgi/gentoo-x86/** > gnome-base/gdm/gdm-3.4.1-r3.**ebuild?view=markup<http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/gnome-base/gdm/gdm-3.4.1-r3.ebuild?view=markup> > [2]: http://sources.gentoo.org/cgi-**bin/viewvc.cgi/gentoo-x86/sys-** > auth/pambase/pambase-20101024-**r2.ebuild?view=markup<http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-auth/pambase/pambase-20101024-r2.ebuild?view=markup> > >
