Bug 650023 - incomplete set of locale files in /usr/lib/locale/{pt_BR,bn_IN,zh_HK,en_CA,zh_TW,zh_CN,en_GB}
Summary: incomplete set of locale files in /usr/lib/locale/{pt_BR,bn_IN,zh_HK,en_CA,zh...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 640388 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-05 02:20 UTC by Danishka Navin
Modified: 2010-12-18 00:56 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-16 16:27:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Danishka Navin 2010-11-05 02:20:53 UTC
Description of problem:

yum update on fresh Fedora based remix gave following output

 Updating       : glibc-common-.12.90-18.i686                   11/271 
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/pt_BR"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/bn_IN"
/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/en_CA"
/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/zh_CN"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/en_GB"
  Updating       : glibc-.12.90-18.i686                           12/271

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Danishka Navin 2010-11-05 02:22:36 UTC
the remix was build on Fedora 14 and updated the system on 5th Nov 2010. (just few minutes ago)

Comment 2 Andreas Schwab 2010-11-05 09:56:31 UTC
rpm -qf /usr/lib/locale/pt_BR

Comment 3 Danishka Navin 2010-11-15 11:38:36 UTC
rpm -qf /usr/lib/locale/pt_BR
file /usr/lib/locale/pt_BR is not owned by any package


I clearly mentioned when i was noticed.

from my side, there is only way to reproduce. its build the remix again.
but the developer/maintainer should know how this could happen.

Btw, I don't use non of these locals and i filed this bug as a help to the community.

Comment 4 Danishka Navin 2010-11-15 11:49:05 UTC
do not depend on the bug reporter.
you could test this on F14 box at least using a VM. 

but i don't mind closing of this bug :)

Comment 5 Andreas Bierfert 2010-11-19 16:19:45 UTC
I do mind. I am still seeing this. Just now during glibc-common-2.12.90-19.x86_64 upgrade.

rpm -qf /usr/lib/locale/{bn_IN,en_CA,en_GB,pt_BR,zh_CN,zh_HK,zh_TW}
file /usr/lib/locale/bn_IN is not owned by any package
file /usr/lib/locale/en_CA is not owned by any package
file /usr/lib/locale/en_GB is not owned by any package
file /usr/lib/locale/pt_BR is not owned by any package
file /usr/lib/locale/zh_CN is not owned by any package
file /usr/lib/locale/zh_HK is not owned by any package
file /usr/lib/locale/zh_TW is not owned by any package

Comment 6 Andreas Schwab 2010-11-19 17:02:13 UTC
Fix whatever created that junk.

Comment 7 Andreas Bierfert 2010-11-19 17:12:44 UTC
Since it is appearing on glibc upgrades it might be related to glibc if not it should assigned to a different package. Being harsh and unfriendly here will not help get this fix it.

Comment 8 Mamoru TASAKA 2010-11-19 17:56:02 UTC
Well, on rawhide:

$ env LANG=C yum --disablerepo=\* --enablerepo=koji-15 whatprovides '/usr/lib/locale/zh_CN/*/*'
Loaded plugins: downloadonly
mutter-2.91.2-1.fc15.i686 : Window and compositing manager based on Clutter
Repo        : koji-15
Matched from:
Filename    : /usr/lib/locale/zh_CN/LC_MESSAGES/mutter.mo



mutter-mbl-2.31.5_1.0-1.fc15.i686 : Window and compositing manager based on Clutter
Repo        : koji-15
Matched from:
Filename    : /usr/lib/locale/zh_CN/LC_MESSAGES/mutter.mo


Then:
# env LANG=C yum --disablerepo=\* --enablerepo=koji-15 -y install mutter
....
Complete!
# rpm -Uvh --replacefiles --replacepkgs ./glibc-common-2.12.90-19.i686.rpm 
警告: ./glibc-common-2.12.90-19.i686.rpm: ヘッダ V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY
準備中...                ########################################### [100%]
   1:glibc-common           ########################################### [100%]
/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/bn_IN"
/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/en_CA"
/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/zh_CN"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/pt_BR"
# rpm -e mutter
# find /usr/lib/locale/ -type d | sort -r | while read dir ; do rpm -qf $dir &>/dev/null || rmdir $dir ; done
# rpm -Uvh --replacefiles --replacepkgs ./glibc-common-2.12.90-19.i686.rpm 
警告: ./glibc-common-2.12.90-19.i686.rpm: ヘッダ V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY
準備中...                ########################################### [100%]
   1:glibc-common           ########################################### [100%]
#

Comment 9 Owen Taylor 2010-11-22 14:16:43 UTC
Andreas: you added me to the CC because you think there's something I need to fix in the Mutter packaging? You'll need to be explicit about it, because I don't really understand the discussion above.

Comment 10 Jakub Jelinek 2010-11-22 14:26:03 UTC
The bug is that mutter* installs its *.mo files in wrong directories, *.mo belong
into /usr/share/locale/*/*.mo, but mutter incorrectly installs them into
/usr/lib/locale/*/*.mo.

Comment 11 Owen Taylor 2010-11-22 15:01:01 UTC
(In reply to comment #10)
> The bug is that mutter* installs its *.mo files in wrong directories, *.mo
> belong
> into /usr/share/locale/*/*.mo, but mutter incorrectly installs them into
> /usr/lib/locale/*/*.mo.

Thanks Jakub... /usr/lib wasn't jumping out at me in the above. Fix filed upstream as https://bugzilla.gnome.org/show_bug.cgi?id=635528 ... not planning on updating F14 at this point.

(Seems like maybe %find_lang needs a fix not to look in /usr/lib? This should have been found and caught at package build time rather than silently packaging up mo files in the wrong place.)

Comment 12 Peter Robinson 2010-11-30 14:42:29 UTC
*** Bug 640388 has been marked as a duplicate of this bug. ***

Comment 13 Mamoru TASAKA 2010-11-30 15:33:28 UTC
On rawhide, this seems fixed in mutter-2.91.3-1.fc15
On F-14, I don't know.

Comment 14 A S Alam 2010-12-16 05:46:31 UTC
Fedora 14 still have problem:
------------
Updating: glibc-common2.12.90-21.x86_64                                                                      1/12 
/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/zh_TW"
/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/pt_BR"
/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/bn_IN"
/usr/sbin/build-locale-archive: incomplete set of locale files in "/usr/lib/locale/en
----------

Comment 15 Owen Taylor 2010-12-16 16:27:48 UTC
(In reply to comment #14)
> Fedora 14 still have problem:
> ------------
> Updating: glibc-common2.12.90-21.x86_64                                        
>                              1/12 
> /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/zh_TW"
> /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/pt_BR"
> /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/bn_IN"
> /usr/sbin/build-locale-archive: incomplete set of locale files in
> "/usr/lib/locale/en
> ----------

No intention to fix for Fedora 14.

Comment 16 John Nixon 2010-12-18 00:40:12 UTC
I too have just seen this problem.

My understanding is that everybody who has mutter (i.e. GNOME Shell) installed will get an unclean install every time glibc-common is updated, which seems to be at least once a month. And presumably, the Chinese and Brazilians get GNOME Shell in English.

Given that a fix has been tested on Rawhide, why isn't this being applied to F14? Is it being queued for the next mutter update? Or is GNOME Shell just not that important?

Comment 17 Owen Taylor 2010-12-18 00:56:48 UTC
(In reply to comment #16)
> I too have just seen this problem.
> 
> My understanding is that everybody who has mutter (i.e. GNOME Shell) installed
> will get an unclean install every time glibc-common is updated, which seems to
> be at least once a month. And presumably, the Chinese and Brazilians get GNOME
> Shell in English.
> 
> Given that a fix has been tested on Rawhide, why isn't this being applied to
> F14? Is it being queued for the next mutter update? Or is GNOME Shell just not
> that important?

The Fedora 14 Mutter and GNOME Shell are roughly 6 months of active development behind the current versions, and don't really represent the current state of GNOME 3 very accurately. Because of library dependencies on newer versions of Clutter and GTK+ 3, we can't update the Fedora 14 GNOME Shell packages to the current version; maintenance updates for the old versions aren't really a high priority and are difficult because of the distance between that version and the current versions.


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