Summary: | sys-apps/portage-2.1.12.2: not displaying useful information at all on this block | ||
---|---|---|---|
Product: | Portage Development | Reporter: | DJ Dunn <djdunn.safety> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | esigra, tomwij |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 300071, 472632 |
Description
DJ Dunn
2013-08-07 05:28:57 UTC
1 more thing, after running emerge -au1 eudev, portage did suggest the changes to eudev use flags adding static-libs and told me to run dispatch-conf. and after that the block cleared. Did emerge show a message after the merge list, similar to the one at the end of bug #365127, comment #0? It sounds like maybe a the issue is the same as bug #365127, but involving virtual/udev instead of virtual/ffmpeg. With virtuals like these, it's very important that the USE flags synchronized between the virtual and the package it depends on. This kind of behavior happened multiple times to me with --dynamic-deps=n. the only messages after were some proposed autounmask changes for udev and that i should run dispatch-conf. comment 0 was a wgetpaste only thing missing was 1-2 lines from --ask that i didnt include I had already made the use and unmask changes thats why they didnt show up in the wgetpaste the only messages after were saying that eudev blocks udev in the usual blocker message fashion, and some proposed autounmask changes for udev and that i should run dispatch-conf. (In reply to DJ Dunn from comment #4) > the only messages after were some proposed autounmask changes for udev and > that i should run dispatch-conf. comment 0 was a wgetpaste only thing > missing was 1-2 lines from --ask that i didnt include Please post output of `emerge --version`. Portage 2.1.12.2 (default/linux/amd64/13.0/desktop/kde, gcc-4.7.3, glibc-2.16.0, 3.4.52-std371-amd64 x86_64) (In reply to DJ Dunn from comment #6) > the only messages after were saying that eudev blocks udev in the usual > blocker message fashion, and some proposed autounmask changes for udev and > that i should run dispatch-conf. Afterwards it's supposed to show either a slot conflict message or similar blocker conflict message. Next time, please post the entire emerge output so that there is no confusion. I will assume that the problem has been fixed unless you can reproduce it with portage-2.2.0 or later. Since portage-2.1.12.5 the parents of packages involved in blocker conflicts are always shown unless the packages are directly involved in a slot conflict: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=f4058826bd2928fb9f12b5cac1d225d79e58c993 |