When requesting for a new dist-git repository with "fedpkg request-repo" and stored Pagure API key is experied, fedpkg prints: Could not execute request_repo: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://pagure.io/settings#api-keys to get or renew your API token. The quoted <https://pagure.io/settings#api-keys> URL does not work. Correct one is <https://pagure.io/settings#nav-api-tab>. Please fix the error message. fedpkg-1.35-1.fc28 is affected.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I believe, that this ticket is still valid, but it belongs to the different component - Pagure. I found the related message in the repo 'https://pagure.io/pagure.git pagure' at 'pagure/api/__init__.py'.
In this case it is an upstream issue, could you open a ticket at https://pagure.io/pagure we'll mark it "easyfix" and let new contributors handle it :) Thanks!
The upstream issue was opened for this: https://pagure.io/pagure/issue/4573