Re: Re: mozilla epoch madness

Matthew Hall wrote:

> Is there any clean way to resolve all this? 
> 
> For my repo, I'm thinking, do a mozilla rebuild with an epoch of 37,
> which obsoletes the current epoch of 52 (eek), and increment the
> release. Something like:
> 
> Obsoletes: mozilla = 52:1.6-1
> 
> I'm not even sure if that'd work, so if anyone has any better ideas, i'm
> open to suggestions.

I don't believe that will work, because in the latest rpm packages, 
Obsoletes (at least sometimes) fails:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116299

Only 2 alternatives as I see it:
1.  (Re)build with Epoch 37, and force folks with existing 37+ pkgs to 
downgrade
2.  (Re)build everything with an inflated Epoch 38 (or 52!) so everyone 
gets on the same page.

-- Rex