Bug 2036086

Summary:	Branch and build web-assets-devel for epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Mattias Ellert <mattias.ellert>
Component:	web-assets	Assignee:	Petr Pisar <ppisar>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	nodejs-sig, ppisar, sergio, tchollingsworth
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-20 02:27:58 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:

Description Mattias Ellert 2021-12-29 17:07:03 UTC

Description of problem:

I recently built uglify-js for EPEL 9. However, the EPEL 9 build root in koji has since been redefined to strictry contain only packages in RHEL 9, and the prevoiusly available web-assets-devel was removed. So koschei now reports the uglify-js package as haviing unresolvable build dependencies.

Version-Release number of selected component (if applicable):

Package is missing.

How reproducible:

Always.

Steps to Reproduce:
1. Try to build a package for EPEL 9 that build requires web-assets-devel.

Actual results:

Failure.

Expected results:

Success.

Additional info:

The web-assets-filesystem built from the same SRPM is available in RHEL 9 and the EPEL 9 build root.

Comment 1 Petr Pisar 2022-01-10 17:16:29 UTC

There 3 binary packages:

web-assets-devel not shipped
web-assets-filesystem shipped in AppStream
web-assets-httpd not shipped

I can try to add this package, but first I need to find guide lines for the source package naming and release numbering. I recall seeing them on epel mailing list, but I cannot find it now. Do you happen to know that details?

Comment 2 Sergio Basto 2022-01-10 20:36:48 UTC

is this you are looking for ? https://docs.fedoraproject.org/tr/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 3 Petr Pisar 2022-01-11 08:50:34 UTC

That's it. The page will be updated <https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/4HBTUMG432DS7BZBBQREHJFSO7CJ7JZK/>.

Comment 4 Petr Pisar 2022-01-11 08:53:41 UTC

https://pagure.io/releng/fedora-scm-requests/issue/40744

Comment 5 Petr Pisar 2022-01-11 15:22:57 UTC

https://pagure.io/releng/fedora-scm-requests/issue/40792

Comment 6 Fedora Update System 2022-01-11 17:02:15 UTC

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

Comment 7 Fedora Update System 2022-01-12 02:11:03 UTC

FEDORA-EPEL-2022-88aba0fa95 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-88aba0fa95

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-01-20 02:27:58 UTC

FEDORA-EPEL-2022-88aba0fa95 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.