Description of problem: Running "dnf -y upgrade" to pick up the latest updates to Fedora 22 generated error messages "Error: Transaction check error: file /etc/logrotate.d/syslog from install of rsyslog-8.8.0-3.fc22.x86_64 conflicts with file from package syslog-ng-3.6.2-2.fc22.x86_64' I'm not sure if this a UFU (user foul up). This system has both rsyslog and syslog-ng installed. I'm not sure how that happened, might have come out of the box that way. Is there a recommended version to use? Version-Release number of selected component (if applicable): syslog-ng-3.6.2-2.fc22.x86_64 rsyslog-8.8.0-2.fc22.x86_64 How reproducible: For now, always. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This seems to be a recurring issue. As far as I know, it is not allowed to have file conflicts between packages. It seems that rsyslog and syslog-ng packages have an exception. Either way, there is nothing DNF can do.
Radek The workaround I picked was to remove rsyslogd... there seems to be some small controversy about which one to use. The syntax for config for syslog-ng appears to be superior. Somehow I got both installed. NOT any more! George...
It isn't permitted for there just to be file conflicts between two packages as this breaks updates at a point too late to fix the transaction set. If the file conflict is intentional, then the packages should be marked as conflicting in their spec files.
What I understood from the referenced bugs, it seems that the goal is to allow installation of both rsyslog and syslog-ng at the same time. That's why they didn't add the explicit conflicts there, I guess.
Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1269245
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.