This package is being added to RHEL 9.2 at the next minor release. Please remove it from epel after the next RHEL minor release.
The capstone package is now available in c9s AppStream: $ repoquery -q --repo=c9s-appstream capstone capstone-0:4.0.2-10.el9.i686 capstone-0:4.0.2-10.el9.x86_64 The capstone package is now available in c9s CRB: $ repoquery -q --repo=c9s-crb capstone-devel capstone-devel-0:4.0.2-10.el9.i686 capstone-devel-0:4.0.2-10.el9.x86_64 (It should not be removed from EPEL right away, but rather when RHEL 9.2 is released).
s/The capstone package is now available in c9s CRB/The capstone-devel package is now available in c9s CRB/
package retired in EPEL9
> (It should not be removed from EPEL right away, but rather when RHEL 9.2 is released). This is/was really critical. Retiring capstone in EPEL9 has just doomed everyone who has RHEL 9.1 deployed today and needs capstone. For example this has broken upstream CI for the virtualization stack which is tested on almalinux:9 container images. Is it possible to un-retire it ? Ideally the version added to RHEL (and c9s) should have been given a Release field which was greater than that in EPEL. That would have ensured the RHEL version was preferred, even if it still existed in EPEL.
> Retiring capstone in EPEL9 has just doomed everyone who has RHEL 9.1 deployed today and needs capstone. As a temporary workaround, RHEL9 and RHEL9 rebuild users can install the CentOS 9 RPM from the appropriate koji URL, e.g.: dnf install https://kojihub.stream.centos.org/kojifiles/packages/capstone/4.0.2/10.el9/x86_64/capstone-4.0.2-10.el9.x86_64.rpm Other links (different architectures or subpackages) can be found here: https://kojihub.stream.centos.org/koji/buildinfo?buildID=24878 > Is it possible to un-retire it ? Yes, but it's probably not worth it considering we're only a few months away from RHEL9.2 being released, per the six month minor release approximate schedule. If the maintainer wants to pursue that the process is basically just steps 4 and 5 from here: https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming > Ideally the version added to RHEL (and c9s) should have been given a Release field which was greater than that in EPEL. That would have ensured the RHEL version was preferred, even if it still existed in EPEL. It did have a greater release. The last EPEL 9 build was 4.0.2-9.el9, and the first C9 build is 4.0.2-10.el9. This is why it was originally stated that it shouldn't be retired until RHEL9.2 is released, implying that the overlap between EPEL9 and C9 was acceptable short term while waiting for RHEL9 to catch up.
For the record, I find bugzillas like this harmful. Discussion: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/LUWUIN5BRPJZGVB5PIH625PFV6IBD6YO/
(In reply to Carl George 🤠 from comment #6) > > Retiring capstone in EPEL9 has just doomed everyone who has RHEL 9.1 deployed today and needs capstone. > > As a temporary workaround, RHEL9 and RHEL9 rebuild users can install the > CentOS 9 RPM from the appropriate koji URL, e.g.: > > dnf install > https://kojihub.stream.centos.org/kojifiles/packages/capstone/4.0.2/10.el9/ > x86_64/capstone-4.0.2-10.el9.x86_64.rpm > > Other links (different architectures or subpackages) can be found here: > > https://kojihub.stream.centos.org/koji/buildinfo?buildID=24878 > > > Is it possible to un-retire it ? > > Yes, but it's probably not worth it considering we're only a few months away > from RHEL9.2 being released, per the six month minor release approximate > schedule. That is the wrong way to think about RHEL. Many of the organizations who deploy RHEL are very conservative about updating to new releases. It would not be unexpected for orgs to stay on 9.1, even deploying new 9.1 servers, for 6-12 months (or more) *after* 9.2 is released. They have organizational processes to certify new distro releases, and integrate 3rd party software that may only be supported by the vendor on certain releases that take time. But this is all getting beyond the scope of this ticket, probably needs to go to the mailing list instead. > If the maintainer wants to pursue that the process is basically > just steps 4 and 5 from here: > > https://docs.fedoraproject.org/en-US/package-maintainers/ > Package_Retirement_Process/#claiming > > Ideally the version added to RHEL (and c9s) should have been given a Release field which was greater than that in EPEL. That would have ensured the RHEL version was preferred, even if it still existed in EPEL. > > It did have a greater release. The last EPEL 9 build was 4.0.2-9.el9, and > the first C9 build is 4.0.2-10.el9. This is why it was originally stated > that it shouldn't be retired until RHEL9.2 is released, implying that the > overlap between EPEL9 and C9 was acceptable short term while waiting for > RHEL9 to catch up. Oh yes, I mis-interpreted what I was looking at. So there wasn't any reason to retire the EPEL branch at all. It just needed to be left in a read-only state thereafter.
I am sorry for the troubles ... and it is limiting me as well rebuilding other packages depending on capstone - radare2 for example. I do not have access to RedHat commercial feed for RHEL9 to check whether 9.2 minor release is already out and whether in some branch it really contains capstone. So I was getting the information from Miro that it is already available in Centos as a measure that we should remove it from EPEL as well. So please can we unretire the package in EPEL9 ?
I apologize if "The capstone-devel package is now available in c9s CRB ... it should not be removed from EPEL right away." was confusing. New RHEL 9 packages appear in c9s (CentOS 9 Stream) before they appear in RHEL 9, but packages should be removed from EPEL 9 only after they appear in RHEL 9. It's a tad tricky. ----- Anyway, https://pagure.io/releng/issue/11297
Package is back in epel9 repository - thanks Miro for help.
Reopening for the actual retirement once RHEL 9.2 is out, which still hasn't happened. DO NOT RETIRE IT YET.
I have verified that capstone is in RHEL 9.2 I have ran the fedpkg retire for capstone on epel9. I will close this ticket when it is no longer in epel9
capstone is no longer in epel9. Thank you for your work work on capstone on epel9.