Metadata Update from @jnsamyak: - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
The package is now unretired. For missing branches please use $fedpkg request-branch
$fedpkg request-branch
pgbouncer epel10.1 orphan pgbouncer f42-Beta fab pgbouncer f44 orphan
Metadata Update from @jnsamyak: - Issue untagged with: low-gain, low-trouble, ops - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Hi,
Sorry for the delay.
$ fedpkg request-branch epel10.1 Could not execute request_branch: epel10.1 is release branch, but not active
What am I doing wrong?
Thanks!
Metadata Update from @devrim: - Issue status updated to: Open (was: Closed)
Let me check, the inital request was regarding the unretirement for the rawhide branch. I'll look for epel 10.1
2025-08-25 16:02:05,982 [ERROR] koji: GenericError: package pgbouncer NOT blocked in tag epel10.1
It is not blocked, try again once?
Oh no my bad, I see why this is happening, the epel10.1 will be branched today and will be done by the members of epel team, so you might have to wait till it happens, because there are no slas implemented for epel10.1 yet hence, you can't request one now. It will automatically going to reflect one more branch, as soon, as the branching happens, if your package is active.
For more information, refer this resource:
Howdy EPEL packagers, Release Engineering will branch epel10.1 from epel10 on 2025-08-25 (one week from today), in accordance with our overall branching strategy for EPEL 10. https://docs.fedoraproject.org/en-US/epel/branches/#_epel_10 During the branching, we will temporarily disable builds to the epel10-candidate target, which is used when you run fedpkg build from the epel10 branch. If you are trying to create a build and receive an error about a target not existing, please try again later. We will send announcements when the branching is starting and when it is completed. Thanks in advance for your patience.
Metadata Update from @jnsamyak: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)