Re: Debian versioning question

2023-11-16 Thread Guillem Jover
Hi! On Sat, 2023-11-11 at 03:28:21 +, Wookey wrote: > On 2023-11-10 23:44 +0100, Preuße, Hilmar wrote: > > On 10.11.2023 03:10, Wookey wrote: > > > I think your options are > > > 1) add an epoch (which exists to deal with this sort of problem) > > > > > Well, would like to avoid it, if possib

Re: Debian versioning question

2023-11-12 Thread Andreas Metzler
On 2023-11-10 "Preuße, Hilmar" wrote: > On 10.11.2023 03:10, Wookey wrote: >> I think your options are >> 1) add an epoch (which exists to deal with this sort of problem) >> > Well, would like to avoid it, if possible. I think it is also not the right solutions, epochs are imho intended to fix o

Re: Debian versioning question

2023-11-10 Thread Wookey
On 2023-11-10 23:44 +0100, Preuße, Hilmar wrote: > On 10.11.2023 03:10, Wookey wrote: > > Hi Wookey, > > > I think your options are > > 1) add an epoch (which exists to deal with this sort of problem) > > > Well, would like to avoid it, if possible. There is no real reason to avoid epochs but t

Re: Debian versioning question

2023-11-10 Thread Preuße , Hilmar
On 10.11.2023 00:37, Mattia Rizzolo wrote: On Thu, Nov 09, 2023 at 11:06:32PM +0100, Hilmar Preuße wrote: Hello Mattia, Can we override that anyhow? Even if it was possible, how would that be of any help? You do realize that versioning order matters for much more than whatever is shown on

Re: Debian versioning question

2023-11-10 Thread Preuße , Hilmar
On 10.11.2023 03:10, Wookey wrote: Hi Wookey, I think your options are 1) add an epoch (which exists to deal with this sort of problem) Well, would like to avoid it, if possible. 2) wait till the next (numerical) release 1.3.9 and upload that. Do releases happen often? This approach on

Re: Debian versioning question

2023-11-09 Thread Wookey
On 2023-11-09 23:06 +0100, Hilmar Preuße wrote: > On 10/13/23 01:32, Mattia Rizzolo wrote: > > On Thu, Oct 12, 2023 at 11:52:30PM +0200, Preuße, Hilmar wrote: > > Hi Mattia, > > > > The upstream minor versions are always determined by letters, so I'm > > > unsure > > > how to make clear that 1.3

Re: Debian versioning question

2023-11-09 Thread Mattia Rizzolo
On Thu, Nov 09, 2023 at 11:06:32PM +0100, Hilmar Preuße wrote: > I just noticed that it is not just a display issue on the web page, but a > real issue: my latest uploaded was rejected telling me: > > Your upload included the source package proftpd-dfsg, version 1.3.8a+dfsg-1, > however testing al

Re: Debian versioning question

2023-11-09 Thread Hilmar Preuße
On 10/13/23 01:32, Mattia Rizzolo wrote: On Thu, Oct 12, 2023 at 11:52:30PM +0200, Preuße, Hilmar wrote: Hi Mattia, The upstream minor versions are always determined by letters, so I'm unsure how to make clear that 1.3.8a+ is later than 1.3.8+. Any hints? This is a real sad interaction betw

Re: Debian versioning question

2023-10-12 Thread Mattia Rizzolo
On Thu, Oct 12, 2023 at 11:52:30PM +0200, Preuße, Hilmar wrote: > The upstream minor versions are always determined by letters, so I'm unsure > how to make clear that 1.3.8a+ is later than 1.3.8+. Any hints? This is a real sad interaction between the letters and the + in this case. Clearly the bes

Debian versioning question

2023-10-12 Thread Preuße , Hilmar
Hello, dumb question. Currently the vcswatch for proftpd-dfsg [1] reports: "OLD: VCS is behind the version in the archive: 1.3.8a+dfsg-1 < 1.3.8+dfsg-8." According to deb-version(7) this is absolutely correct: First the initial part of each string consisting entirely of non-digit character