* 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/cronie-1.5.1-r1:0::gentoo * /usr/share/man/man5/anacrontab.5.bz2 * * Package 'sys-process/systemd-cron-1.5.12-r1' NOT merged due to file ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma-systemd_20180408-121704 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) [2] ruby23 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-8] Available Java Virtual Machines: [1] icedtea-8 system-vm emerge -qpv sys-process/systemd-cron [ebuild N ] sys-process/systemd-cron-1.5.12-r1 USE="-cron-boot -etc-crontab-systemd -minutely -setgid {-test} -yearly" PYTHON_SINGLE_TARGET="python3_5 -pypy3 -python3_4 -python3_6" PYTHON_TARGETS="python3_5 -pypy3 -python3_4 -python3_6"
Created attachment 527282 [details] emerge-info.txt
Created attachment 527284 [details] emerge-history.txt
Created attachment 527286 [details] etc.portage.tbz2
Created attachment 527288 [details] logs.tbz2
Created attachment 527290 [details] sys-process:systemd-cron-1.5.12-r1:20180413-093031.log
This is the same issue (with a different package) as bug 616022. I'm a bit torn on the solution here. The simplest solution is a blocker, but it seems a bit silly to block anacron and cronie over a manpage. I could rename the manpage, but then the manpage doesn't actually match the filename of the config file.
What about installing the manpage under a different man_number other than man5?
*** This bug has been marked as a duplicate of bug 616022 ***
