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.

python-pygments is built but not released, meaning we cannot install ipython as it's a runtime dependency.

$ fedpkg request-branch --repo python-pygments epel9
Could not execute request_branch: This package is already an EL package, therefore it cannot be in EPEL. If this is a mistake or you have an exception, please contact the Release Engineering team.

https://gitlab.com/redhat/centos-stream/rpms/python-pygments

*** Bug 2126149 has been marked as a duplicate of this bug. ***

So this is in c9s but not in alma 9.0, so I'm guessing the package got added in the current cycle. Any idea if it can be released for the current minor release? If not, I'll push out ipython for epel9-next only until 9.1 comes out.

(In reply to Michel Alexandre Salim from comment #2)
> So this is in c9s but not in alma 9.0, so I'm guessing the package got added
> in the current cycle. Any idea if it can be released for the current minor
> release? If not, I'll push out ipython for epel9-next only until 9.1 comes
> out.

I would recommend only pushing it out for epel9-next.

epel9 is the right target.  python3-pygments is in RHEL 9 CRB.  The ipython-8.5.0-1.el9 that was in epel9-testing installs fine on RHEL 9 with CRB enabled.  It appears that Alma is missing that package in their CRB repo.

false alarm, somehow I can't see pygments from my old Alma container, but I can't repro after recreating it. Rocky CRB also has pygments. Thanks for checking Carl!