Summary: | portage-2.2.0_alpha37 does not display why a package is masked | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alec Moskvin <alecm> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 358927 |
That's true, we should display the mask comments there. Until this is fixed, note that you can use --autounmask=n to see the mask comments. Also, we have an unreleased fix which makes emerge note that the --autounmask=n option is available (from bug 369917). This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=61ee292b5976be4a7f0495cc1a5f4df75357bd03 This is fixed in 2.1.10 and 2.2.0_alpha38. |
When trying to emerge a masked package, portage used to display the file where the package was masked as well as a the comment above it describing why it was masked. This was convenient. The recent versions of portage no longer do this. Reproducible: Always Steps to Reproduce: 1. Add a package to package.mask 2. Try to emerge it Actual Results: # emerge -p gtk+:3 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS #] x11-libs/gtk+-3.0.10 [2.24.4] USE="cups vim-syntax (-aqua) -debug -doc -examples -introspection -test -xinerama" The following mask changes are necessary to proceed: #required by gtk+:3 (argument) >=x11-libs/gtk+-3.0.10