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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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

Closed by  Doug Newgard (Scimmia)
Friday, 27 May 2016, 02:55 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Thursday, 26 May 2016, 22:51 GMT
Do you have anything in /etc/systemd/* that references the timer/service?
Comment by pedrum (pd5rm) - Thursday, 26 May 2016, 23:15 GMT
I find | grep'd and there were no files named man-db. The service/timer files were removed in the recent package changes (from -1 to -2).
Comment by Doug Newgard (Scimmia) - Thursday, 26 May 2016, 23:52 GMT
Right, they aren't there anymore, so how could they fail?
Comment by pedrum (pd5rm) - Friday, 27 May 2016, 01:15 GMT
I think they're still loaded in memory unless you remove them explicitly, but I'm no systemd expert. ;-)
Comment by Doug Newgard (Scimmia) - Friday, 27 May 2016, 02:22 GMT
Oh, so the issue is simply that you haven't reloaded systemd or rebooted yet.
Comment by pedrum (pd5rm) - Friday, 27 May 2016, 02:42 GMT
I did call 'systemctl daemon-reload', but no reboot.
Comment by Doug Newgard (Scimmia) - Friday, 27 May 2016, 02:55 GMT
daemon-reload just reloads some configuration data. daemon-reexec should do it. Really, though, it doesn't matter.

I'm going to close this. This is something left to the sysadmin, not a bug.

Loading...