On Wed, Dec 20, 2006 at 03:10:20PM +1100, Nathan Scott wrote: > > As reports of broken sid systems rose up, Andreas Barth NMUed > > your package yesterday in a 0-day NMU policy. He setup an epoch > > to the package version which IMHO is a bad thing now that we > > have the possibility of ~ in version strings. He could have used > > 2.4.35~is.2.4.32-0.1 instead of the ugly 1:2.4.32-1.1, because from > > now on, you are stuck with an epoch in your package versions.
> Oh. What is your recommendation on fixing this Andi? How do I get > past this epoch that's been thown into my previously neat and tidy > version management, and back to the simple versioning model I had? Epochs are forever. You'll need to incorporate the epoch into your versioning. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
