Summary: | emerge parallelization | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Steinmetz <ast> |
Component: | New packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 184128 |
Description
Andreas Steinmetz
2011-09-18 02:48:36 UTC
Behavior like you describe can be triggered by deep dependencies, which emerge identifies by traversing dependencies recursively. That's part of the design, and bug 279623 is about adding a mode for more aggressive parallelization. There are lots of things that depend on ghostscript, so it wouldn't surprise me if it was a deep dependency that triggered the behavior. The output of `emerge -pv --depclean` will show a full dependency tree, which we can use to confirm this. *** This bug has been marked as a duplicate of bug 279623 *** Another reason this type of behavior is that system packages (or their dependencies) may be waiting for other builds (like ghostscript) to complete before they are merged, in order to avoid issues like the one reported in bug 256616. I have updates running right now, and I noticed this happening during a app-emulation/wine build because there was a sys-power/upower install being held back by the app-emulation/win build. *** Bug 403895 has been marked as a duplicate of this bug. *** |