Red Hat Bugzilla – Bug 714668
Legacy SysV initscript file must go into an optional subpackage.
Last modified: 2013-07-04 08:57:00 EDT
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
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.
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:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** Bug 706789 has been marked as a duplicate of this bug. ***
*** Bug 697522 has been marked as a duplicate of this bug. ***
Created attachment 510060 [details]
Spec file which drops SysV support for firstboot.service
I think this is correct spec file for firstboot which drops sysv support note that you need to use correct firstboot native service not the current hack ones which call the old sysv init script I'm pretty sure that I have submitted the correct native hack free systemd service files sometime during the F15 development cycle.
1.118-1 dropped the old sysv initscripts. firstboot-16.3-1.fc16 (newer) is in testing. This can be closed when it hits stable.