Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

After a long wait for fix bug #1196539 (Please ship perl-gettext package on ppc64/ppc64le/aarch64 ) .

Now we have an odd situation fully describe in the end of the bug #1443685

In https://src.fedoraproject.org/rpms/po4a/commits/epel7 , Till claim that po4a 
is now included in RHEL , I checked with dpkg and failed to build only in ppc64 [1], ppc64le/aarch64 got po4a . 

but the odd situation is that po4a is an noarch package and therefore should be easy to fix . 

The other suggestion is update po4a at least to 0.45 in rhel7-optional as you may notice [2] not even Debian oldstable have po4a-0.44


[1]
https://koji.fedoraproject.org/koji/taskinfo?taskID=21310958
https://kojipkgs.fedoraproject.org//work/tasks/961/21310961/root.log

DEBUG util.py:439:  Error: No Package found for po4a

https://koji.fedoraproject.org/koji/taskinfo?taskID=22187180 built successfully  
on aarch64, x86_64 and ppc64le

[2] 
https://tracker.debian.org/pkg/po4a

    oldstable: 0.45-1
    stable: 0.47-2
    testing: 0.47-2
    unstable: 0.51-1

po4a-0.52-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-40776a60b5

Develack+ we still need explicit pm_ack+

po4a is now included in RHEL except in ppc64, even ppc64le/aarch64 got po4a 

po4a is a noarch package, why you can't add it to ppc64 arch ? 

I can't built schroot on ppc64 !

I can't built dpkg on ppc64 !

Fixed rpm placement (add to ppc64) in  in https://code.engineering.redhat.com/gerrit/#/c/145765

Lubos

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-2018:3014