Red Hat Bugzilla – Bug 714705
Legacy SysV initscript file must go into an optional subpackage.
Last modified: 2011-07-20 07:58: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 697526 has been marked as a duplicate of this bug. ***
SysV init scripts dropped in ntp-4.2.6p3-5.fc16.