Summary: | portage-2.1.9.42: portage --pretend doesn't | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Raymond Jennings <shentino> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Raymond Jennings
2011-06-29 07:36:50 UTC
In theory, this means that if brasero and gvfs are both merged in the same batch, then portage's failure to pick up gvfs's changed USE flags while analyzing compliance with brasero's deps would cause brasero to have an unmet dependency once gvfs got remerged with a deficient use flag. Confirmed. Simultaneously merging brasero, and remerging gvfs with a (required by brasero) cdda use flag removed, caused brasero to be installed simultaenously with a cdda-less gvfs. This should not be possible. Portage should be taking into account proposed use flag changes in already installed packages when running dep checks for packages to be freshly merged. To add insult to injury, gvfs lacking the cdda use flag didn't even cause a build failure in brasero. It seems like USE flag changes of packages that have already been installed (and are set to be reinstalled with the changed flags) aren't taken into account when other packages that depend on them have their dependencies evaluated. I should also note that while re-emerging both brasero and gvfs simultaneously (after changing gvfs's use flags) causes an inconsistent situation, remerging gvfs and brasero serially causes brasero to dep-barf after gvfs is remerged manually. I don't think it's ok for emerge to behave differently depending on whether two packages are emerged at the same time or in series. (In reply to comment #2) > Simultaneously merging brasero, and remerging gvfs with a (required by brasero) > cdda use flag removed, caused brasero to be installed simultaenously with a > cdda-less gvfs. This looks like bug 367555. You can set EMERGE_DEFAULT_OPTS="--complete-graph" in order to avoid this behavior. See "Why doesn't emerge account for reverse dependencies sometimes?" in the FAQ: http://www.gentoo.org/proj/en/portage/doc/faq.xml The behavior in comment 0 could also be bug 266836. (In reply to comment #5) > This looks like bug 367555. You can set > EMERGE_DEFAULT_OPTS="--complete-graph" in order to avoid this behavior. The new -complete-graph-if-new-use option (enabled by default) helps for this case (see bug #425558). |