Bug 2052738

Summary:	Please branch and build busybox in epel8 and epel9
Product:	[Fedora] Fedora	Reporter:	Davide Cavalca <davide>
Component:	busybox	Assignee:	Tom "spot" Callaway <spotrh>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	admiller, carl, dvlasenk, michel, pasik, spotrh
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	busybox-1.35.0-2.el8.next busybox-1.35.0-2.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-15 00:30:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2052737, 2052740, 2052741
Bug Blocks:	1914423

Description Davide Cavalca 2022-02-09 21:59:06 UTC

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.

Comment 1 Davide Cavalca 2022-02-09 22:25:48 UTC

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

Comment 2 Davide Cavalca 2022-02-17 17:36:49 UTC

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.

Comment 3 Davide Cavalca 2022-03-02 00:28:29 UTC

Filed stalled package ticket: https://pagure.io/releng/issue/10678

Comment 4 Tom "spot" Callaway 2022-03-02 20:17:58 UTC

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.

Comment 5 Fedora Update System 2022-03-12 00:03:57 UTC

FEDORA-EPEL-2022-59f6ebf2ce has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-59f6ebf2ce

Comment 6 Fedora Update System 2022-03-13 19:14:39 UTC

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.

Comment 7 Fedora Update System 2022-03-13 19:43:58 UTC

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

Comment 8 Fedora Update System 2022-03-15 00:30:35 UTC

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.

Comment 9 Carl George 🤠 2022-03-20 19:08:38 UTC

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.

Comment 10 Fedora Update System 2022-03-22 04:50:14 UTC

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.