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.
Description of problem:
Please rebase pango to 1.50.10, because Gajim 1.5.1 for EPEL 9 requires at least 1.50.
Version-Release number of selected component (if applicable):
pango-1.48.7-2.el9
Actual results:
pango-1.48.7-2.el9
Expected results:
pango-1.50.10-1.el9 or better ;-)
Do you know why gajim-1.5 requires pango-1.50?
I wonder if maybe you can patch it for epel9 to allow the older stable pango there?
(We are considering a Emoji update for RHEL9 which would probably come to pango too as a backport.)
Thanks Robert for investigating.
Perhaps you want to try and see what the impact might be on 1.5.
I wonder how much gajim uses that feature.
Anyway I would still suggest to start by building an older version first for gajim for epel9 now.
Generally we are not planning to rebase Gnome GUI stack components in RHEL 9,
at least without a strong reason to do so.
(Also just noting that 1.50.10 only landed in Fedora a few days ago:)
Anyway we will discuss this also with Desktop etc.
There is already an older gajim version in EPEL 9, however I really would like to rebase to gajim 1.5.x due to its major UI improvements for users (including business/corporate/enterprise usage), see: https://gajim.org/post/2022-09-19-gajim-1.5.0-released/
We are afraid that with the amount of changes seen since pango 1.48.7
(https://gitlab.gnome.org/GNOME/pango/-/blob/main/NEWS)
such a large rebase of pango seems too risky for RHEL
even at this point in the lifecycle. It will almost
certainly cause some rendering changes to occur in some
situations which we can't justify within minor releases.
Our RHEL desktop strategy really focuses on maintaining
stability and also for that reason we are not doing
general rebases to newer Gnome versions within
a RHEL major release these days.
Comment 8RHEL Program Management
2022-12-12 09:06:43 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.