Summary: | sys-apps/portage-2.2.0_alpha47 sets EMERGE_DEFAULT_OPTS="--autounmask=y" by default | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Amit Prakash Ambasta <amit.prakash.ambasta> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | pchrist |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 376695 | ||
Attachments: | emerge output from paste URL |
Description
Amit Prakash Ambasta
2011-07-28 07:44:03 UTC
Created attachment 281225 [details]
emerge output from paste URL
I've attached your pasted emerge output here, in case the URL expires.
(In reply to comment #0) > [...] autounmask=y [...] leads to > incoherent results while emerging packages and adds to user confusion. Please file bugs for specific cases. > Also, it > overrides masks in /etc/portage/package.mask > Right, but how is that worse than the old output that told you that it can't proceed because all packages are masked? >Steps to Reproduce: >1. emerge portage 2.2 alpha 47 >2. mask dev-db/mysql and virtual/mysql >3. emerge dev-db/mysql >Actual Results: >Overrides /etc/portage/package.mask and shows incoherent results. What else should it say than it needs to unmask dev-db/mysql? >Expected Results: >Should respect /etc/portage/package.mask and have saner suggestions! >The attached url is on a system without mysql while using autounmask=y on >portage 2.1.10.3. > The attached url Please don't use pastbins on bugzilla as they expire. > is on a system without mysql while using autounmask=y on > portage 2.1.10.3. Your past is missing the command. Hard to tell without it if it makes sense what it tells you. What suggestion do you expect? > > Moreover, in my opinion it would be wiser to advise user to use auto-unmask in > case portage runs into mask issues while emerging packages, than first > auto-unmasking and then informing user if issues arise. Without --autounmask users have to solve one conflict after another, autounmask is much better in that regard. *** This bug has been marked as a duplicate of bug 372485 *** |