On Fri, Jan 14, 2022 at 5:31 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > > On 14. 01. 22 5:11, Orion Poplawski wrote: > > While working on EPEL9, it seems that even more packages are missing from RHEL9 > > than were in RHEL8. The latest I found was cppunit, which appears to be > > completely missing from the CS9 repos despite having been built (See > > https://kojihub.stream.centos.org/koji/packageinfo?packageID=2414) and > > presumably in the CS9/RHEL9 buildroot. > > > > So I scraped some screens from pkgs.org: > > > > Stream 9: > > > > CentOS AppStream Official x86_64 8882 > > CentOS BaseOS Official x86_64 2357 > > CentOS CRB Official x86_64 1856 > > > > Stream 8: > > > > CentOS AppStream Official x86_64 15008 > > CentOS BaseOS Official x86_64 6721 > > CentOS PowerTools Official x86_64 3771 > > > > That's a pretty big difference. Now, I don't know how many were dropped > > completely and how many are of the "buildroot only" variety. But I suspect > > there is a fair amount of the latter and so a lot of make-work ahead of us for > > EPEL9. A fairly accurate list of packages removed in RHEL 9 can be found in our RHEL 9 Adoption documentation: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9-beta/html-single/considerations_in_adopting_rhel_9/index#removed-packages_assembly_changes-to-packages > > Packaging for EPEL9 is starting to feel more and more like cleaning the Augean > > stables with RedHat piling up more manure. > > If there is any Python stuff that's in Buildroot only, let me know and I'll do > my best to persuade the maintainers to move it to CRB (but my powers are limited). I will politely point out two things. 1) The entirety of the RHEL buildroot is available in the CentOS Stream koji buildroots. I know the EPEL stewards have qualms about using it, but they are there and the technical hurdles to consume them are not large. 2) Moving content to CRB in RHEL is not a silver bullet solution in many scenarios. If it's strictly for build dependencies, CRB works well. If an EPEL package has a runtime requires on CRB content, that is less desirable. RHEL CodeReady Linux Builder (CRB) content is unsupported, not enabled by default, and not intended to be used at runtime in production. EPEL itself is clearly in the same unsupported category, but requiring another unsupported repo at runtime may lead to unintentional surprises for many users. josh _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
