On 07/17/2012 04:55 PM, Alex Mestiashvili wrote: > On 07/17/2012 11:56 AM, Charles Plessy wrote: > >> Le Tue, Jul 17, 2012 at 11:31:47AM +0200, Alex Mestiashvili a écrit : >> >> >>> I just imported a new upstream version of bowtie2 and lintian gives me >>> the following warning: >>> >>> bowtie2 source: rc-version-greater-than-expected-version 2.0.0-beta7 > >>> 2.0.0 (consider using 2.0.0~beta7) >>> >>> How should I continue now ? change imported and following beta versions >>> to 2.0.0~betaX or leave it like it is ? >>> There are already bowtie2-2.0.0-beta6 in the distribution and I am >>> afraid that uploading 2.0.0~beta7 will mix up versions order. >>> >>> >> Hi Alex, >> >> given that the changes have stayed in our repositories for less than a day, >> and given >> that our audience is not that broad, I am tempted to suggest to simply reset >> or rebase. >> >> To push with --force, you will need to log in git.debian.org, and temporarly >> disable the denyNonFastforwards configuration option, which is currently set >> to >> 'true'. >> >> Have a nice day, >> >> >> > Hi Charles, > Done. > I hope people who have checked it out already also read debian-med.l.d.o > ... > > Thank you, > Alex > > > > >
And returning back to the problem: as far as I understand changing version from let's say 2.0.0-beta6 to 2.0.0~beta6 makes the version 2.0.0~beta6 lower that the original. for example: $dpkg --compare-versions 2.0.0-beta6-1 gt 2.0.0~beta7-1 && echo $? 0 What can we do with that ? the only solution I see is to keep the old versions format and do not change to "~" as lintian suggests. Best regards, Alex -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
