Description of problem: good old yum logged all package actions (install, update, ...) and respective package versions to syslog by default. Regardless if the action was done through commandline, yum-cron or whatever. Like this: yum[3218]: Updated: device-mapper.x86_64 1.02.90-2.el6_6.2 yum[27167]: Installed: tmux-1.6-3.el6.x86_64 This is very helpful if you are debugging a problem, you are able to pinpoint when it started and see in the log that some packages where installed or updated shortly before. So please add that to dnf too and enable it by default. Version-Release number of selected component (if applicable): dnf-1.0.1-2.fc22 How reproducible: always. Steps to Reproduce: 1. dnf install foo 2. journalctl -t dnf --since -1m | grep -i install Actual results: empty Expected results: dnf[pid]: Installed: foo-1.2.3
Dnf logs actions into /var/log/dnf.log but I must admit that filtering in journalctl is more convenient.
dnf.log is very chatty, even with the default "debuglevel = 1" from automatic.conf. I don't think all this information is needed unless you are debugging some dnf problem. What I'm after is the stuff that is supposed to go in dnf.rpm.log. I think that should go to the journal / syslog by default instead. I think there are several reasons why I think this is a good idea: - one log file contains the package installs/upgrades and the (error) messages of the packages updated. So the reason for the messages (= the update) is obvious to the reader of the log and you don't have to think about "oh maybe there was an update, let's look into dnf.rpm.log". Especially important if you don't have seasoned admins but newbies. - Automatically integrates into remote logging systems if you have them set up for your regular journald / syslog. - Automatically integrates into log monitoring and alert systems if you have them set up for your regular journald / syslog.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.
*** This bug has been marked as a duplicate of bug 1278865 ***