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 1691534 - glibc: Binary locale files vary within a mutilib set e.g. x86_64/i686 and should not.
Summary: glibc: Binary locale files vary within a mutilib set e.g. x86_64/i686 and sho...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: DJ Delorie
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1710258
TreeView+ depends on / blocked
 
Reported: 2019-03-21 20:18 UTC by DJ Delorie
Modified: 2020-03-31 19:08 UTC (History)
8 users (show)

Fixed In Version: glibc-2.17-301.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:08:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0989 0 None None None 2020-03-31 19:08:51 UTC
Sourceware 24372 0 'P2' 'RESOLVED' 'Binary locale files are not architecture independent' 2019-11-27 09:41:26 UTC

Description DJ Delorie 2019-03-21 20:18:23 UTC
This bug was initially created as a copy of Bug #1311954


The binary locale files of glibc should be multilib independent,
but they are not.

Carlos O’Donell: “... the fact that they don't match means there is an upstream ABI bug.”

To test whether they match or not, I did this:

I built glibc from the current f23 branch here:

http://koji.fedoraproject.org/koji/taskinfo?taskID=13113924

Then downloaded:

https://kojipkgs.fedoraproject.org//work/tasks/3923/13113923/glibc-common-2.22-10.fc23.x86_64.rpm
https://kojipkgs.fedoraproject.org//work/tasks/3924/13113924/glibc-common-2.22-10.fc23.i686.rpm

unpacked the rpms and checked whether locale-archive.tmpl differ.

They do differ:

mfabian@ari:~/tmp/glibc-locale-subpackaging
$ diff {i686,x86_64}/usr/lib/locale/locale-archive.tmpl
Binary files i686/usr/lib/locale/locale-archive.tmpl and
x86_64/usr/lib/locale/locale-archive.tmpl differ
mfabian@ari:~/tmp/glibc-locale-subpackaging
$

And not only a little bit:
mfabian@ari:~/tmp/glibc-locale-subpackaging
$ cmp -l {i686,x86_64}/usr/lib/locale/locale-archive.tmpl |wc
3084277 9252831 55516986
mfabian@ari:~/tmp/glibc-locale-subpackaging
$

Comment 8 Sergey Kolosov 2019-10-09 11:16:10 UTC
Verified, the file /usr/lib/locale/locale-archive.tmpl is the same on i686 and x86_64 architectures.

Comment 10 errata-xmlrpc 2020-03-31 19:08:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0989


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