Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-02 Thread Alex Muntada
Hi Jonas, > I find it irrelevantĀ¹ to list changes reverted or shadowed later > within same release: Please cleanup auto-generated changelog, > stripping parts not ending in the final package release. At least in this particular case (iterating over URL changes in the deb822 headers) I think this

Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-01 Thread Paul Wise
Control: close -1 On Sun, 2018-07-01 at 10:45 +0100, Chris Lamb wrote: > Tagging as moreinfo for the time being... The discussion has revealed that we do not have consensus on what debian/changelog should look like in general so I close this bug. I don't plan on starting any wider discussion on

Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-01 Thread Jonas Smedegaard
Quoting Florian Schlichting (2018-07-01 17:23:04) > Hi, > > On Sun, Jul 01, 2018 at 11:37:21AM +0200, Mattia Rizzolo wrote: > > On Sun, Jul 01, 2018 at 12:39:47PM +0800, Paul Wise wrote: > > > I recently saw a changelog entry (quoted below) for a Perl team > > > package where several contributors

Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-01 Thread Florian Schlichting
Hi, On Sun, Jul 01, 2018 at 11:37:21AM +0200, Mattia Rizzolo wrote: > On Sun, Jul 01, 2018 at 12:39:47PM +0800, Paul Wise wrote: > > I recently saw a changelog entry (quoted below) for a Perl team package > > where several contributors to that version had their names mentioned > > multiple times w

Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-01 Thread Adam D. Barratt
On Sun, 2018-07-01 at 11:37 +0200, Mattia Rizzolo wrote: > On Sun, Jul 01, 2018 at 12:39:47PM +0800, Paul Wise wrote: > > I recently saw a changelog entry (quoted below) for a Perl team > > package > > where several contributors to that version had their names > > mentioned > > multiple times with

Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-01 Thread Chris Lamb
tags 902797 + moreinfo thanks Hi Mattia & Paul, > I personally agree with you here, but apparently not everybody does. Mm, I can see both sides although agree with you both in that each changelog entry should be a summary of sorts rather than be *internally* chronological, etc. etc. Tagging as

Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-01 Thread Mattia Rizzolo
On Sun, Jul 01, 2018 at 12:39:47PM +0800, Paul Wise wrote: > I recently saw a changelog entry (quoted below) for a Perl team package > where several contributors to that version had their names mentioned > multiple times with one or more changes below each instance of their > name. This made the ch

Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-06-30 Thread Paul Wise
Package: lintian Version: 2.5.91 Severity: wishlist I recently saw a changelog entry (quoted below) for a Perl team package where several contributors to that version had their names mentioned multiple times with one or more changes below each instance of their name. This made the changelog harder