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 pygobject3 to 3.42.2, because Gajim 1.5.1 for EPEL 9 requires at least 3.42.

Version-Release number of selected component (if applicable):
pygobject3-3.40.1-6.el9

Actual results:
pygobject3-3.40.1-6.el9

Expected results:
pygobject3-3.42.2-1.el9 or better ;-)

The technical justification was requested via https://dev.gajim.org/gajim/gajim/-/issues/11159 at Gajim upstream:

The need for having GObject.Object.run_dispose() accessible is actually https://gitlab.gnome.org/GNOME/pygobject/-/issues/470 at PyGObject upstream and the resulting commit https://gitlab.gnome.org/GNOME/pygobject/-/commit/eb5aefa615e85e023920c366225a67b602a812db landed in the 3.42.0 release for the first time.

Cross-filed case 03321090 at the Red Hat customer portal.

As RHEL 9 is based on Fedora 34 it would be expected that the EPEL 9 version of that package will be branched from the f34 branch (aka gajim 1.3.3 - https://src.fedoraproject.org/rpms/gajim/tree/f34) and not from a version that is only part of rawhide (as of today) and being pushed to Fedora 36 and 37 (currently in Bodhi).

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/

Looking at the upstream changelog in https://pygobject.readthedocs.io/en/latest/changelog.html and the amount of changes done there and also on how many packages use pygobject3 in RHEL 9 (see https://tiny.distro.builders/view-rpm--view-c9s--python3-gobject.html) the rebase is too risky. What we might accept is a merge request that will backport the required change https://gitlab.gnome.org/GNOME/pygobject/-/commit/eb5aefa615e85e023920c366225a67b602a812db into RHEL 9. It also depends on whether the pango will be updated/rebased. I'm closing this request as WONTFIX for now and it can reopened if the merge request will be opened.