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

Hi, On Tue, 08 May 2018, Mattia Rizzolo wrote: > > > I think this warning was not in place yet when you made that mistake. > > > > This warning was added in 2007 so it's likely I just missed it. > > I doubt you missed it. > latest-debian-changelog-entry-without-new-version is really what it >

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

On Tue, May 08, 2018 at 03:57:23AM +0100, Chris Lamb wrote: > > > "W: latest-debian-changelog-entry-without-new-version" > > > > > > Do you think it's still worth adding (essentially) an "E:" version > > > of this? I would tend to be in favour, given that at least I did not > > > see this

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

Processing commands for cont...@bugs.debian.org: > tags 889816 + pending Bug #889816 [lintian] lintian: Complain when epoch has been bumped but upstream version did not go backwards Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 889816:

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

tags 889816 + pending thanks Hi Raphael, > > "W: latest-debian-changelog-entry-without-new-version" > > > > Do you think it's still worth adding (essentially) an "E:" version > > of this? I would tend to be in favour, given that at least I did not > > see this warning when uploading "that"

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

Hi Chris, On Mon, 07 May 2018, Chris Lamb wrote: > I've just implemented this, but I notice that it overlaps with > > "W: latest-debian-changelog-entry-without-new-version" > > Do you think it's still worth adding (essentially) an "E:" version > of this? I would tend to be in favour, given

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

Hi Raphael Hertzog, I've just implemented this, but I notice that it overlaps with "W: latest-debian-changelog-entry-without-new-version" Do you think it's still worth adding (essentially) an "E:" version of this? I would tend to be in favour, given that at least I did not see this warning

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

Dear Raphael, > 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 Sat, 02 Dec 2017 18:36:33 + > > python-django (1:2.0~rc1-1) experimental;

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

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

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

tags 889816 + moreinfo thanks Hi Raphaël, > lintian: Complain when epoch has been bumped but upstream version did not go > backwards 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

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

Package: lintian Version: 2.5.73 Severity: wishlist When the last changelog entry implements an epoch bump, we want to make sure that the epoch is justified by the fact that the upstream version is lower than the former entry in the changelog. e.g when you switch from E¹:U¹-D¹ to E²:U²-D²