Packaging Committee: either rpmlint is correct, or the guidelines are correct; but at the moment they conflict. Please see this bugzilla and review.

Thanks, Matt

-- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux

-----Original Message----- From: bugzilla@redhat.com [mailto:bugzilla@redhat.com] Sent: Mon 4/13/2009 3:42 PM To: Domsch, Matt Subject: [Bug 495529] rpmlint incorrect warning for missing-lsb-keyword Default-Stop

Please do not reply directly to this email. All additional

comments should be made in the comments box of this bug.

https://bugzilla.redhat.com/show_bug.cgi?id=495529

Ville Skyttä ville.skytta@iki.fi changed:

What |Removed |Added

----------------------------------------------------------------------------

Status|NEW |CLOSED

Resolution| |NOTABUG

--- Comment #1 from Ville Skyttä ville.skytta@iki.fi 2009-04-13 16:42:46 EDT ---

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

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.