Bug#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Sean Whitton
Hello, On Sat, Nov 11 2017, Mattia Rizzolo wrote: > 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

Bug#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Mattia Rizzolo
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

Bug#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Sean Whitton
Hello Christoph, On Sat, Nov 11 2017, Christoph Biedl wrote: > 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

Bug#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Christoph Biedl
Package: debian-policy Version: 4.1.1.1 Severity: wishlist Hello, this is in the category of "It should be obvious to anybody but I'd prefer things are well-defined in case anybody wishes to start an argument over that". So rather nitpicking. Version number re-usage happens, probably always by a