Summary: | sys-apps/portage: emerge needs a more clever parent selection for blocked packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Vladimir Berezhnoy <non7top> |
Component: | Core | 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: | 159310 | ||
Bug Blocks: | 300071, 381649, 390359 | ||
Attachments: | log |
Description
Vladimir Berezhnoy
2011-10-02 13:54:59 UTC
Created attachment 288553 [details]
log
emerge system -uDavN &> log.log
What concerns the merge list, no it should display all packages that are about to be installed. A problem with your output is that it shows too many parents for the slot conflict message. Does this still happen if you update portage first? (emerge -1u portage and then run your command again) sys-apps/portage-2.1.10.20 gives the same output I miss read it. It's not a slot conflict, but blocked packages. This is a long standing issue. What we should do is to use the same parent selection algorithm the slot conflict handler uses. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=77b651300731ec007cd535a83b8ee9a898602783 This is fixed in 2.1.10.21 and 2.2.0_alpha61. |