[repo-coord] Re: mozilla epoch madness
matt at ecsc.co.uk
Wed Apr 14 11:26:34 CEST 2004
On Wed, 2004-04-14 at 08:36 +0200, Dag Wieers wrote:
> My latest and only epoch bump was accidental when I followed matt's
> package by mistake. My policy is to use Red Hat's epochs, but I can't back
> down now ;/
I never understood why it was set at 37; so every time I rebuilt I
incremented it. Most likely this has silently broken a ton of stuff, so
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.atrpms.net/pipermail/repo-coord/attachments/20040414/d18ea0a7/attachment.bin
More information about the repo-coord