1. Creating new packages has become (more of) a pain since the
retirement of pkgdb2. I know I keep complaining about needing to
manually fetch Pagure API keys, but it is actually extremely annoying
when I go to request a repo and realize I need to first request a new
API key before doing anything else. The problem isn't the workflow,
per se, but the infrastructure: reviews could really use a better
platform than bugzilla. If reviews were more integrated into the
tooling, automatic checks like fedora-review could maybe be ran
automatically. Maybe approving a new package could even automatically
create the repository, without the requestor having to do anything!
This is a big one for me and I think part of the problem is we have both
src.fedoraproject.org (a pagure instance) and
pagure.io, which also is specifically for fedora but not in the
fedoraproject.org domain. Then I get emails telling me my API key is about to expire and there's no links i the notification and I'm not entirely sure which pagure instance it is.
THEN once I create new keys, because it's often enough to be annoying but not often enough to remember, I don't know which file to put it in...
.config/fedrepo_req/config.ini ?
or
.config/rpkg/fedpkg.conf ?
And google was almost useless this last time, "man fedpkg" was no help either I had to run:
$ fedpkg request-repo --help
To get the answer...
Thanks,
Richard