Description of problem: Currently your component is providing both native systemd service files and legacy sysv init script in the same package which is in violation of the packaging guidelines[1]. Once a native systemd service file is shipped and if the intention is to continue to maintain and ship the old sysv initscript the old sysvinit must go into an optional subpackage. "SysV Initscripts Packages may also provide a SysV initscript file, but are not required to do so. This format is considered legacy, but Fedora still contains init mechanisms such as upstart which do not support the systemd unit file format. If present, the SysV initscript(s) must go into an optional subpackage, so as not to confuse sysadmins. The guidelines for SysV initscripts can be found here: Packaging:SysVInitScript" http://fedoraproject.org/wiki/Packaging:Guidelines:Systemd https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd http://fedoraproject.org/wiki/Packaging:Tmpfiles.d Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** This bug has been marked as a duplicate of bug 697532 ***
Note this is filed against acpid which a) is not part of iputils hence not duplicate and b) still has the legacy init script in the same package
Ah, sorry. There was already one duplicity against iputils and I was closing the bug against iputils so I've overlooked right component.