> > Per Policy 3.2.2 this is actually RC, and there is no length of time > > after which it's Policy-compliant to reuse package name--version pairs: > > "the version numbers which a binary package must not reuse includes the > > version numbers of any versions of the binary package ever accepted into > > the archive". > > The two ppmd source packages do not have any binary packages in common, > so this paragraph of policy does not apply here.
but other paragraphs do (i think) :) from https://www.debian.org/doc/debian-policy/ch-binary.html#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. This uniqueness requirement applies to the version numbers of source packages and of binary packages, [...] ``` there's no guarantee (althought i find it highly unlikely) that src:ppmd will not reach the same version of the old ppmd that used to be present in the archive a decade ago. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
