Summary: | sys-apps/portage: emerge --autounmask quits before unmasking all necessary packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | lfs9azh |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 376695 |
Description
lfs9azh
2021-09-18 03:41:47 UTC
(In reply to lfs9azh from comment #0) > It would be better if portage can tell all ebuilds that have been masked AT > ONE TIME. Try with emerge --autounmask-keep-masks=n or --autounmask to enable autounmask entirely. Actually --autounmask-keep-keywords=n is the relevant option for the masks shown in comment #0. Only use --autounmask-keep-masks=n if you want to also allow package.mask changes. Use --autounmask to allow all possible changes. (In reply to Zac Medico from comment #2) > Actually --autounmask-keep-keywords=n is the relevant option for the masks > shown in comment #0. Only use --autounmask-keep-masks=n if you want to also > allow package.mask changes. Use --autounmask to allow all possible changes. Thanks Zac Medico! Have a good day! |