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.
dpkg-parsechangelog
Description: stunt dpkg-parsechangelog
_______________________________________________ devscripts-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel
