Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bugzilla DB migration completed. Please report issues to Infra team via email via infra@gentoo.org or IRC
Bug 699030 - New changes to portage keyword handling breaks multiple live packages, and others"
Summary: New changes to portage keyword handling breaks multiple live packages, and ot...
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
: 704042 (view as bug list)
Depends on: 658648
Blocks:
  Show dependency tree
 
Reported: 2019-10-31 15:28 UTC by rbrown4014
Modified: 2019-12-27 20:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rbrown4014 2019-10-31 15:28:19 UTC
Generally in the past live(9999) packages would install fine, even though there was no KEYWORDS variable defined in them. Now, portage throws invalid keywords for every package that doesnt have this variable defined.

To fix, revert what ever change made this check more strict, until all the ebuilds in the portage tree have had keywords updated, and then re apply. There are a lot of packages(live and non live), where this variable wasnt set at all, so it is quite annoying to have to modify ebuilds, to build packages that should build.

Reproducible: Always

Steps to Reproduce:
1.emerge any live package
2.emerge any package with no KEYWORD variable defined
3.
Actual Results:  
Portage throws invalid keyword error on package scan.

Expected Results:  
It gives error, and goes back to command line.

Installed the packages, or at least given a warning.
Comment 1 Zac Medico gentoo-dev 2019-10-31 16:50:27 UTC
Please post an example emerge command along with the unexpected output.
Comment 2 Zac Medico gentoo-dev 2019-10-31 17:39:03 UTC
I suspect that the issue you have is related to the change from bug 658648, and you can revert that simply by setting EMERGE_DEFAULT_OPTS="--autounmask" in /etc/portage/make.conf.
Comment 3 rbrown4014 2019-10-31 18:35:36 UTC
example command: emerge <any package that has KEYWORDS="" or no KEYWORD variable at all(generally 9999 ebuilds)>

Always results in missing keyword error when trying to install.

here is an example output from media-video/ffmpeg-9999 but it applies to a lot of packages, not just ffmpeg-9999.

!!! All ebuilds that could satisfy "=ffmpeg-9999" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-video/ffmpeg-9999::gentoo (masked by: missing keyword)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
Comment 4 Zac Medico gentoo-dev 2019-10-31 18:58:13 UTC
(In reply to rbrown4014 from comment #3)
> example command: emerge <any package that has KEYWORDS="" or no KEYWORD
> variable at all(generally 9999 ebuilds)>
> 
> Always results in missing keyword error when trying to install.
> 
> here is an example output from media-video/ffmpeg-9999 but it applies to a
> lot of packages, not just ffmpeg-9999.
> 
> !!! All ebuilds that could satisfy "=ffmpeg-9999" have been masked.
> !!! One of the following masked packages is required to complete your
> request:
> - media-video/ffmpeg-9999::gentoo (masked by: missing keyword)
> 
> For more information, see the MASKED PACKAGES section in the emerge
> man page or refer to the Gentoo Handbook.

This is the intended result of the changes from bug 658648. If you want the old behavior, then you need to set EMERGE_DEFAULT_OPTS="--autounmask" in /etc/portage/make.conf. This suggestion is included in the NEWS file:

https://gitweb.gentoo.org/proj/portage.git/commit/NEWS?id=196ff7d54f1a23646f2ad70801a7a04c80c0a8cd
Comment 5 Zac Medico gentoo-dev 2019-12-27 20:50:45 UTC
*** Bug 704042 has been marked as a duplicate of this bug. ***