|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
cqi commented 7 years ago | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
pingou commented 7 years ago So what if fedpkg is updated but not the bodhi client? :) | ||
bowlofeggs commented 7 years ago bodhi 2.1.9 has never been released into any version of Fedora or EPEL yet. My original plan was to coordinate a release of fedpkg and bodhi to Rawhide in the same push, but the purpose of this patch is to make that unnecessary. This patch will make it possible (and the preferred path) for fedpkg to be updated in all platforms first, and then later release bodhi 2 into Rawhide and EPEL 7. At this time, I plan to leave bodhi at 0.9 in EPEL 6 and Fedoras 23-25, since it is a backwards incompatible update. I have permission from the EPEL steering committee to release the backwards incompatible update to EPEL 7. | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
This commit modified fedpkg to detect the installed version of the
bodhi CLI, and then use the appropriate bodhi command to create
the update.
This will allow fedpkg to be installed on a variety of OS versions
with differing bodhi client versions.
Signed-off-by: Randy Barlow randy@electronsweatshop.com
Better use
pyrpkg.rpkgError
instead ofException