Re: fixing rc-version-greater-than-expected-version
On 07/30/2012 04:17 PM, Andreas Tille wrote:
> On Mon, Jul 30, 2012 at 02:49:36PM +0200, Alex Mestiashvili wrote:
>
>> I just imported the new upstream version for bowtie2 and now lintian
>> gives me the following warning:
>>
>> N: Processing binary package bowtie2 (version 2.0.0-beta7-1, arch i386) ...
>> W: bowtie2: rc-version-greater-than-expected-version 2.0.0-beta7 > 2.0.0
>> (consider using 2.0.0~beta7)
>>
>> In general the message is totally clear 2.0.0-beta7 is higher than
>> 2.0.0, but if I consider using 2.0.0~beta7 then my updated version will
>> become lower than any previous version.
>> Ffor example:
>>
>> dpkg --compare-versions 2.0.0-beta6-1 gt 2.0.0~beta7-1 &&echo $?
>>
>> returns 0 exit code...
>>
> Well, at some point in time you somehow did a bad choice for the RC
> versions (and to prevent this the lintian check was invented - probably
> to late for your case).
>
>
True, you read my mind :)
>> What should I do in such case? override the warning?
>>
> I'd call this a dangerous way because it will close your eyes in such
> cases in the future. You should decide about your plan how to number
> the real bowtie 2.0.0 release because also
>
> $ dpkg --compare-versions 2.0.0-beta6-1 gt 2.0.0 &&echo $?
> 0
>
> is the case. If you simply override the warning users of 2.0.0-beta6-1
> do not see any upgrade path on their machines before, say 2.0.1~alpha1.
>
I see, thank you for the hint.
> The proper way to deal with such problems is using an epoch:
>
> $ dpkg --compare-versions 2.0.0-beta6-1 gt 1:2.0.0 && echo $?
>
>
this depend on the way upstream will call the non-beta version.
In case of version clash it is fine for me to start use epochs.
But what to do if I want to upload the package ?
Will it be fine to upload it with the warning ?
> There are people who do not like epochs - but this is the clean way.
>
> Kind regards
>
> Andreas.
>
>
Thank you,
Alex
Reply to: