Matthew Palmer wrote: > On Sat, Sep 15, 2007 at 07:20:29PM -0400, Peter wrote: >> If I post this question in the wrong list please tell me where to ask >> the question :) >> >> I created an update package and it install perfectly but for one thing. >> If I install an earlier version, my package won't show up as an update. >> It's the first time this has happened. I believe I know why it doesn't >> but I don't know how to fix it :) >> >> The old version has a version as 1:2.1.1, my version is a 2.2 but >> because of the 1: in front of the earlier version that one seems to be >> preferred. >> >> In the debian/control file I added the line: >> Replaces: package ( << 1:2.1.2) >> Result was no update >> >> Changed it to: >> Replaces: package ( << 1:2.1.1) >> Result was no Update >> >> Changed it to: >> Replaces: package ( <= 1:2.1.2) >> Result was no update >> >> So what do I need to do to make my package be seen as an update? > > You need to leave the epoch (the 1:) in the version number of your new > package. Once an epoch is in place, it can never be removed as long as the > same package exists in the system. > > Policy 5.6.12 > (http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version) > will give you all the goss. > > - Matt > > OK, I get it. The reason I asked was because in the changelog at one point they removed the 1: so I thought it was possible but reading your answer explains it, they also changed the package name when they removed the 1:
Thanks for the quick answer guys -- Peter van der Does GPG Key ID: E77E8E98
signature.asc
Description: OpenPGP digital signature
