Description of problem: I saw this during today's yum update: ---> Package man-db.x86_64 0:2.6.7.1-13.fc21 will be updated ---> Package man-db.x86_64 0:2.6.7.1-14.fc21 will be an update <snip> Failed to stop mandb.timer: Unit mandb.timer not loaded. Updating : man-db-2.6.7.1-14.fc21.x86_64 105/250 It would be nice if it didn't print anything, unless there really is an error. Is there an error?
It is not. For a while man-db used systemd timer instead of cron to update local cache. This change was reverted. Since some users updated man-db using timer I added code to stop and disable timer to remove it from their system as well. This can be ignored.
However, as this error message is going to show up with every update, it should be removed.
f21: https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20150518/1578444.html f22: https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20150518/1578458.html master: https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20150518/1578503.html
man-db-2.6.7.1-15.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/man-db-2.6.7.1-15.fc21
man-db-2.7.1-5.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/man-db-2.7.1-5.fc22
Package man-db-2.7.1-5.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing man-db-2.7.1-5.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-8629/man-db-2.7.1-5.fc22 then log in and leave karma (feedback).
man-db-2.6.7.1-15.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
man-db-2.7.1-5.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.