Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-18 Thread Rodrigo Siqueira
On 03/12, Tobias Frost wrote: > On Sat, Mar 11, 2023 at 06:35:39PM -0700, Rodrigo Siqueira wrote: > > Hi, > > > > While working on a new version of the kworkflow package > > (https://tracker.debian.org/pkg/kworkflow), we noticed that the current > > version is 20191112-1.2, and the latest upstream

Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-12 Thread Gioele Barabucci
On 12/03/23 19:13, Peter Wienemann wrote: On 12.03.23 18:48, IOhannes m zmölnig wrote: Could lintian warn when a date based version is used? Lintian already does this - see [0]. [0] https://salsa.debian.org/lintian/lintian/-/blob/f03fc15a45df4965e374b1e3a40c51cf6fe545ed/tags/n/new-package-us

Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-12 Thread IOhannes m zmölnig
Am 12. März 2023 19:13:46 MEZ schrieb Peter Wienemann : >Dear IOhannes, > >On 12.03.23 18:48, IOhannes m zmölnig wrote: >> Could lintian warn when a date based version is used? > >Lintian already does this - see [0]. Ah. Thx. Praise to the lintian maintainers then, and sorry for not doing all th

Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-12 Thread Peter Wienemann
Dear IOhannes, On 12.03.23 18:48, IOhannes m zmölnig wrote: Could lintian warn when a date based version is used? Lintian already does this - see [0]. Best regards, Peter [0] https://salsa.debian.org/lintian/lintian/-/blob/f03fc15a45df4965e374b1e3a40c51cf6fe545ed/tags/n/new-package-uses-da

Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-12 Thread Alexandre Detiste
Lintian already does some special handling for the initial release (like checking the closure of an ITP bug), this check could happen there. Greets Le dim. 12 mars 2023 à 19:06, IOhannes m zmölnig a écrit : > >In future, please use a lower version number when packaging unreleased > >software. A

Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-12 Thread IOhannes m zmölnig
Am 12. März 2023 15:58:00 MEZ schrieb Simon McVittie : >On Sun, 12 Mar 2023 at 09:15:35 +0100, Tobias Frost wrote: >> >> > Version 20191112-1.2 was created because the upstream had no official >> > release at that time; for this reason, the 20191112-1.2 was created and >> > named based on a date.

Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-12 Thread Simon McVittie
On Sun, 12 Mar 2023 at 09:15:35 +0100, Tobias Frost wrote: > On Sat, Mar 11, 2023 at 06:35:39PM -0700, Rodrigo Siqueira wrote: > > While working on a new version of the kworkflow package > > (https://tracker.debian.org/pkg/kworkflow), we noticed that the current > > version is 20191112-1.2, and the

Re: Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-12 Thread Tobias Frost
On Sat, Mar 11, 2023 at 06:35:39PM -0700, Rodrigo Siqueira wrote: > Hi, > > While working on a new version of the kworkflow package > (https://tracker.debian.org/pkg/kworkflow), we noticed that the current > version is 20191112-1.2, and the latest upstream version is 0.6.2. > Version 20191112-1.2

Adding epoch to kworkflow package to correct a wrong upstream version

2023-03-11 Thread Rodrigo Siqueira
Hi, While working on a new version of the kworkflow package (https://tracker.debian.org/pkg/kworkflow), we noticed that the current version is 20191112-1.2, and the latest upstream version is 0.6.2. Version 20191112-1.2 was created because the upstream had no official release at that time; for thi