Bug 2144190
| Summary: | Request to add it to EPEL 9 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Debarshi Ray <debarshir> |
| Component: | codespell | Assignee: | Debarshi Ray <debarshir> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | codespell-2.2.1-1.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-12-08 01:11:02 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
Debarshi Ray
2022-11-19 18:24:40 UTC
I've assigned the EPEL branch to you. I'll let you handle the updates, and reassign this bug to you for the first build. I am confused about where things exactly are at. I don't see an 'epel9' branch in dist-git. Neither here: https://src.fedoraproject.org/rpms/codespell/branches?branchname=rawhide ... nor through Git: [rishi@topinka codespell]$ git branch -r origin/HEAD -> origin/rawhide origin/f29 origin/f30 origin/f31 origin/f32 origin/f33 origin/f34 origin/f35 origin/f36 origin/f37 origin/main origin/rawhide [rishi@topinka codespell]$ Did you already request a branch using 'fedpkg request-branch': https://docs.fedoraproject.org/en-US/epel/epel-policy/#getting_fedora_packages_in_epel I am asking because I don't see a ticket asking for an epel9 branch for codespell: https://pagure.io/releng/fedora-scm-requests/issues?status=all&search_pattern=codespell&close_status= Do you want me to request a branch myself? I am happy to, but I wanted to be sure first. > I've assigned the EPEL branch to you. I'll let you handle the updates, and reassign this bug to you for the first build. This is exactly what I did, assigned the EPEL maintainership in https://src.fedoraproject.org/rpms/codespell I didn't do anything else, such as creating branches, or asking for branches to be created. Ok, I requested an epel9 branch: https://pagure.io/releng/fedora-scm-requests/issue/49299 It looks like the automated scripts only work if the Fedora owner of the package requests the EPEL branch: https://pagure.io/releng/fedora-scm-requests/issue/49299 Let's see if a human can help: https://pagure.io/releng/issue/11153 Now that Bastien made me an admin of the whole codespell package, here's another attempt at fedpkg request-branch: https://pagure.io/releng/fedora-scm-requests/issue/49451 Looks like the last attempt worked, removing myself from CC:. FEDORA-EPEL-2022-03a24db589 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-03a24db589 FEDORA-EPEL-2022-03a24db589 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-03a24db589 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-03a24db589 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |