On Sat, Nov 11, 2017 at 07:07:48PM +0100, Christoph Biedl wrote: > Version number re-usage happens, probably always by accident. In the > past, before the advent of slugs to mark security uploads and the like, > this was more likely to happen, and a long time ago my src:file package > was affected by that as well[1]. Unfortunately, there was such an event > even in 2017, see #876633.
There is another reuse that you haven't considered here: reusing a
version (or even, a lower version) after a package has been removed
from the archive (and here I mean, remove from all of oldoldstable,
oldstable, stable, testing, unstable, experimental releases). At that
point dak doesn't know of it anymore and allows everything.
TTBOMK that happened in the past several times.
Do you want to forbid such "reuse" as well?
> So I'd like to suggest an addition to "3.2. The version of a package",
> for clarification, wording in the simplest form:
>
> | For any package, a version number must never be re-used.
>
> What I'd like to express but I guess is a bit too long:
>
> | Unless bitwise identical, no two files that share the base name and
> | have a version number in it may exist anywhere in the archives, ever.
That's all good and nice, but it requires some techinical block on the
archive software for it not to happen.
> Also I feel a temptation to implement an according check in the
> auto-reject machinery at ftp-master. But that's for another day.
Personally I believe that should come *before* having it in policy.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
