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.

While building rebase to 3.22.x packages for evolution I realized that localizations are not saved into
   /usr/share/locale/
but into
   /usr/@DATADIRNAME@/locale
instead, (the DATADIRNAME is not replaced, it's kept this way in the rpm), thus the localizations are not found and so on.

Currently known affected packages are evolution-data-server, evolution and gedit.

Kalev found a fix for intltool:
https://bazaar.launchpad.net/~intltool/intltool/trunk/revision/742

and we verified that it fixes the build.

This is somewhat blocking the rebase, thus it would be good to get it in as soon as possible.

Sandeep would you please provide qa_ack to this bz, pkovar advised you as the right person who could test.

Thanks
-Tom

From Comment 2, currently the advisory 27171 is in NEW FILES.

Requesting to move advisory 27171 back to QE state (so as to verify this bug).

(In reply to sandeep shedmake from comment #3)
> Requesting to move advisory 27171 back to QE state (so as to verify this
> bug).

I hope Kalev won't mind, I just changed state of the advisory.

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/RHEA-2017:2155