Sponsor-patch died horribly in the face of a broken changelog entry:
$ sponsor-patch -s 755954
sponsor-patch: https://launchpad.net/bugs/755954 has 2 Ubuntu tasks:
1) opendrim-lmp-powersupply
2) opendrim-lmp-powersupply (oneiric)
To which Ubuntu tasks do the patch belong? 2
Branched 2 revision(s).
+N debian/patches/
+N debian/patches/01-ftbfs-add-opendrim-lib.patch
+N debian/patches/series
M acinclude.m4
M debian/changelog
All changes applied successfully.
Traceback (most recent call last):
File "/usr/bin/sponsor-patch", line 123, in <module>
main()
File "/usr/bin/sponsor-patch", line 114, in main
options.upload, workdir, options.verbose)
File "/usr/lib/python2.6/dist-packages/ubuntutools/sponsor_patch/sponsor_patch.py", line 313, in sponsor_patch
if update_maintainer("debian", verbose) != 0:
File "/usr/lib/python2.6/dist-packages/ubuntutools/update_maintainer.py", line 124, in update_maintainer
distribution = _get_distribution(changelog_file).split("-")[0]
File "/usr/lib/python2.6/dist-packages/ubuntutools/update_maintainer.py", line 87, in _get_distribution
return changelog.distributions
File "/usr/lib/pymodules/python2.6/debian/changelog.py", line 480, in <lambda>
distributions = property(lambda self: self._blocks[0].distributions,
IndexError: list index out of range
The changelog in question had no spaces before the first bulleted item. Don't know if this is something you want to catch. Using -e worked here, so maybe an error like this should drop the user into a shell to fix the source package?
sponsor-patch shouldn't crash. It should tell the user that the changelog entry is malformed and ask the user to fix it.