Control: tags -1 +patch
Here's my proposed wording: .---- §3.2.2. Versions must be unique Because of a quirk of file naming, version numbers that are identical save for epoch cause problems, and thus must not be used. In such case you may bump the Debian revision (it doesn't need to start at 1 or be consecutive) or append a tag. In these three namespaces: source, upstream (.orig), and binary, a combination of package name:version-without-epoch must never be reused once a package has been accepted into the archive, even after a release the package belonged to has been obsoleted. `---- This should address all issues mentioned in this bug, plus a not entirely obvious case of a new source package producing a binary with a name that used to belong to another package. It also forbids the secret tech of uploading 1.2.3.orig.tar.gz then 1.2.3.orig.tar.xz; this is sometimes useful but the confusion is not worth it compared to adding a tag. WRT doing policy first before DAK/etc implementation: a maintainer in #887740 refused to make a version before such a requirement has been agreed upon -- thus, it'd be good to provide guidelines even before they're enforced with code. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄⠀⠀⠀⠀ A master species delegates.
