Bug 653968 - Too strict directory permissions shouldn't be an error
Too strict directory permissions shouldn't be an error
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: rpmlint (Show other bugs)
rawhide
Unspecified Unspecified
low Severity medium
: ---
: ---
Assigned To: Tom "spot" Callaway
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-16 09:37 EST by Matěj Cepl
Modified: 2011-04-25 04:11 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-04-24 21:06:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
message from autoqa (6.46 KB, message/rfc822)
2010-11-16 09:37 EST, Matěj Cepl
no flags Details

  None (edit)
Description Matěj Cepl 2010-11-16 09:37:44 EST
Created attachment 460848 [details]
message from autoqa

Description of problem:
I've got a message from autoqa@fedoraproject.org saying among other things that

spectrum.ppc: E: non-standard-dir-perm /var/run/spectrum 0700L
(and the same for /var/{log,lib}/spectrum).

I may accept that it is slightly to draconic, but upstream wants it and I don't see any hurt which would it cause to anybody.

Please, make this into warning (which should be waiveable, but that's other issue).

Version-Release number of selected component (if applicable):
what's on autoqa@fedoraproject.org today

How reproducible:
100%
Comment 1 Fedora Admin XMLRPC Client 2010-12-07 16:18:48 EST
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Tom "spot" Callaway 2011-04-24 21:06:53 EDT
The short answer here is that the check isn't that smart, nor is there any real way for it to be. It just knows that 0700L is a non-standard permission for /var/run/spectrum and /var/{log,lib}/spectrum, which is true. How should it know that in the case of spectrum, this is okay, when for another package, it would not be?

Using your own common sense here will be the best recourse. Also, in the context of autoqa, hopefully it will be possible on a per-package basis to filter out specific rpmlint errors/warnings that the packager knows to be false positives.

Closing as WONTFIX
Comment 3 Ville Skyttä 2011-04-25 04:11:40 EDT
(In reply to comment #2)
> Also, in the
> context of autoqa, hopefully it will be possible on a per-package basis to
> filter out specific rpmlint errors/warnings that the packager knows to be false
> positives.

From rpmlint POV this is technically possible, just install desired *config snippets that do the filtering to /etc/rpmlint/.  Packages can also install their own snippets there, but that doesn't work too well because the packages need to be installed before the filters take effect, so I think it'd be better if autoqa would install those files.

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