Bug 442797 - policycoreutils use sr@Latn rather sr@latin directory
Summary: policycoreutils use sr@Latn rather sr@latin directory
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Target
TreeView+ depends on / blocked
 
Reported: 2008-04-16 21:06 UTC by Robert Scheck
Modified: 2008-05-17 18:20 UTC (History)
0 users

Fixed In Version: 2.0.49-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-17 18:20:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Robert Scheck 2008-04-16 21:06:43 UTC 
Description of problem:
policycoreutils use sr@Latn rather sr@latin directory, so policycoreutils.mo is: 
/usr/share/locale/sr@Latn/LC_MESSAGES/policycoreutils.mo

> rpm -qf /usr/share/locale/sr@Latn
file /usr/share/locale/sr@Latn is not owned by any package
>

> rpm -qf /usr/share/locale/sr@latin
filesystem-2.4.13-1.i386
>

See also bug #436887 for further information.

Version-Release number of selected component (if applicable):
policycoreutils-2.0.46-3

How reproducible:
Everytime, see above.

Expected results:
Use sr@latin instead of the current sr@Latn directory for policycoreutils.
Comment 1 Daniel Walsh 2008-05-07 18:47:06 UTC 
Fixed in policycoreutils-2.0.47-2
Comment 2 Robert Scheck 2008-05-10 18:17:49 UTC 
No, it is definately not fixed:

/usr/share/locale/sr@Latn/LC_MESSAGES is needed by policycoreutils-2.0.47-3.i386
Comment 3 Bug Zapper 2008-05-14 09:32:46 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 Daniel Walsh 2008-05-14 10:54:22 UTC 
policycoreutils-2.0.47-3 did not exist until now

But you are correct it was not fixed in -2

Fixed in policycoreutils-2.0.47-3

Hopefully :^)
Comment 5 Robert Scheck 2008-05-17 18:20:58 UTC 
Yes, done. Verified in 2.0.49-2, thus closing now.
Note You need to log in before you can comment on or make changes to this bug.