Bug#889816: lintian: Complain when epoch has been bumped but upstream version did not go backwards

[Raphael Hertzog <hertzog@debian.org>]

On Fri, 04 May 2018, Chris Lamb wrote:
> Could you provide some concrete "good" and "bad" cases? I'm pretty
> sure I know what you're after here but want to be 100% certain,
> especially if we want this to be an "error". :)

Good (in the context of this lintian tag, though I would have used
1.10~beta1+really1.9.7 in this case):

python-django (1:1.9.7-2) unstable; urgency=medium

  * Re-upload 1.9.7 to unstable with epoch.

 -- Chris Lamb <lamby@debian.org>  Sun, 26 Jun 2016 09:58:19 +0200

python-django (1.10~beta1-1) unstable; urgency=medium

  * New upstream beta release.

 -- Chris Lamb <lamby@debian.org>  Sat, 25 Jun 2016 19:17:49 +0200



Bad:

python-django (2:2.0-1) experimental; urgency=medium

  * New upstream stable release.
    https://docs.djangoproject.com/en/2.0/releases/2.0/

 -- Chris Lamb <lamby@debian.org>  Sat, 02 Dec 2017 18:36:33 +0000

python-django (1:2.0~rc1-1) experimental; urgency=medium

  * New upstream release candidate.
    <https://www.djangoproject.com/weblog/2017/nov/15/django-20-release-candidate-1-released/>
  * Drop trailing whitespace in debian/changelog.

 -- Chris Lamb <lamby@debian.org>  Thu, 16 Nov 2017 09:55:14 +0900


;-)

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/