Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 577678 - portage --auto-unmask on unsupported architecture suggests on adding entries in package.accept_keywords
Summary: portage --auto-unmask on unsupported architecture suggests on adding entries ...
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Mike Gilbert
URL:
Whiteboard:
Keywords:
: 577710 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-03-18 05:46 UTC by Oleh
Modified: 2016-03-18 16:53 UTC (History)
4 users (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 Oleh 2016-03-18 05:46:05 UTC
Here is the deal. Since early March, google chrome precompiled images dropped 32-bit on Linux (and platforms too). Ebuild in portage that is:
=www-client/google-chrome-49.0.2623.87_p1 
has only ~amd64 keywords as expected. Now, if I set stable x86 chroot and attempt to merge this version of ebuild, portage suggest to add keywords with --auto-unmask. It may be easily overlooked and any user can trust portage and add keywords, which leads to breakage.



Reproducible: Always

Steps to Reproduce:
1. create stable x86 chroot (or use such box)
2. emerge =www-client/google-chrome-49.0.2623.87_p1 -av
3. notice a message about adding keywords
4. hit "yes"
5. notice an expected failure.
Actual Results:  
oleg2 / # emerge =www-client/google-chrome-49.0.2623.87_p1 -av

[ebuild  N    *] www-client/google-chrome-49.0.2623.87_p1::gentoo  USE="plugins" LINGUAS="am ar bg bn ca cs da de el en_GB es es_LA et fa fake_bidi fi fil fr gu he hi hr hu id it ja kn ko lt lv ml mr ms nb nl pl pt_BR pt_PT ro ru sk sl sr sv sw ta te th tr uk vi zh_CN zh_TW" 0 KiB

Total: 127 packages (125 new, 2 in new slots), Size of downloads: 232,134 KiB

The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by google-chrome (argument)
=www-client/google-chrome-49.0.2623.87_p1 **

The following license changes are necessary to proceed:
 (see "package.license" in the portage(5) man page for more details)
# required by google-chrome (argument)
>=www-client/google-chrome-49.0.2623.87_p1 google-chrome

NOTE: The --autounmask-keep-masks option will prevent emerge
      from creating package.unmask or ** keyword changes.

Would you like to add these changes to your config files? [Yes/No]
Comment 1 Zac Medico gentoo-dev 2016-03-18 06:01:34 UTC
How about if we set REQUIRED_USE="ABI_X86_64" in the google-chrome ebuilds? If we do that, then it will provide some useful information to package managers, since it will make it impossible to install unless the profile enables ABI_X86_64.
Comment 2 Oleh 2016-03-18 07:43:21 UTC
added in ebuild locally.

that seems working:

oleg2 / # emerge =www-client/google-chrome-49.0.2623.87_p1 -av

 * IMPORTANT: 3 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


These are the packages that would be merged, in order:

Calculating dependencies /

!!! Problem resolving dependencies for =www-client/google-chrome-49.0.2623.87_p1                                                     ... done!

!!! The ebuild selected to satisfy "=www-client/google-chrome-49.0.2623.87_p1" has unmet requirements.
- www-client/google-chrome-49.0.2623.87_p1::gentoo USE="plugins" LINGUAS="am ar bg bn ca cs da de el en_GB es es_LA et fa fake_bidi fi fil fr gu he hi hr hu id it ja kn ko lt lv ml mr ms nb nl pl pt_BR pt_PT ro ru sk sl sr sv sw ta te th tr uk vi zh_CN zh_TW"

  The following REQUIRED_USE flag constraints are unsatisfied:
    abi_x86_64

oleg2 / # USE="abi_x86_64" emerge =www-client/google-chrome-49.0.2623.87_p1 -av

 * IMPORTANT: 3 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


These are the packages that would be merged, in order:

Calculating dependencies \

!!! Problem resolving dependencies for =www-client/google-chrome-49.0.2623.87_p1                                                     ... done!

!!! The ebuild selected to satisfy "=www-client/google-chrome-49.0.2623.87_p1" has unmet requirements.
- www-client/google-chrome-49.0.2623.87_p1::gentoo USE="plugins" LINGUAS="am ar bg bn ca cs da de el en_GB es es_LA et fa fake_bidi fi fil fr gu he hi hr hu id it ja kn ko lt lv ml mr ms nb nl pl pt_BR pt_PT ro ru sk sl sr sv sw ta te th tr uk vi zh_CN zh_TW"

  The following REQUIRED_USE flag constraints are unsatisfied:
    abi_x86_64
Comment 3 Oleh 2016-03-18 07:44:17 UTC
however it may rise another questions from users?
Comment 4 Zac Medico gentoo-dev 2016-03-18 07:50:23 UTC
(In reply to Oleg from comment #3)
> however it may rise another questions from users?

Thanks for testing. I think the resulting error message is intuitive enough, but that's just me.
Comment 5 Mike Gilbert gentoo-dev 2016-03-18 14:22:41 UTC
I guess that will work, at least until someone decides that portage should start automatically unmasking USE flags as well.
Comment 7 Mike Gilbert gentoo-dev 2016-03-18 14:42:14 UTC
*** Bug 577710 has been marked as a duplicate of this bug. ***