Guidance on hulahop epoch usage

Peter Hutterer peter.hutterer at
Thu Jun 2 23:39:13 UTC 2011

On Fri, Jun 03, 2011 at 02:21:14AM +0300, Jussi Lehtola wrote:
> On Fri, 3 Jun 2011 08:51:55 +1000
> Peter Hutterer <peter.hutterer at> wrote:
> > hulahop had it's Epoch bumped on the F-10 branch to
> > hulahop-1:0.4.6-5.fc10 (commit 3c3f6d12edb) to undo 0.4.7 update.
> > That epoch bump was limited to F-10, no other branches saw it afaict.
> > 
> > So anyone who ever installed the F-10 package is stuck with it.
> > Anyone else is still fine. Yum on my box claims the version available
> > on f15 is indeed the 0.7.1 currently in the repos (I never had the
> > F-10 package installed).
> > 
> > What's the correct thing to do here? Just bump the Epoch again and
> > get on with life?
> Yes, the correct way to fix this would be to set Epoch: 1 in the
> current spec file. That way version 0.7.1 would be allowed to update
> the 0.4.7 with Epoch 1.
> However, given that the problematic package only appeared in Fedora 10
> and upgrade paths are guaranteed by Fedora policy only from F(N-1) to
> F(N), I'd say that there's probably no need to fix this any more, since
> any remaining installations haven't had updates for ages and upgrading
> to a current release cleanly would require a clean reinstall anyway.

true, but anyone who would have had hulahop installed at F-10 time and did
the (guaranteed) update to F11, F12, ... F15 at the right times would still
have this issue now, right?

tbh, it seems to be corner case enough to just say "uninstall and
re-install" but nonetheless...


More information about the devel mailing list