Bug 409739 – --autounmask-write doesn't seem to work correctly

• Status: RESOLVED INVALID
• Product: Portage Development

[Description Dirkjan Ochtman (RETIRED) 2012-03-26 09:16:37 UTC]

With my overlay from http://hg.xavamedia.nl/portage, I cannot reliably install the app-text/pelican package on my stable x86 server using the stable version of portage 2.1.10.49 (but it's not a recent regression). Adding app-text/pelican to /etc/portage/package.keywords (either just CP, CPV, with or without ~x86) doesn't appear to help, even the results of --autounmask-write fail (after etc-update). I don't have any other files in /etc/portage that could overwrite this.

'ACCEPT_KEYWORDS=~x86 emerge -1 pelican' works, but it's still rather annoying. wired reports it works correctly in portage 2.2.

[Comment 1 Zac Medico 2012-03-26 16:27:23 UTC]

There's probably something wrong with your configuration. Try moving you existing configuration out of the way:

   mv /etc/make.conf /etc/make.conf.backup
   mv /etc/portage /etc/portage.backup

Then try again:

   emerge --autounmask-write pelican
   etc-update
   emerge pelican

[Comment 2 Zac Medico 2012-03-26 16:29:02 UTC]

Also, check if ACCEPT_KEYWORDS is exported in your shell environment, like this:

    env | grep ACCEPT_KEYWORDS

[Comment 3 Dirkjan Ochtman (RETIRED) 2012-03-27 07:53:43 UTC]

You're right, with /etc/portage and /etc/make.conf out of the way, it works. So what kinds of things should I be looking for that make this not work?

[Comment 4 Zac Medico 2012-03-27 07:59:49 UTC]

Do you have any other settings for pelican in package.keywords or package.accept_keywords? Do you have any matching wildcard atoms in those files?

[Comment 5 Zac Medico 2012-03-27 08:01:20 UTC]

Usually, a command like this will find anything relevant:

  grep -r pelican /etc/portage

[Comment 6 Dirkjan Ochtman (RETIRED) 2012-03-27 08:55:30 UTC]

The result of the grep is this:

/etc/portage/package.keywords:=dev-python/pelican-2.7.2 ~x86
/etc/portage/package.unmask:dev-python/pelican

[Comment 7 Zac Medico 2012-03-27 14:07:50 UTC]

(In reply to comment #6)
> The result of the grep is this:
> 
> /etc/portage/package.keywords:=dev-python/pelican-2.7.2 ~x86
> /etc/portage/package.unmask:dev-python/pelican

I don't see anything here that would cause your issue. Do you have any matching wildcard atoms in package.keywords or package.accept_keywords?

Since we still don't know the source of trouble, I'd suggest to use a bisection-style search method. Just move all your configs out of the way as suggested in comment #1, then move them back one by one until you find the one that triggers the problem.

[Comment 8 Dirkjan Ochtman (RETIRED) 2018-04-23 09:00:47 UTC]

I guess this was a problem on my side; closing.