Summary: | sys-process/systemd-cron-1.5.12-r1 : file collision with sys-process/cronie-1.5.1-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Richard Freeman <rich0> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | cron-bugs+disabled, polynomial-c |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt etc.portage.tbz2 logs.tbz2 sys-process:systemd-cron-1.5.12-r1:20180413-093031.log |
Description
Toralf Förster
![]() 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 *** |