Some scriptlet cleanup is needed in the cups package: Mise à jour de : cups-1:2.2.11-3.fc31.x86_64 5/10 Exécution du scriptlet: cups-1:2.2.11-3.fc31.x86_64 5/10 Exécution du scriptlet: cups-1:2.2.11-2.fc31.x86_64 6/10 Nettoyage de : cups-1:2.2.11-2.fc31.x86_64 6/10 Exécution du scriptlet: cups-1:2.2.11-2.fc31.x86_64 6/10 Warning: The unit file, source configuration file or drop-ins of cups.path changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of cups.socket changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units. Job failed. See "journalctl -xe" for details. Exécution du scriptlet: cups-client-1:2.2.11-2.fc31.x86_64
Hi Nicolas, thank you for reporting the issue! Actually, that update did not change any scriptlet - maybe there was some cleanup at systemd (I saw emails on devel-list about removing requires on systemd for packages, which only needs systemd to put the unit files on correct places, but I did not see anything official announcement on devel-announce, if the change will really be done), so scriptlets in cups which only install unit files could trigger this warnings... Zbyszek, would you mind telling me your opinion on the issue? Is the change already active and this is the result? Or it is different issue?
We recently changes systemd macros to not silence warnings (they used to be redirected to /dev/null, now they are not). Unfortunately this shows that there is a problem, and the warnings are valid: 'systemctl try-restart' is called during package's %postun, and 'systemctl daemon-reload' is called later, during %transfiletriggerin. It seems the whole scheme is broken ;(, and the recent change simply uncovered the error.
Thank you for the info, Zbyszek!
*** Bug 1716336 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
*** This bug has been marked as a duplicate of bug 1614751 ***