Bug 1001409

Summary: incomplete local warnings when install glibc-common
Product: [Fedora] Fedora Reporter: Henrique Martins <fedora>
Component: glibcAssignee: Carlos O'Donell <codonell>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 19CC: codonell, fweimer, jakub, law, pfrankli, schwab, spoyarek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-27 02:58:27 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:

Description Henrique Martins 2013-08-27 02:11:21 UTC 
Description of problem:
When installing glibc, glibc-common (I believe) spits out warnings of incomplete locales:
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/zh_CN"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/en_CA"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/en_GB"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/zh_HK"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/zh_TW"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/pt_BR"
Not sure if this means I'm missing something else or some dependency is not being enforced, or even whether that this is just a innocuous warning.

Version-Release number of selected component (if applicable):
glibc-common-2.17-14.fc19.x86_64
Also in 2.17-13, maybe even back further but I never noticed it.

How reproducible:
Happen when installing 2.17-13 and -14


Steps to Reproduce:
1. yum update glibc to any of those

Actual results:
warning messages above

Expected results:
clean update?

Additional info:
Comment 1 Siddhesh Poyarekar 2013-08-27 02:58:27 UTC 

*** This bug has been marked as a duplicate of bug 960815 ***
Comment 2 Carlos O'Donell 2013-09-09 19:32:10 UTC 

*** This bug has been marked as a duplicate of bug 1000162 ***