DevHeads.net

On not bumping the epoch in ceph-14, f30 and f31/rawhide

The epoch was inadvertently bumped (not by me) when ceph was rebased to
14.x in f30/rawhide.

I reset it to 1 in subsequent builds. Now adamwill is running builds with
it bumped to 2 again.

I would prefer that it not be bumped. Ceph has their own builds (for Fedora
even I think) where they have epoch=2. I see this as a feature that lets
someone install Ceph's epoch=2 packages on a system and not risk
inadvertently updating with the Fedora Ceph packages.

Is there really no other way to get rid of the one or two "bad builds"
where epoch=2 and keep shipping epoch=1 in Fedora? By untagging the builds
perhaps?

Thanks,

Comments

Re: On not bumping the epoch in ceph-14, f30 and f31/rawhide

By King InuYasha at 03/08/2019 - 15:16

On Fri, Mar 8, 2019 at 3:08 PM Kaleb Keithley < ... at redhat dot com> wrote:
As of right now, no. Once it goes out in a compose, that's the way it goes...

I really wish we'd allow Epochs to be reset on distribution upgrades.
With dnf distro-sync (which is used by system-upgrade) Epochs don't
really matter and upgrades work as intended anyway...

And EVR games like this are really annoying. :(