FS#49477 - [man-db] man-db.timer in failed state after latest package upgrade
Attached to Project:
Arch Linux
Opened by pedrum (pd5rm) - Thursday, 26 May 2016, 22:14 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 27 May 2016, 02:55 GMT
Opened by pedrum (pd5rm) - Thursday, 26 May 2016, 22:14 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 27 May 2016, 02:55 GMT
|
Details
Description:
The latest package update to man-db (2.7.5-2) removes the man-db timer/service systemd files from disk. This results in a failed state for man-db when you use the 'systemctl --failed --all'. I'm not sure how systemd removal works, but should these services/timer be masked or disabled on removal? Should the 'reset-failed' action be called on them so they don't show as failed errors? Will a system reboot (not optimal, but a reasonable workaround) cleanly do these actions? Steps to reproduce: Upgrade from man-db 2.7.5-1 to 2.7.5-2. |
This task depends upon
I'm going to close this. This is something left to the sysadmin, not a bug.