Please branch and build busybox in epel8 and epel9. If you do not wish to maintain busybox in epel8 and epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/busybox/addgroup and grant it commit access, or collaborator access on epel* branches.
For libselinux-static, while we wait for it to be sorted out upstream I've requested https://pagure.io/releng/fedora-scm-requests/issue/42019 per https://docs.fedoraproject.org/en-US/epel/epel-faq/#rhel_8_has_binaries_in_the_release_but_is_missing_some_corresponding__devel_package._how_do_i_build_a_package_that_needs_that_missing__devel_package
Will you be able to branch and build busybox in epel8 and epel9? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel8 and epel9.
Filed stalled package ticket: https://pagure.io/releng/issue/10678
I'm going to go ahead and request the branches, but currently busybox just segfaults and I need to figure out why before I push it to new branches.
FEDORA-EPEL-2022-59f6ebf2ce has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-59f6ebf2ce
FEDORA-EPEL-2022-59f6ebf2ce has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-59f6ebf2ce See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2022-3835ab4dbd has been submitted as an update to Fedora EPEL 8 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-3835ab4dbd
FEDORA-EPEL-NEXT-2022-3835ab4dbd has been pushed to the Fedora EPEL 8 Next stable repository. If problem still persists, please make note of it in this bug report.
It looks like the segfault that affects the f36 build doesn't affect the epel9 build. [root@f36-container:~]# rpm -q busybox busybox-1.35.0-2.fc36.x86_64 [root@f36-container:~]# busybox pwd Segmentation fault (core dumped) [root@c9s-container:~]# rpm -q busybox busybox-1.35.0-2.el9.x86_64 [root@c9s-container:~]# busybox pwd /root The were built from the same commit.
FEDORA-EPEL-2022-59f6ebf2ce has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
It appears as as if busybox is available in EPEL for EL9 but EPEL Next for EL8. Does anyone know why?
I checked with Davide who added it to EPEL 8 Next, but he doesn't remember why. I went ahead and rebuilt the EPEL 8 Next package in EPEL 8 with a release bump for a correct update path and to keep the package present for EL8 users after the EPEL 8 Next retirement. I also confirmed that this EL8 build didn't suffer from the segfault that was present in F36. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-a72ce6bcf2