Summary: | sys-apps/portage doesn't recognise entries in /etc/portage package.mask directory | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Geoff Madden <mgmadden> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge info
my working mask file |
Description
Geoff Madden
2015-07-31 16:44:28 UTC
Created attachment 408058 [details]
emerge info
Attach your package.mask and package.unmask entries (one file each attachment). Created attachment 408080 [details]
my working mask file
(In reply to Brian Evans from comment #2) > Attach your package.mask and package.unmask entries (one file each > attachment). Dont have a package.unmask dir/file as stated in my original report,it appears portage is not recognising any entries in the package.mask directory. But will recognise a file named package.mask I am not sure if folders are allowed for package.mask... anyway, if not valid, probably it could be explained at man portage to prevent this confusions ;) It works for me. This has been supported for years, and the relevant code hasn't changed recently. |