Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 1182307

Summary: incorrect specification of ghost file mlocate.db in mlocate package
Product: Red Hat Enterprise Linux 5 Reporter: Paulo Andrade <pandrade>
Component: mlocateAssignee: Michal Sekletar <msekleta>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.11   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-10 08:11:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1182304, 1182306, 1185798    
Bug Blocks:    

Description Paulo Andrade 2015-01-14 20:23:50 UTC
The mlocate rpm correctly defines mlocate.db to be a ghost file. However it is incorrectly stated that this file is owned by group root and that the mode is 644. When updatedb runs it creates the files with group slocate and mode 640.
This leads to rpm verification errors, which lead to failed compliance checks.

This bug may be present in other RHEL versions as well.

A simple mlocate.spec pseudo patch would be:

-%ghost %{_localstatedir}/lib/mlocate/mlocate.db
+%ghost %attr(0640,root,slocate) %{_localstatedir}/lib/mlocate/mlocate.db

Comment 1 RHEL Program Management 2015-01-15 08:47:58 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 2 Michal Sekletar 2015-07-10 08:11:30 UTC
Fixing this trivial/cosmetic issue via z-stream would be just waste of everyone's time.