[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Reminder: mailx_8.1.1-1_i386.changes was rejected



The mail copied in part below has informed me that my mailx package
upload had been rejected, because the robot does not think it is an
uptodate version, the epoch number is the cause of the trouble.

It is not clear whether the epoch component must appear explicitely in
the name of the files (with current dpkg tools, it does not) . And
even if it would appear, the comparison is not currently done
properly: "Old version `8.5.5-1' >= new version `1:8.1.1-1'". I do not
know if it is another "epoch bug" in some dpkg tool, or one that is
already fixed by one of the patch that has been posted on debian-bugs.

In the meantime,  I see three solutions:

1) choose another artificial version number that solves the
problem. Abandon the epoch number.

2) Decide that the epoch number should appear in the names of all files,
this involves some changes in the dpkg tools.

3) Decide that the epoch component never appear in the name of
directories or files, so fix the tools that do not handle this
situation gracefully.  I hope the robot that checks the upload (or is
it Guy that do this manually?) is the last step before being able to
use version with epochs. In particular, it seems that the name of the
diff file is used to deduce the version number, but the .changes file
should be trusted instead.

Any advice about what I should do now?

Perhaps some clarification should be made afterwards in the policy
manual or in the dpkg programmer manual.

Loic


> 
> Here is mailx_8.1.1-1_i386.changes:
> ========================================
> -----BEGIN PGP SIGNED MESSAGE-----
>  
>  Format: 1.5
>  Date: Mon, 23 Dec 1996 01:57:44 +0100
>  Source: mailx
>  Binary: mailx
>  Architecture: source i386
>  Version: 1:8.1.1-1
>  Distribution: unstable
>  Urgency: medium
>  Maintainer: Loic Prylli <lprylli@graville.fdn.fr>
>  Description: 
>   mailx      - A simple mail user agent.
>  Changes: 
>   mailx (1:8.1.1-1) unstable; urgency=medium
>   .
>     * recreate completely starting from OpenBSD mail version (we loose a lot
>       of extension but we have a working program now)
>     * OpenBSD base version is the last one in december 96
>     * rechange the numbering of version, so epoch 1+8.1 is from 4.4BSD, the
>       last upstream digit is to change each time we update to a new openbsd
>       version.
>     * fix the problem of longjmp inside signals inside stdio calls
>     * reincorporate a patch to be dot file locking+setgid safe
>     * some fix in signal handling
>  Files: 
>   57d2a99ee69455df60c8feb5eb0d38d6 573 mail important mailx_8.1.1-1.dsc
>   c779002cb043b57fd5198ec2032cacb0 89069 mail important mailx_8.1.1.orig.tar.gz
>   16dc4dc8bd466a77927af85b1e7e048d 10320 mail important mailx_8.1.1-1.diff.gz
>   fe7b7e2711cc038c2fb4abb86c47a6e4 97960 mail important mailx_8.1.1-1_i386.deb
> 
> and here is mailx_8.1.1-1_i386.reason, why the upload was rejected:
> ========================================
> Rejected: mailx_8.1.1-1.diff.gz: Old version `8.5.5-1' >= new version `8.1.1-1'.
>  Rejected: mailx_8.1.1-1_i386.deb: Old version `8.5.5-1' >= new version `1:8.1.1-1'.
> ========================================
> 
> If you have any questions, reply to this email.
> 
> 
> Guy
> 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com


Reply to: