On 22-Jan-2019, Ben Finney wrote: > In earlier Lintian versions (e.g. 2.5.94) an unfinalised changelog > entry would be handled correctly: no maintainer and no release timestamp. > > […] > > (Could this be related to the recent Lintian change “[…] now we are > trialling using gbp-dch”?)
If it is ‘gbp-dch’ failing to handle an unfinalised changelog, that should be fixed (similar to bug#843248 for ‘dpkg-parsechangelog’). Feel free to reassign this bug report if it is a dependent library causing this behaviour. I am not sufficiently familiar with how Lintian parses changelogs, but perhaps the patch at <URL:https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843248;filename=0001-dpkg-parsechangelog-Tolerate-once-more-unfinalised-c.patch;msg=5> can be useful also for this bug. -- \ “Working out the social politics of who you can trust and why | `\ is, quite literally, what a very large part of our brain has | _o__) evolved to do.” —Douglas Adams | Ben Finney <[email protected]>
