There are 4 packages that are in epel9 that were also released with RHEL 9.0. This isn't that big of a surprise, we knew about them. Three managed to get branched and built before we had the check in place. One had a race condition with the build in RHEL.
Two are easy to remove: ** pybind11 - Nothing in epel9 currently depends on it. - I will remove it today - https://bugzilla.redhat.com/show_bug.cgi?id=2091185 ** tesseract - Although a few things depend on it in epel9, nothing depends on it's specific version. - I will remove it today. - https://bugzilla.redhat.com/show_bug.cgi?id=2091183 Two are harder ** libwmf - epel9 release version is lower than RHEL, thus doesn't get installed. - RHEL is missing libwmf-devel, thus things that depend on it to build, will not be able to once it is removed. - I did a check and nothing depends on libwmf-devel in runtime or buildtime. But I know that sometimes the buildtime checks don't always work. - I am waiting a week (possibly two) before I remove this package. - https://bugzilla.redhat.com/show_bug.cgi?id=2091184 ** tesseract-tessdata - epel9 release version is lower than RHEL, thus doesn't get installed. - There are about 150 binary sub-packages that get built, but RHEL 9.0 only releases 2 of them. The epel9 version has all of them. Thus, removing this package is rather huge. - My opinion is that we get it moved over to tesseract-tessdata-epel and built it without those two packages that RHEL provides. Troy
_______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
