fedpkg

#187 fedpkg request-branch should use pdc or something else instead of bodhi
Closed: Fixed Opened by mohanboddu.

Closed: Fixed
Reopen Issue

https://pagure.io/fedpkg/blob/master/f/fedpkg/utils.py#_100 is using bodhi to find releases/branches to request, but during mass branching bodhi is not activated, it is activated 2 weeks(beta freeze) after mass branching, which creates the issue of not able to request new branches for those 2 weeks or so.

Here's the schedule of f28 for reference: https://fedoraproject.org/wiki/Releases/28/Schedule

It also uses fedora.client.bodhi, which has been deprecated for more than a year and could be removed at any time. The bodhi client now lives at bodhi.client.bindings.

I'll take this ticket.

@bowlofeggs it seems like we can't use Bodhi for this purpose, so the use of fedora.client.bodhi will be inherently removed as part of this PR.
Edited by mprahl

PR #188 fixes this

@mprahl Thanks for the fix. Would you mind to click the Take button to assign this issue to you?

@cqi I don't have rights to assign the ticket to myself.

Commit 00aed529 fixes this issue

--all-releases is now erroneously requesting f24 branches; not sure how to report that on PDC (as I assume that's the real problem.)

@qulogic thank you for reporting this. I submitted a ticket to get this data fixed in PDC at:
https://pagure.io/fedora-infrastructure/issue/6784

Metadata Update from @cqi:
- Issue set to the milestone: 1.32
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.