Bug 569414

Summary: Wrong directory ownership
Product: [Fedora] Fedora Reporter: Ondrej Vasik <ovasik>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: chkr, jakub, schwab
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: glibc-2.11.90-15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-14 13:44:39 UTC Type: ---
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:    
Bug Blocks: 559592    

Description Ondrej Vasik 2010-03-01 14:17:24 UTC
Based on the check done on F-12 system, your package owns directories owned by filesystem. 
This is not allowed by Fedora policies. 

See http://fedoraproject.org/wiki/Packaging/Guidelines#File_and_Directory_Ownership 
for details.

(Sub)package glibc-common:
/usr/share/locale/de
/usr/share/locale/lt/LC_MESSAGES
/usr/share/locale/gl
/usr/share/locale/lt
/usr/share/locale/tr/LC_MESSAGES
/usr/share/locale/ca
/usr/share/locale/id
/usr/share/locale/pt_BR/LC_MESSAGES
/usr/share/locale/pl/LC_MESSAGES
/usr/share/locale/rw/LC_MESSAGES
/usr/share/locale/nb
/usr/share/locale/ja/LC_MESSAGES
/usr/share/locale/tr
/usr/share/locale/pt_BR
/usr/share/locale/zh_TW
/usr/share/locale/cs
/usr/share/locale/bg/LC_MESSAGES
/usr/share/locale/id/LC_MESSAGES
/usr/share/locale/zh_CN/LC_MESSAGES
/usr/share/locale/ja
/usr/share/locale/ko
/usr/share/locale/nl/LC_MESSAGES
/usr/share/locale/es/LC_MESSAGES
/usr/share/locale/sv/LC_MESSAGES
/usr/share/locale/cs/LC_MESSAGES
/usr/share/locale/be/LC_MESSAGES
/usr/share/locale/bg
/usr/share/locale/el/LC_MESSAGES
/usr/share/locale/fr/LC_MESSAGES
/usr/share/locale/pl
/usr/share/locale/be
/usr/share/locale/hu
/usr/share/locale/da
/usr/share/locale/gl/LC_MESSAGES
/usr/share/locale/es
/usr/share/locale/zh_CN
/usr/share/locale/hr
/usr/share/locale/hr/LC_MESSAGES
/usr/share/locale/nb/LC_MESSAGES
/usr/share/locale/fr
/usr/share/locale/fi
/usr/share/locale/de/LC_MESSAGES
/usr/share/locale/en_GB/LC_MESSAGES
/usr/share/locale/ru/LC_MESSAGES
/usr/share/locale/rw
/usr/lib/locale
/usr/share/locale/sk/LC_MESSAGES
/usr/share/locale/zh_TW/LC_MESSAGES
/usr/share/locale/ru
/usr/share/locale
/usr/share/locale/el
/usr/share/locale/en_GB
/usr/share/locale/fi/LC_MESSAGES
/usr/share/locale/vi
/usr/share/locale/vi/LC_MESSAGES
/usr/share/locale/sk
/usr/share/locale/hu/LC_MESSAGES
/usr/share/locale/da/LC_MESSAGES
/usr/share/locale/it/LC_MESSAGES
/usr/share/locale/ca/LC_MESSAGES
/usr/share/locale/it
/usr/share/locale/nl
/usr/share/locale/ko/LC_MESSAGES
/usr/share/locale/sv

This is autogenerated bugzilla, I'm sorry if the problem is already fixed or reported. Additionally I apologize if that directory ownership was requested earlier by some bugzilla (some directories were probably added into filesystem package later, so your package should no longer own that directory).

Comment 1 Ondrej Vasik 2010-03-01 20:32:31 UTC
Still exists with glibc-common-0:2.11.90-12.i686 .

Comment 2 Fedora Update System 2010-03-09 16:35:14 UTC
glibc-2.11.90-15 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/glibc-2.11.90-15

Comment 3 Fedora Update System 2010-03-11 07:17:11 UTC
glibc-2.11.90-15 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update glibc'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/glibc-2.11.90-15

Comment 4 Fedora Update System 2010-03-14 13:44:05 UTC
glibc-2.11.90-15 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Andreas Schwab 2010-07-02 13:12:27 UTC
*** Bug 610256 has been marked as a duplicate of this bug. ***