On Sat, Apr 15, 2006 at 03:54:27PM +0200, Goswin von Brederlow wrote: > Lionel Elie Mamane <[EMAIL PROTECTED]> writes:
>> As other people have pointed out later in the thread, my point was >> that I was _not_ having an epoch with dots in it; my version string >> was 0:1.2.7:1.2.8-1, which is explicitly allowed by policy (if there >> is an epoch, then the upstream version can contain a colon.) and >> parses as: >> - epoch: 0 >> - upstream version: 1.2.7:1.2.8 >> - Debian revision: 1 > I hope you are aware that dpkg (correctly) takes no epoch as an > implicit epoch of 0. Yes, that's what policy says the epoch semantics are. > Apt on the other hand (wrongfully) tracks explicitly if you have not > epoch or an epoch of 0. Crap. :-( I forgot to remove the explicit zero epoch from my next upload. Are you telling me that if I leave no epoch in my following upload, apt won't detect it as an upgrade? That would be unfortunate. > So better use an epoch of 1 to avoid this bug. I kinda hoped I wouldn't have to keep an epoch forever... -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
