Bug#920184: lintian: incorrectly parses an unfinalised changelog entry
On 22-Jan-2019, Chris Lamb wrote:
> Hi Ben,
>
> > ipsum (3.4.5-2) UNRELEASED; urgency=medium
> >
> > * Lorem ipsum dolor sit amet, consectetur adipiscing elit.
> > * Cras in sem consequat, consectetur ligula ac, volutpat nulla.
> >
> > --
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> (NB. this bit is missing; the first time I saw your report I didn't
> see this and almost pinged you back with a "huh?" …!)
Yes, that is what constitutes an unfinalised changelog entry: no
maintainer or date value in the closing line.
I'm not sure what the NB refers to; that part of the changelog entry
is exactly the difference I was pointing out. So we both seem to be
directing each other's attention to the same thing :-)
> Anyway, fixed in Git, pending upload:
Thanks.
> I don't believe Lintian should silence this and defer to whatever
> happens to be reporting this (likely libdpkg-perl) […]
My Perl knowledge is too weak to debug this, so how would I diagnose
where this behaviour in changelog parsing originates?
--
\ “Quidquid latine dictum sit, altum viditur.” (“Whatever is |
`\ said in Latin, sounds profound.”) —anonymous |
_o__) |
Ben Finney <bignose@debian.org>
Reply to: