Re: Adding epoch to kworkflow package to correct a wrong upstream version
Am 12. März 2023 15:58:00 MEZ schrieb Simon McVittie <smcv@debian.org>:
>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.
>
>In future, please use a lower version number when packaging unreleased
>software. A version starting with an 8-digit date is almost guaranteed
>to compare greater than whatever upstream eventually chooses,
Could lintian warn when a date based version is used?
(I haven't checked how many upstreams use date-based versions intentionally and fully aware of the consequences, but I think the problem appears mostly if upstream does not do any formal releases at all, so the package maintainer concocts some arbitrary version number on their own)
mfh.her.fsr
IOhannes
Reply to: