On Wed, Jul 27, 2016 at 5:07 PM, Randy Barlow
As you may be aware, Bodhi 2.0 is deployed in production while Bodhi
0.9 is packaged in the Fedora and EPEL repositories. The tl;dr of
this post is that we are interested in updating the bodhi package in
EPEL 7 to the newer 2.x release series so that the client will work
with the production deployment of Bodhi. Unfortunately, the 2.x CLI is
not backwards compatible with the 0.9 series.
The incompatible upgrades policy suggests that we should instead
create a new package called bodhi2, since our reason for upgrading the
bodhi package is not security related. I'm happy to go with that policy
if the discussion here leads down that path, but I'd like to request an
exception in this case since the bodhi 0.9 CLI is not fully compatible
with the Bodhi 2 server.
What do you think?
It makes sense to me to go ahead and upgrade it. I don't know of any
other Bodhi instances out there, and frankly broken software needs to
be removed from the repos as soon as possible. It puzzles me that this
hasn't been resolved before...
真実はいつも一つ！/ Always, there's only one truth!