Your message dated Sat, 30 May 2015 10:47:32 -0400
with message-id <[email protected]>
and subject line Re: Bug#787254: dch insists on trailing space in "Changes: "
has caused the Debian Bug report #787254,
regarding dch insists on trailing space in "Changes: "
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
787254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787254
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.

Attachment: dpkg-parsechangelog
Description: stunt dpkg-parsechangelog


--- End Message ---
--- Begin Message ---
Version: 2.14.4

On Sat, May 30, 2015 at 01:18:53PM +0100, Ian Jackson wrote:
> 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.

We're now using libdpkg-perl to do this parsing instead of performing it
manually, so this is fixed.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]>

Attachment: signature.asc
Description: Digital signature


--- End Message ---
_______________________________________________
devscripts-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel

Reply via email to