Bug#517973: unfinalized changelog entries imply unparseable debian/changelog files
Sean Whitton <firstname.lastname@example.org> writes:
> On Fri 19 Oct 2018 at 10:12PM -0300, David Bremner wrote:
>> Aside from the terminalogy of "finalization", which seems to be specific
>> to debian-changelog-mode, I'd say that's now a (the?) standard workflow.
> dgit doesn't use it, i.e., it uses unfinalised changelogs.
Interesting. I guess this is one of those generational things.
> dpkg-buildpackage can build packages that have unfinalised changelogs,
> though? I have built unreleased dgit many times.
Ah. I was fooled by the 40+ lines of warnings (really, I just counted),
into thinking the build did not succeed.
Don't those warnings annoy you when building unreleased dgit? Or do you
suppress them somehow?
> The advantage is the fact that you can set the distribution for the
> upload while still keeping it clear that the upload is not yet
> released. The way that debian-changelog-mode does it better reflects
> the idea of signing off on an upload.
> Ideally debian-changelog-mode would support both the dch and the
> traditional workflows, but I appreciate that would be a lot of work.
Yeah, I'd be willing to look at patches, but I doubt I'd find the
motivation myself. For one thing, debian-changelog-mode.el is already
more than 1800 lines long...