Summary: | sys-apps/portage: `emerge -u @set` should not exit(0) when some packages in @set missed updates (add option making missed updates fatal) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Rick Farina (Zero_Chaos) <zerochaos> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=452732 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 300071 |
Description
Rick Farina (Zero_Chaos)
2014-04-12 18:21:22 UTC
please show the exact command line you used (In reply to Rick Farina (Zero_Chaos) from comment #0) > !!! The following update(s) have been skipped due to unsatisfied dependencies > !!! triggered by backtracking: > > pentoo/pentoo:0 A missed update is not the same as being "unsatisfied". In this case, it's possible for emerge to update some other packages while skipping that update. We should make it display precisely which broken dependencies caused the update to be skipped. We could add an option to make missed updates fatal. |