* Detected file collision(s): * * /usr/share/man/man5/anacrontab.5.bz2 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-process/systemd-cron-1.5.12-r1:0::gentoo * /usr/share/man/man5/anacrontab.5.bz2 * * Package 'sys-process/anacron-2.3-r2' NOT merged due to file ------------------------------------------------------------------- This is an stable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_stable-libressl_20190503-232230 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * Available Rust versions: [1] rust-bin-1.29.1 [2] rust-1.29.1 * java-config: The following VMs are available for generation-2: emerge -qpvO sys-process/anacron [ebuild N ] sys-process/anacron-2.3-r2
Created attachment 575916 [details] emerge-info.txt
Created attachment 575918 [details] emerge-history.txt
Created attachment 575920 [details] etc.portage.tbz2
Created attachment 575922 [details] logs.tbz2
Created attachment 575924 [details] sys-process:anacron-2.3-r2:20190508-200425.log
See also: Bug 653108 Bug 616022 Basically we have three different implementations installing variants on the same manpage. I guess these could block, but I'd have to dig into whether they're actually otherwise-incompatible.
