Bug#784397: (no subject)

[Barry Warsaw]

Note that the problem isn't only in debchange.  dpkg-buildpackage also seems
to suffer from unfinalized trailers:

$ bzr bd -S
Building using working tree
Building package in merge mode
Looking for a way to retrieve the upstream tarball
Upstream tarball already exists in build directory, using that
Building the package in /home/barry/projects/debian/pylockfile/build-area/python-lockfile-0.10.2, using debuild -S
parsechangelog/debian: warning:     debian/changelog(l21): badly formatted trailer line
LINE:  --
parsechangelog/debian: warning:     debian/changelog(l23): found start of entry where expected more change data or trailer
LINE: python-lockfile (1:0.10.2-1) experimental; urgency=low
parsechangelog/debian: warning:     debian/changelog(l23): found eof where expected more change data or trailer
 dpkg-buildpackage -rfakeroot -d -us -uc -S
parsechangelog/debian: warning:     debian/changelog(l21): badly formatted trailer line
LINE:  --
parsechangelog/debian: warning:     debian/changelog(l23): found start of entry where expected more change data or trailer
LINE: python-lockfile (1:0.10.2-1) experimental; urgency=low
parsechangelog/debian: warning:     debian/changelog(l23): found eof where expected more change data or trailer
dpkg-buildpackage: error: unable to determine source changed by
dpkg-buildpackage: source package python-lockfile
dpkg-buildpackage: source version 1:0.10.2-2
dpkg-buildpackage: source distribution UNRELEASED
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -d -us -uc -S failed
bzr: ERROR: The build failed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20150511/9029a0c3/attachment.sig>