Summary: | sys-apps/portage-2.2.0_alpha63 can throw incorrect warning for binary packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Guy <defuebr> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 381649 |
Description
Guy
2011-10-08 16:09:54 UTC
Sorry - meant to put down 'sys-apps/portage-2.2.0_alpha60' in the one line desc. Not 'sys-apps/portage-2.2.0_alpha63'. 'alpha60' applies to the binary package using PCs prior to the new round of 'update world'. 'alpha63' applies to the binary package host after the new round of 'update world'. The ambiguous warning message comes from 'alpha60'. I don't know if 'alpha63' is subject to the same issue. I can confirm the 'alpha63' version has the same issue. I updated portage on a binary package PC which had not yet gone through the 'update world' process. executing: emerge -gpuNDv --with-bdeps=y @world resulted with the same ambiguous/incorrect warning message. We should only add binaries to ignored_binaries in _wrapped_select_pkg_highest_available_imp if we don't select select something with a higher version than the binary. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=6622bb5b63b49b1e528d89fee061e40b2d0d5afd This is fixed in 2.1.10.25 and 2.2.0_alpha65. |