Bug 2374524
| Summary: | Please branch and build sox in epel10.0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | keenonkites |
| Component: | sox | Assignee: | Jiri Kucera <jkucera> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel10 | CC: | felix, hhorak, jkucera, zonexpertconsulting |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | sox-14.4.2.0-42.el10_1 sox-14.4.2.0-42.el10_0 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-07-11 00:22:53 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
keenonkites
2025-06-24 08:37:39 UTC
Non-responsive maintainer check has been created: https://bugzilla.redhat.com/show_bug.cgi?id=2375333 While this bug has been created just recently, the following bug was created earlier (hence the non-responsive check): https://bugzilla.redhat.com/show_bug.cgi?id=2369788 FEDORA-EPEL-2025-2c8be96ce2 (sox-14.4.2.0-42.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2c8be96ce2 Should be done now. FEDORA-EPEL-2025-2c8be96ce2 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2c8be96ce2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. hey Jiri - Can you build this for EPEL 10.0 as well as EPEL 10.1? Hello, I see that EPEL 10.1 has been chosen by default. I am trying to find some guide how to backport builds also for EPEL 10.0 but did not found any. Hi Jiri - I just went through this and had the exact same question. The description of how EPEL 10 branches are handled is shown here: https://docs.fedoraproject.org/en-US/epel/branches/#_epel_10 However, it doesn't tell us what we need to do from the commandline. For me, the missing step was: >fedpkg request-branch epel10.0 That will create the 10.0 branch and allow you to build the package in the same way you did for the 10.1 branch. At the time, I didn't know if I was supposed to request the branch (we don't have to for Fedora), or whether a period of underscore was needed in the branch name. Once the package is in the latest "rawhide" branch (today that 10.1), it should get built automatically when 10.2 is branched. Hope that helps. Hi Andrew, thanks, yes, it should be similar how CentOS Stream workflow works now. I suppose that `fedpkg request-branch` (or the server with Pagure itself) has some branch name checking mechanism. I will try to investigate. From the link you provided it seems that `epel10.0` is the branch name from which the dist tag `.el10_0` is derived. As for now, `epel10` means `epel10.1`, then it will mean `epel10.2` and so on. FEDORA-EPEL-2025-d11c6f5620 (sox-14.4.2.0-42.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d11c6f5620 FEDORA-EPEL-2025-d11c6f5620 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d11c6f5620 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2025-2c8be96ce2 (sox-14.4.2.0-42.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-d11c6f5620 (sox-14.4.2.0-42.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report. |