(sys-apps/systemd-218-r3:0/2::gentoo, ebuild scheduled for merge) pulled in by >=sys-apps/systemd-208:0/2[abi_x86_64(-),gudev,kmod] required by (virtual/udev-208-r1:0/0::gentoo, installed) ^^^^ sys-apps/systemd (Argument) (sys-apps/systemd-208-r2:0/1::gentoo, installed) pulled in by >=sys-apps/systemd-38:0/1= required by (gnome-extra/gnome-system-monitor-3.10.2:0/0::gentoo, installed) ^^^^^ (and 8 more with the same problem) Because of #556168, which forces me to solve this kind of trivial dependencies by hand, one really big and easy to code help would be for portage to just tell me which other 8 have the same problem. This way, I have to run emerge eight incremental times, each time adding one of this problem packages to the command line just to get that full list, each time waiting for 2 minutes of dependency calculation that is known to fail from the beginning already ... Regards, Bodo
You want the --verbose-conflicts option. You can add it to EMERGE_DEFAULT_OPTS in make.conf if you want it enabled by default.
At least, we should make the relevant conflict messages show a hint about the --verbose-conflicts option being available.
There's a patch to make it suggest --verbose-conflicts in the following branch: https://github.com/zmedico/portage/tree/bug_556172 I've posted it for review here: https://archives.gentoo.org/gentoo-portage-dev/message/719ead25b24c82b1d1527385504b93ab
(In reply to Zac Medico from comment #3) > There's a patch to make it suggest --verbose-conflicts in the following > branch: > > https://github.com/zmedico/portage/tree/bug_556172 > > I've posted it for review here: > > https://archives.gentoo.org/gentoo-portage-dev/message/ > 719ead25b24c82b1d1527385504b93ab This is in the master branch now: https://gitweb.gentoo.org/proj/portage.git/commit/?id=44971d397c63e16b134d9b93b06ce3b8db768aca
Released in portage-2.2.21
