Red Hat Bugzilla – Bug 716984
Legacy SysV initscript file must go into an optional subpackage.
Last modified: 2014-02-02 17:15:39 EST
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:
What's the current status of you are one of few that is not package
native systemd unit in the Base group correctly?
If you dont have the time to fix this should I try to find a proven packager to
do the work for you?
Created attachment 515381 [details]
Spec file patch for gpm
Note this has to be cleanup before thursday
thanks for patch, I really appreciate it!
Honestly, your patch is not applicable, because
I know that this is a diff between spec file, but '$ patch' does not
you are in git man! '$ git commit -sm "message"' and '$ git format-patch -1' will do a great job for you ;)
gpm-1.20.6-18.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gpm-1.20.6-18.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
gpm-1.20.6-18.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.