Summary: | sys-apps/portage-2.2.0_alpha37 breaks USE dependencies on update @system | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Denis Lisov <dennis.lissov> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Denis Lisov
2011-06-06 09:26:36 UTC
It's probable that the broken dependencies are part of the build-time graph. You can verify this by checking whether or not `emerge --pretend --depclean --with-bdeps=n` reports the same breakage. If that doesn't report breakage, then you can prevent this issue in the future by setting EMERGE_DEFAULT_OPTS="--with-bdeps=y" in make.conf. Also, you might want to add --complete-graph to EMERGE_DEFAULT_OPTS if you want to avoid some other forms of breakage. No, emerge --pretend --depclean --with-bdeps=n still reports the breakage, and adding --with-bdeps=y to update does not prevent it. However, --complete-graph succeeds in preventing it. Oh, I thought you were using @world. Now I see that you were using @system, in which case the behavior is expected. *** This bug has been marked as a duplicate of bug 367555 *** |