Re: Beast-mcmc2 upgrade is missing class net.jsign.JsignTask

[Pierre Gruet <pgtdebian@free.fr>]

Hi again Andreas,

Le 28/09/2020 à 21:36, Andreas Tille a écrit :
> On Mon, Sep 28, 2020 at 08:23:11PM +0200, Pierre Gruet wrote:
>  
>> I have a question about "best practices": last uploaded version of
>> beast2-mcmc is 2.6.3+dfsg-2, but I will need to repack the tarball to
>> remove some convenience copies of code.
>> What would you do concerning the version number? I would consider
>> something like 2.6.3+dfsg-1 for the upstream version and 2.6.3+dfsg-1-1
>> for the Debian revision... but maybe juste removing cruft is not worth
>> increasing the version and 2.6.3+dfsg-3 would be fine for the next upload?
> 
> I would use
> 
>     2.6.3+dfsg1-1
> 
> (without the '-' between dfsg and 1).  That's something I have seen
> frequently.
>
Thanks for your advice! Nevertheless, this seems to rank before the
current version number, as

echo "2.6.3+dfsg-2,2.6.3+dfsg1-1" | tr ',' '\n' | sort --version-sort

outputs

2.6.3+dfsg1-1
2.6.3+dfsg-2

Yet I understand you mean the upstream version number should be changed.
For instance T could thus use 2.6.3+dfsg.1-1, which is a bit ugly but
sorts well. Please kindly tell me if this sound unreasonable to you.

> 
> Kind regards
>  
>      Andreas.
> 

Thanks again for the advice,
Pierre