RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 857276 - glibc-common deletes any local locales on upgrade
Summary: glibc-common deletes any local locales on upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: glibc
Version: 6.3
Hardware: All
OS: All
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-14 01:50 UTC by Christoph Anton Mitterer
Modified: 2016-08-09 19:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-09 19:28:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Christoph Anton Mitterer 2012-09-14 01:50:14 UTC 
Hi.

When locale locales are used, e.g. via:
localedef -i /usr/local/share/i18n/locales/foo_BAR -c -f UTF-8 foo_BAR.UTF-8
and glibc-common is upgrade any such locale locales get deleted.

Subsequently (on reboot) any services which strictly depend on these locales break utterly, e.g. postgresql when it uses such a locale in a database; therefore the high severity.


Please automatically re-generate also the locale locales, like e.g. Debian does since ages.


Cheers,
Chris.
Comment 2 Zdenek Kabelac 2012-09-24 08:57:11 UTC 
It's not the first time my  /etc/localtime has disappeared after glibc upgrade.
After todays rawhide upgrade to

glibc-common-2.16.90-14.fc19.x86_64
glibc-2.16.90-14.fc19.x86_64

I've found out this link in  /etc

/etc/localtime.rpmnew -> ../usr/share/zoneinfo/US/Eastern

and my original  /etc/localtime  pointing to Europe/Prague was lost.

Is there any chance there will be upgrade process tested by the package maintainer before it kills rawhide user's machine?

So far the fix for my time issue was simple by adding localtime link by hand...
Comment 3 Jeff Law 2012-09-25 20:23:00 UTC 
Zdenek, the problem you're referencing is completely and totally different than the original reporter.

The handling of /etc/localtime is in a state of flux, initially due to packaging changes within glibc itself and more recently due to moving the ownership/management of /etc/localtime to systemd for F18 and beyond.
Comment 12 Carlos O'Donell 2016-08-09 19:28:53 UTC 
Red Hat Enteprise Linux 6.9 is in production phase 2, and as such only urgent priority bug fix errata will be considered. Red Hat engineering does not quality this bug as urgent. The behaviour has been present for the entire lifetime of RHEL6, and fixing it would require major restructuring of how locales are tested and deployed.

The solution is not to add the local locales to locale-archive and instead place the compiled locales in /usr/lib/locale which will be searched after the archive. Upstream Fedora is doing this to support C.UTF-8 outside of the locale-archive file.
Note You need to log in before you can comment on or make changes to this bug.