Summary: | Unreachable "newest versions" should not be fatal on an --update | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Cedric Sodhi <manday> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | manday |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 328343 | ||
Bug Blocks: |
Description
Cedric Sodhi
2011-11-01 16:12:06 UTC
> Steps to Reproduce: > 1. Have the system in a state in which many packages need normal updating > 2. One of those updatable packages should be in ~unstable and the updated > version should newly depend on another package in ~unstable, which so far was > not required to be ~unstable > 3. Try to update > Actual Results: > You can't update, unless you also unmask the other package It sounds like you're describing the --autounmask behavior which is enabled by default since portage-2.1.10. This behavior is only triggered by unsatisfied dependencies, which would cause emerge to abort even if --autounmask was disabled. So, I guess we can consider this as a duplicate of bug 328343? (In reply to comment #1) > > Steps to Reproduce: > > 1. Have the system in a state in which many packages need normal updating > > 2. One of those updatable packages should be in ~unstable and the updated > > version should newly depend on another package in ~unstable, which so far was > > not required to be ~unstable > > 3. Try to update > > Actual Results: > > You can't update, unless you also unmask the other package > > It sounds like you're describing the --autounmask behavior which is enabled by > default since portage-2.1.10. This behavior is only triggered by unsatisfied > dependencies, which would cause emerge to abort even if --autounmask was > disabled. So, I guess we can consider this as a duplicate of bug 328343? I think yes. If I conclude otherwise I'll reopen this bug. Thank you. *** This bug has been marked as a duplicate of bug 328343 *** |