Bug 2032256
| Summary: | Branch and build beep in epel9 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Neal Gompa <ngompa13> |
| Component: | beep | Assignee: | Hans Ulrich Niedermann <rhbugs> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | carl, davide, daxelrod, fedora, matt, michel, rhbugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | beep-1.4.11-2.el9 beep-1.4.11-2.el7 beep-1.4.11-2.fc34 beep-1.4.11-2.el8 beep-1.4.11-2.fc35 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-20 02:28:52 UTC | Type: | --- |
| 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: | 1914423 | ||
|
Description
Neal Gompa
2021-12-14 09:21:25 UTC
Will do when I find the time to figure out how to do that. It's pretty simple: https://docs.fedoraproject.org/en-US/epel/fedora-package-in-epel/#the_procedure_for_getting_a_package_in_epel `fedpkg request-branch <branch>`? Does not say what the actual branch name in this namespace is. "el9"? "epel9"? Guessing "epel9". `fedpkg request-branch epel9` then says I need to `fedpkg set-pagure-token`. Does not say what that API token actually needs to do: Blanket all permissions or something specific? Guessing "create ticket" on https://pagure.io/settings/token/new... $ fedpkg set-pagure-token .... ERROR: User config file not found at: /home/user/.config/rpkg/fedpkg.conf $ mkdir ~/.config/rpkg $ chmod 0700 ~/.config/rpkg $ touch ~/.config/rpkg/fedpkg.conf $ chmod 0600 ~/.config/rpkg/fedpkg.conf $ fedpkg set-pagure-token .... https://pagure.io/releng/fedora-scm-requests/issue/41071 $ _ Finally. Pretty simple indeed. :-) Anyway, I expect the following two steps until this can be closed: * wait for the epel9 branch creation ticket to be resolved * run `fedpkg build` on epel9 branch, and maybe create a bodhi update FTR, all three tickets: epel7: https://pagure.io/releng/fedora-scm-requests/issue/41073 epel8: https://pagure.io/releng/fedora-scm-requests/issue/41072 epel9: https://pagure.io/releng/fedora-scm-requests/issue/41071 FEDORA-2022-0d7b3c1ed9 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0d7b3c1ed9 FEDORA-2022-d56626616b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d56626616b FEDORA-EPEL-2022-ac857a2b3b has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ac857a2b3b FEDORA-EPEL-2022-471f181d53 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-471f181d53 FEDORA-EPEL-2022-985b2a7cf7 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2022-ac857a2b3b has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-0d7b3c1ed9 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2022-471f181d53 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-d56626616b has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |