This is a tracking bug for Change: Systemd file triggers For more details, see: https://fedoraproject.org//wiki/Changes/systemd_file_triggers systemd daemon-reload is invoked once or twice per rpm transaction.
This is mostly done in rawhide (systemd-228-4.gite35a787). The triggers have been implemented, and so far there have been no bug reports over two months. There is some ugliness in the implementation though (#1287918, #1284645), but the triggers are functional.
On 2016-Feb-23, we have reached Fedora 24 Change Checkpoint: Completion deadline (testable). At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline. Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness. Incomplete and non testable Changes will be reported to FESCo on 2016-Feb-26 meeting. Contingency plan for System Wide Changes, if planned for Alpha (or in case of serious doubts regarding Change completion), will be activated.
It is implemented, I should have set it to MODIFIED with comment #1.
On 2016-Apr-19 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 24 release. At this point all the Changes not at least in in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review. Thanks, Jan