I've noticed that requesting a branch for an EPEL branch has been flaky for the past week or so - the last time, the problem seemed to resolve itself after several hours, but it just happened again so it probably should be looked at.
e.g.
$ fedpkg request-branch --repo trousers epel9 Could not execute request_branch: The connection to infrastructure.fedoraproject.org failed while trying to determine if this is a valid EPEL package. The status code was: 404
2021/01/07
Metadata Update from @humaton: - Issue tagged with: low-gain, medium-trouble, ops
@humaton can we reconsider the 'low-gain' tag? I've been trying to branch squashfuse for a few days now and it's blocking @ngompa 's work
squashfuse
$ fedpkg request-branch epel9 Could not execute request_branch: rsplit() takes no keyword arguments
seems to be showing up now.
Metadata Update from @mohanboddu: - Issue untagged with: low-gain, ops - Issue assigned to humaton - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: dev, medium-gain
fedpkg should be doing a check against centos stream api for epel9 packages.
@salimma what version of fedpkg there? It might be that it's too old to understand epel9 and it's querying the wrong place?
@jcpunk what version do you have? and if you add --repo <packagename> does it work?
$ rpm -q fedpkg fedpkg-1.41-2.el7.noarch $ fedpkg request-branch epel9 --repo json Could not execute request_branch: rsplit() takes no keyword arguments
This is being run by someone I'm mentoring who should have the right access to that repo.
This is very likely: https://pagure.io/fedpkg/pull-request/459 (epel7 fedpkg uses python2.7)
@salimma what fedpkg version do you have there?
Also, can you try and run it with --verbose when it fails?
Is this still happening?
I'll go ahead and close this. If you see it happening again please reopen and attach --verbose output or open a new ticket.
Metadata Update from @kevin: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
It's been fine recently, I suspect it's the initial volume of branching. Will provide --verbose output if it reoccurs.
--verbose
Login to comment on this ticket.