Summary: | sys-apps/portage-2.2.0_alpha75 ignores --quiet-build=n on resume after portage update | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Denis Lisov <dennis.lissov> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 381649 |
Description
Denis Lisov
2011-11-17 12:07:47 UTC
The bug is really only in 2.1.10.34 and 2.2.0_alpha74, and you'll experience it when upgrading or downgrading to or from either of versions. It's fixed in 2.1.10.35 and 2.2.0_alpha75 by this commit: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=957b1dcdde637338cdcef625b9c820bbfe50ae5f (In reply to comment #1) > The bug is really only in 2.1.10.34 and 2.2.0_alpha74, and you'll experience it > when upgrading or downgrading to or from either of versions. Actually, you will experience it with all older versions as well. It's a tricky interaction related to the change in defaults. In order to prevent issues like this from happening in future, I've fixed the update process so that it will no longer call emerge --resume: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d3f704a425a50b5cfa997a25866929b30f1b7d0f Of course, this won't solve upgrades from older versions of portage, since we can't stop them from calling emerge --resume after they update themselves. (In reply to comment #3) > In order to prevent issues like this from happening in future, I've fixed the > update process so that it will no longer call emerge --resume: > > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d3f704a425a50b5cfa997a25866929b30f1b7d0f This is in 2.1.10.36 and 2.2.0_alpha76. |