Bug 1775789
| Summary: | perl-Fsdb for epel8 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | John Heidemann <johnh> |
| Component: | perl-Fsdb | Assignee: | John Heidemann <johnh> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | epel8 | CC: | johnh, paul, perl-devel |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | perl-Fsdb-2.69-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-26 06:58:10 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
John Heidemann
2019-11-22 19:48:31 UTC
fedpkg request-repo epel8 1775789 fails with Could not execute request_repo: The Bugzilla bug provided is not the proper type It's unclear how I get epel8 added :-( *** Bug 1775788 has been marked as a duplicate of this bug. *** Request the branch as follows from your existing checkout of perl-Fsdb: fedpkg request-branch epel8 You don't need to specify a bugzilla ticket as this is not a new (to Fedora/EPEL) package. Thanks, Paul. However, fedpkg request-branch epel8 gives Could not execute request_branch: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://pagure.io/settings#nav-api-tab to get or renew your API token. For invalid or expired token refer to "fedpkg request-repo -h" to set a token in your user configuration. Could not execute request_branch: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://pagure.io/settings#nav-api-tab to get or renew your API token. For invalid or expired token refer to "fedpkg request-repo -h" to set a token in your user configuration. which seems to suggest I do fedpkg request-repo epel8 1775789 Which leads back to the error message I reported in comment 1. What am I doing wrong? No, it's saying you've got an expired Pagure token. Get a new token from https://pagure.io/settings/token/new (I usually tick all the boxes) and it goes in ~/.config/rpkg/fedpkg.conf Then try the fedpkg request without the ticket number again. Thanks. I had a non-expired token that I got for this purpose. But at your prompting I got a new token and also chmod'ed the fedpkg.conf go-rwx. One of those two things fixed it and seems to have created two tickets in fedora-scm-requests. I guess that means that this ticket was not needed (other than to get me to retry that step)? Well now that you have this ticket you can reference it in the update for the EPEL-8 package when you've built it. Yes, thank you very much. Epel8 should now be active. Yes, thank you very much. Epel8 should now be active. You still need to submit an update to get the package into epel8, just the same as you will have done for epel7. The separate build for epel8-playground does not need an update. FEDORA-EPEL-2019-bb03499a53 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bb03499a53 Thank you for the prompt in comment 10. Should now be closed. perl-Fsdb-2.69-1.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bb03499a53 perl-Fsdb-2.69-1.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report. |