Bug 2337368
| Summary: | Please branch and build uncrustify for EPEL 10 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Scott K Logan <logans> |
| Component: | uncrustify | Assignee: | Timotheus Pokorra <mailinglists> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel10 | CC: | mailinglists, mcatanza, ndbecker2 |
| 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: | 2025-01-26 20:29:12 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: | |||
| Bug Blocks: | 1225692 | ||
|
Description
Scott K Logan
2025-01-13 14:26:31 UTC
(In reply to Scott K Logan from comment #0) > Please branch and build uncrustify into EPEL 10. This package is really simple, so sure. But are there instructions for doing so somewhere? Note: this package is no longer needed as a build dependency for WebKitGTK, which is the only reason it's present in Fedora, so it may not be needed in EPEL. Hi there, thanks for the quick response. > are there instructions for doing so somewhere? I'm surprised to say this, but I can't find any EPEL-specific docs regarding this process. In general: 1. Request the branch, i.e. `fedpkg request-branch epel10` 2. A few moments later after the ticket has been processed, fetch the new branch with `git fetch` 3. Switch to the new branch and merge whichever branch you'd like to become the new EPEL 10 package, something like `git checkout epel10 && git merge rawhide` 4. Follow normal Fedora package processes, i.e. `git push && fedpkg build` and then submit the package in Bodhi > this package ... may not be needed in EPEL. My motivation for building it is to support development of ROS 2 packages on RHEL 10. We're currently targeting RHEL 9[1] and I'm trying to get RHEL 10 to parity prior to release where possible. [1] https://docs.ros.org/en/jazzy/Installation/RHEL-Install-RPMs.html The epel10 branch has been created: https://pagure.io/releng/fedora-scm-requests/issue/71484 I have built the package from the rawhide sources for Epel10: https://koji.fedoraproject.org/koji/taskinfo?taskID=127839203 I have created an update for Epel10: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-8a6e8ef0b2 (I missed linking that to this ticket) OK, thanks for handling it! This is now in Epel10: https://src.fedoraproject.org/rpms/uncrustify |