Re: watch files and weird version numbers
Wouter Verhelst <email@example.com> wrote:
> On Tue, Apr 05, 2005 at 09:53:43AM +0200, Frank Küster wrote:
>> thanks to the thread about watchfiles for sourceforge projects I now
>> have a "working" watch file for jabref which I intend to package.
>> However, they used version numbers that lacked a dot - 1.55 is meant to
>> be in between 1.5 and 1.6, but now of course it is regarded as newer
>> than current 1.7. Is there any way to teach uscan about this?
> Slap upstream for having broken and confusing version numbers. Dpkg will
> not understand that, either, as will many users who do not bother to
> read the upstream web pages.
I'll do that (they also used 1.7b which means "second release candidate
for 1.7), but I probably won't be able to rewrite history and make 1.55
Inst. f. Biochemie der Univ. Zürich