On Mon, 19 Aug 2019, Chris Lamb wrote: > > latest-debian-changelog-entry-without-new-version > > latest-debian-changelog-entry-reuses-existing-version
> I just checked that they don't have different severities which could > have been a justification for different tags (they don't). Umm… as I always understood it these are completely different: - latest-debian-changelog-entry-reuses-existing-version checks that the version without the epoch is never reused, for the archive and snapshots to be consistent (as the epoch is not used in filenames) - latest-debian-changelog-entry-without-new-version checks that the upload does not have a smaller (or equal) version number to the previous upload except in backports, to ensure that it’ll be newer and nobody forgot a version increment before uploading Just wondering, //mirabilos PS: Personally I’m not negatively affected by removal of the latter, it was always annoying for local backports, but it might have saved someone else from a brown paper bag upload… -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg ********** Mit der tarent Academy bieten wir auch Trainings und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an. Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt. **********