[gentoo-user] Somehow my local portage tree is out of sync

[gentoo-user] Somehow my local portage tree is out of sync

[Mike Mazur]

Hi,

I've had this issue for a few days now...

`emerge -pvuDN world` tells me that "x11-libs/libwnck-2.16.3 (masked
by: ~x86 keyword)". But when looking inside
/usr/portage/x11-libs/libwnck/libwnck-2.16.3.ebuild I see
KEYWORDS="alpha amd64 ~arm hppa ia64 ppc ppc64 ~sh sparc x86
~x86-fbsd". I've done `emerge --sync` and `emerge --metadata`, but
still this persists.

I've never come across such a situation before. How do I fix this? `rm
-rf /usr/portage/x11-libs && emerge --sync`, perhaps?

Thanks!
Mike
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Somehow my local portage tree is out of sync

[Xavier Parizet]

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

OIMELONG "Mike Mazur" <mmazur@gmail.com> wrote :
> Hi,
>
> I've had this issue for a few days now...
>
> `emerge -pvuDN world` tells me that "x11-libs/libwnck-2.16.3 (masked
> by: ~x86 keyword)". But when looking inside
> /usr/portage/x11-libs/libwnck/libwnck-2.16.3.ebuild I see
> KEYWORDS="alpha amd64 ~arm hppa ia64 ppc ppc64 ~sh sparc x86
> ~x86-fbsd". I've done `emerge --sync` and `emerge --metadata`, but
> still this persists.
>
> I've never come across such a situation before. How do I fix this? `rm
> -rf /usr/portage/x11-libs && emerge --sync`, perhaps?
Try running your emerge -pvuDN world as this : 
ACCEPT_KEYWORDS="~x86" emerge -pvuDN world
or add ACCEPT_KEYWORDS="~x86" to your /etc/make.conf .
If this not works, can you post the output of emmerge --info ?
>
> Thanks!
Regards.
> Mike

--
Xavier Parizet <blackhawk@linuxant.fr>
http://www.linuxant.fr

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: Somehow my local portage tree is out of sync

[Mike Mazur]

Hi,

On 6/7/07, Xavier Parizet <blackhawk@linuxant.fr> wrote:
> Try running your emerge -pvuDN world as this :
> ACCEPT_KEYWORDS="~x86" emerge -pvuDN world
> or add ACCEPT_KEYWORDS="~x86" to your /etc/make.conf .

Sure, adding '=x11-libs/libwnck-2.16.3 ~x86' to my
/etc/packages/package.keywords allows me to update, no problems there.
What I don't understand is that libwnck-2.16.3 is not marked ~x86 in
portage:
http://packages.gentoo.org/ebuilds/?libwnck-2.16.3

Also, the ebuild on my system claims that libwnck2.16.3 is stable on my system:
# cat /usr/portage/x11-libs/libwnck/libwnck-2.16.3.ebuild | grep
KEYWORDSKEYWORDS="alpha amd64 ~arm hppa ia64 ppc ppc64 ~sh sparc x86
~x86-fbsd"

But yet somehow portage thinks that libwnck-2.16.3 is masked by the
~x86 keyword.

Still puzzled,
Mike
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Somehow my local portage tree is out of sync

[Bo Ørsted Andresen]

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

On Thursday 07 June 2007 11:19:30 Mike Mazur wrote:
> I've had this issue for a few days now...
>
> `emerge -pvuDN world` tells me that "x11-libs/libwnck-2.16.3 (masked
> by: ~x86 keyword)". But when looking inside
> /usr/portage/x11-libs/libwnck/libwnck-2.16.3.ebuild I see
> KEYWORDS="alpha amd64 ~arm hppa ia64 ppc ppc64 ~sh sparc x86
> ~x86-fbsd". I've done `emerge --sync` and `emerge --metadata`, but
> still this persists.
>
> I've never come across such a situation before. How do I fix this? `rm
> -rf /usr/portage/x11-libs && emerge --sync`, perhaps?

An overlay? emerge --info ?

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Somehow my local portage tree is out of sync

[Mike Mazur]

Hi,

On 6/7/07, Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
> An overlay?

Yep, that was it. Feeling pretty silly right now.

Thanks a lot!
Mike
--
gentoo-user@gentoo.org mailing list