Bug#787254: dch insists on trailing space in "Changes: "
Ian Jackson
ijackson at chiark.greenend.org.uk
Sat May 30 12:18:53 UTC 2015
Package: devscripts
Version: 2.12.6+deb7u2
Severity: minor
When dch is processing the output of dpkg-parsechangelog, it barfs if
the line introducing the Changes field does not have a trailing space
after the colon.
To reproduce: put the attached script as "dpkg-parsechangelog"
somewhere on your path, and run dch. For example, in a test repo I
have, the invocation
dch -v1.1 --distribution unstable 'Commit a forbidden thing'
produces this message:
dch: fatal error at line 641:
Don't understand dpkg-parsechangelog output: Changes:
But if at line 27 of my script I add a single trailing space, all is
well.
I don't think this bug is of any immediate practical relevance to most
people, and I can easily work around it. But it would probably be
worth fixing in case dpkg-source ever changes the output format.
Thanks,
Ian.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dpkg-parsechangelog
Type: application/octet-stream
Size: 869 bytes
Desc: stunt dpkg-parsechangelog
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20150530/7bac4ad9/attachment.obj>
More information about the devscripts-devel
mailing list