Hello, Seeking seconds: > §3.2.2 Uniqueness of version numbers > > The part of the version number after the epoch must not be reused for > a version of the package with different contents once the package has > been accepted into the archive, even if the version of the package > previously using that part of the version number is no longer present > in any archive suites. > > Epochs are not included in the names of the files that compose source > packages, or in the filenames of binary packages, so reusing a version > number, even if the epoch differs, results in identically named files > with different contents. This can cause various problems. > > If you find yourself wanting to reuse the part of a version number > after the epoch, you can just bump the Debian revision, which doesn't > need to start at 1 or be consecutive. I dropped the thing about tags as the solution of bumping the Debian revision is simpler so it keeps Policy's suggested solution easier to read. Admittedly doesn't help with native packages but those can just have their patch level bumped. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature