Bug 498107 - incoherent-subsys: incorrectly parsed name
incoherent-subsys: incorrectly parsed name
Product: Fedora
Classification: Fedora
Component: rpmlint (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-28 17:05 EDT by Pavel Alexeev
Modified: 2009-09-13 17:43 EDT (History)
3 users (show)

See Also:
Fixed In Version: 0.89-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-13 17:43:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pavel Alexeev 2009-04-28 17:05:07 EDT
$ rpmlint RabbIT-3.18-7.fc9.noarch.rpm | grep incoherent-subsys
RabbIT.noarch: E: incoherent-subsys /etc/rc.d/init.d/rabbit RabbIT}

# grep RabbIT} /etc/rc.d/init.d/rabbit

Rpm used in example from review - https://bugzilla.redhat.com/show_bug.cgi?id=492810

Version-Release number of selected component (if applicable):
$ rpm -q rpmlint
Comment 1 manuel wolfshant 2009-04-29 00:31:52 EDT
What makes you think that /etc/rc.d/init.d/rabbit is a good name for the init script, but that the lock file should be /var/lock/subsys/RabbIT rather than /var/lock/subsys/rabbit ?
Comment 2 Ville Skyttä 2009-04-29 12:01:26 EDT
Besides that, there is a real parsing deficiency - note the "}" in "RabbIT}".  Hacked around upstream, will most likely be in the next rpmlint release: http://rpmlint.zarb.org/cgi-bin/trac.cgi/changeset/1584
Comment 3 Pavel Alexeev 2009-05-01 08:50:11 EDT
manuel wolfshant, I think name of lock-file for RabbIT is absolutely is not subject of this bug. If you want diccuss about it, we can do it in its Review Request: https://bugzilla.redhat.com/buglist.cgi?quicksearch=RabbIT

Ville Skyttä, off course I speek about incorrect parsing "}" at the and. And thank you for the fixing.

If it fixed may be bug should be closed as NEXTRELEASE?
Comment 4 Ville Skyttä 2009-05-02 05:01:12 EDT
I'll close this bug when the fix is actually shipped in Fedora packages instead of just upstream svn, if that's fine with you.
Comment 5 Pavel Alexeev 2009-05-02 05:17:01 EDT
As you want.
Comment 6 Bug Zapper 2009-06-09 23:41:35 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Note You need to log in before you can comment on or make changes to this bug.