[Pkg-mailman-hackers] Re: mailman_2.1.8-1_sparc.changes REJECTED

[Joost van Baal]

Hi Lionel,

Op wo 10 mei 2006 om 07:44:24 +0200 schreef Lionel Elie Mamane:
> On Sun, Apr 16, 2006 at 05:43:51PM +0200, Lionel Elie Mamane wrote:
> > On Sun, Apr 16, 2006 at 08:17:09AM -0700, Debian Installer wrote:
> 
> >> Rejected: mailman_2.1.8-1_sparc.deb: old version (0:2.1.7-2.1.8rc1-1) in unstable >= new version (2.1.8-1) targeted at unstable.
> >> Rejected: mailman_2.1.8-1_sparc.deb: old version (0:2.1.7-2.1.8rc1-1) in testing >= new version (2.1.8-1) targeted at unstable.
> >> Rejected: mailman_2.1.8-1.dsc: old version (0:2.1.7-2.1.8rc1-1) in unstable >= new version (2.1.8-1) targeted at unstable.
> >> Rejected: mailman_2.1.8-1.dsc: old version (0:2.1.7-2.1.8rc1-1) in testing >= new version (2.1.8-1) targeted at unstable.
> 
> > That's all completely wrong:
> 
> > dmaster at bagnat:~$ dpkg --compare-versions 0:2.1.7-2.1.8rc1-1 lt 2.1.8-1 && echo yes || echo no
> > yes
> 
> > According to policy, an explicit zero epoch is exactly the same as no
> > epoch.
> 
> I downloaded katie and traced the bug back to libapt-pkg (via
> python-apt), and submitted a patch, which got applied. Version 0.6.44
> solves this error.

http://ftp-master.debian.org/reject.html says:

----

Rejected: foobar_0.8.1-5_i386.deb: Old version `0.8.1-6' >= new version
`0.8.1-5'.

Problem
    Every new upload to the archive must have a greater version number
 than existing versions in the target suite (stable, unstable).
Solution
    Increase the version number (with an epoch if necessary).
Notes
    You must increase the version number; requests to override the
version check will be refused. The reasoning behind this is simple: if
the version number does not increase, tools like dpkg, apt and dselect
will not see the package as new and will not update it. Epoch-hating has
become unfortunately trendly over the last 5 years or so, but with very
little technical justification. If there's no better way to increase the
version number: Just epoch it.

----

So perhaps there's no easy way to prevent the mailman package to go
carry 1:2.1.8-1: I suggest to upload your 2.1.8 package as 1:2.1.8-1.

Bye,

Joost

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/attachments/20060510/1397b40e/attachment.pgp