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.

As part of the desktop rebase in 7.6, we need to rebase orca to the version that is shipped with GNOME 3.28.

Wondering how we are going to solve python3 issue?

(In reply to Tomas Pelka from comment #2)
> Wondering how we are going to solve python3 issue?

Was seemingly enough to drop the ([3.3]) from the AM_PYTHON in configure.ac …

I kind of jumped the gun. it built, but doesn't run.

Some of the porting changes are pretty small (changing chr to unichr, renaming urllib.parse to urlparse, that kind of thing).  it also uses a faulthandler module that's available in python2 but we don't ship it.  That could be stripped out pretty easily.

It's a bunch of small changes, but adds up. I think we should backpedal and avoid rebasing after all.  I'll untag the build and revert it in version control.

okay untagged and reverted. devnak for 7.6

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.