Summary: | Avoid loops with @preserved-rebuild | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin von Gagern <Martin.vGagern> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | esigra |
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 240323 |
Description
Martin von Gagern
2009-10-27 17:26:51 UTC
You can use the --complete-graph option to check for upgrade/downgrade issues like this. It's not enabled by default because it makes small dependency calculations significantly slower. (In reply to comment #1) > You can use the --complete-graph option to check for upgrade/downgrade issues > like this. It's not enabled by default because it makes small dependency > calculations significantly slower. Since portage-2.1.9.42 and portage-2.2.0_alpha26, downgrades automatically trigger --complete-graph mode: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=f90df89f9053bdad96d61935d704f33239f3fed5 However, it won't help if your conflicting packages (ffmpeg and avidemux) are not both pulled in as dependencies of the world set. It seems like this was probably the case, since otherwise you probably would have noticed a "slot conflict" error at some point. Anyway, I plan to implement a --preserved-rebuild target (bug #364425) which will solve this problem by automatically excluding any packages that are eligible for removal by --depclean. *** This bug has been marked as a duplicate of bug 364425 *** |