This package is being added to RHEL 9.1 at the next minor release. Please remove it from epel after the next RHEL minor release.
What repo is this being added into?
It's available in CentOS Stream 9 AppStream. https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/commit/4ceab6290258b29d4c16a68b141e977a632fa891
Thanks, Carl. What could we do to make the *RHEL Process Automation* actually say that in a next bugzilla like this? I am afraid of packages being added to Buidlroot triggering this.
At the time these bugs are created, the automation/script currently has no way of knowing where the binary packages are going to show up, all it is given is the source package name. There also might be several binary packages that go into different places. Miro, I'm going to flip the question back at you. As a Red Hat package maintainer, when you request a new package and start going through the steps to add a package, do you have the information about where the binary packages will end up? I know when I see these new packages go through the CentOS Stream 9, the initial "allow this to build" part, there is no setting for binary packages. There has to be a second, manually added ticket that says where the binary packages go to. Even for modules, there isn't anyplace to put the packages in the module, that has to be added in the generic description. I'm not saying this cannot be done, I'm just saying, it might require alot of re-writting of scripts and workflows that are not ours (the EPEL community).
> As a Red Hat package maintainer, when you request a new package and start going through the steps to add a package, do you have the information about where the binary packages will end up? When we request a new package, we do need to know what repo we plan to add it to, yes. But I have personally not yet followed that process. > I'm not saying this cannot be done, I'm just saying, it might require alot of re-writting of scripts and workflows that are not ours (the EPEL community). I understand that. My only concern is that package additions to the Buildroot repo might open bugzillas to nuke them from EPEL, which would of course be a wrong thing to do.
I've retired python-tornado from EPEL 9 [0]. I've also announced it on the epel-devel mailing list [1]. [0] https://src.fedoraproject.org/rpms/python-tornado/c/afcb3d648c4d21de86ae34b17b7cc9453c0797ed?branch=epel9 [1] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/KM4I626NNMHP7DVR6U6TAZZ4JD57NP7P/