backport-source fails with a dpkg-genchanges error

[Martin Pitt]

While trying to do the backport request in bug 141300, backport-source died:

lp_archive@drescher:~/backports$ backport-source -b jdong -s feisty -S gutsy -v inotify-tools
09:08:52 DEBUG Acquiring lock
09:08:52 DEBUG Initialising connection.
 * Trying to backport inotify-tools...
  - <inotify-tools_3.11-1ubuntu1.tar.gz: downloading from librarian>
  - <inotify-tools_3.11-1ubuntu1.dsc: downloading from librarian>
I: Extracting inotify-tools_3.11-1ubuntu1.dsc ... done.
I: Building backport of inotify-tools-3.11 as 3.11-1ubuntu1~feisty1 ... E: execution of 'dpkg-genchanges -S -sa -v3.3-1' failed with return code 255.

More -v's don't get more debugging.

[Colin Watson (cjwatson)]

backport-source is one of our local scripts, not part of Soyuz.

In any case, this seems to be fixed now. I think what was happening was that dpkg-genchanges was failing on this changelog entry header:

inotify-tools (3.10-1) unstable; urgency=low

Note that there are two spaces there rather than the usual one. My guess is that this was fixed in dpkg-genchanges by Debian somewhere between edgy and hardy, and we picked it up when drescher was upgraded to hardy recently.

[Colin Watson (cjwatson)]

(Since it isn't clear in the web UI view of this bug, the two spaces were between "inotify-tools" and "(3.10-1)".)