Red Hat Bugzilla – Bug 495529
rpmlint incorrect warning for missing-lsb-keyword Default-Stop
Last modified: 2010-08-10 11:13:37 EDT
Description of problem:
rpmlint warns if the LSB section of an initscript does not contain a Default-Stop line.
notes that this line is not required if the package is not set to start by default.
The warning should be removed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpmlint against a package with an initscript with no Default-Stop: line
I think the documentation cited draws wrong conclusions/interpretations from the LSB spec. One may very well want to have a service stopped by default in some runlevels even if it is not started in any by default. The LSB specs are quite vague too, which has resulted in rpmlint drawing its own conclusions, the one of which in effect here is that there should be no need not to have a Default-Stop in all init scripts, thus it always recommends adding one in all init scripts, even if empty.
$ rpmlint -I missing-lsb-keyword
The package contains an init script that does not contain one of the LSB init
script comment block convention keywords that are recommendable for all init
scripts. If there is nothing to add to a keyword's value, include the keyword
in the script with an empty value. Note that as of version 3.2, the LSB
specification does not mandate presence of any keywords.
What about Required-Start and Required-Stop? I have the same problem (rpmlint-0.98-1.fc13).