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.
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.