On Mon, Mar 11, 2019 at 7:35 AM Daniel P. Berrangé berrange@redhat.com wrote:
On Fri, Mar 08, 2019 at 03:07:09PM -0500, Kaleb Keithley wrote:
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.
The ability to have multiple different builds of the same software which users can choose between, sounds alot like the use case for modularity. Abusing Epoch to try to address this kind of situation feels like a pretty undesirable approach, as this problem with suddenly clashing Epochs will illustrate.
If ceph in Fedora were a module, is it possible for Ceph upstream to provide an alternate module stream of ceph too ? If so, then users could use the normal modules features in DNF for deciding which stream to have active on their systems.
If there was a material difference between upstream and downstream, you might have a case for it. Today, there is not. Heck, the spec file that is in Fedora is basically an openSUSE spec with Fedora conditionals in it. It even has the (IMO dumb) license header thing that openSUSE forces for all of its package spec files.
Not that it's necessarily a bad thing that the spec files are identical, but I'd rather just say we should not care, since there's no appreciable difference between the two.