public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right?
@ 2012-12-31 15:22 Leho Kraav
  2012-12-31 15:25 ` Diego Elio Pettenò
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Leho Kraav @ 2012-12-31 15:22 UTC (permalink / raw
  To: gentoo-dev

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
[2]: 
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-auth/pambase/pambase-20101024-r2.ebuild?view=markup


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right?
  2012-12-31 15:22 [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right? Leho Kraav
@ 2012-12-31 15:25 ` Diego Elio Pettenò
  2012-12-31 15:34 ` Michał Górny
  2012-12-31 23:55 ` Zac Medico
  2 siblings, 0 replies; 6+ messages in thread
From: Diego Elio Pettenò @ 2012-12-31 15:25 UTC (permalink / raw
  To: gentoo-dev@lists.gentoo.org

[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]

It doesn't — I guess gdm should have used [consolekit?,systemd(-)?].


Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/


On Mon, Dec 31, 2012 at 4:22 PM, Leho Kraav <leho@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>
>
>

[-- Attachment #2: Type: text/html, Size: 2649 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right?
  2012-12-31 15:22 [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right? Leho Kraav
  2012-12-31 15:25 ` Diego Elio Pettenò
@ 2012-12-31 15:34 ` Michał Górny
  2013-01-02 16:49   ` Leho Kraav
  2012-12-31 23:55 ` Zac Medico
  2 siblings, 1 reply; 6+ messages in thread
From: Michał Górny @ 2012-12-31 15:34 UTC (permalink / raw
  To: gentoo-dev; +Cc: leho

[-- Attachment #1: Type: text/plain, Size: 1802 bytes --]

On Mon, 31 Dec 2012 17:22:16 +0200
Leho Kraav <leho@kraav.com> wrote:

> 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?

http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-870008.2.6.4

«Unless a 4-style default is specified, it is an error for a use
dependency to be applied to an ebuild which does not have the flag in
question in IUSE_REFERENCEABLE.»

which in understandable language means that without USE defaults, even
[-foo] matches only packages which have 'foo' in IUSE.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right?
  2012-12-31 15:22 [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right? Leho Kraav
  2012-12-31 15:25 ` Diego Elio Pettenò
  2012-12-31 15:34 ` Michał Górny
@ 2012-12-31 23:55 ` Zac Medico
  2 siblings, 0 replies; 6+ messages in thread
From: Zac Medico @ 2012-12-31 23:55 UTC (permalink / raw
  To: gentoo-dev

On 12/31/2012 07:22 AM, Leho Kraav 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?]
> 

I've fixed the --depclean output to display the unevaluated atom in this
case:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=925eadd210dbc3802000d92f458ae7029832273e

-- 
Thanks,
Zac


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right?
  2012-12-31 15:34 ` Michał Górny
@ 2013-01-02 16:49   ` Leho Kraav
  2013-01-03  2:36     ` Zac Medico
  0 siblings, 1 reply; 6+ messages in thread
From: Leho Kraav @ 2013-01-02 16:49 UTC (permalink / raw
  To: gentoo-dev

Ok my conclusion is then that gdm-3.4.1.ebuild should be patched for [systemd?-], considering it seems otherwise fully compatible with current stable pambase. Opinions?

--
Sent from my Nokia N9On 31.12.12 17:34 Michał Górny wrote:
On Mon, 31 Dec 2012 17:22:16 +0200
Leho Kraav <leho@kraav.com> wrote:

> 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?

http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-870008.2.6.4

«Unless a 4-style default is specified, it is an error for a use
dependency to be applied to an ebuild which does not have the flag in
question in IUSE_REFERENCEABLE.»

which in understandable language means that without USE defaults, even
[-foo] matches only packages which have 'foo' in IUSE.

--
Best regards,
Michał Górny



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right?
  2013-01-02 16:49   ` Leho Kraav
@ 2013-01-03  2:36     ` Zac Medico
  0 siblings, 0 replies; 6+ messages in thread
From: Zac Medico @ 2013-01-03  2:36 UTC (permalink / raw
  To: gentoo-dev, Leho Kraav

On 01/02/2013 08:49 AM, Leho Kraav wrote:
> Ok my conclusion is then that gdm-3.4.1.ebuild should be patched for [systemd?-], considering it seems otherwise fully compatible with current stable pambase. Opinions?

Since gdm is using EAPI 4, sys-auth/pambase[consolekit?,systemd(-)?]
seems doable. You can file a bug at http://bugs.gentoo.org to have the
maintainers fix it (if they agree).
-- 
Thanks,
Zac


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-01-03  2:37 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-31 15:22 [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right? Leho Kraav
2012-12-31 15:25 ` Diego Elio Pettenò
2012-12-31 15:34 ` Michał Górny
2013-01-02 16:49   ` Leho Kraav
2013-01-03  2:36     ` Zac Medico
2012-12-31 23:55 ` Zac Medico

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox