[sponsor-patch/update-maintainer] Failing when maintainer already is correctly set

[Andrew Starr-Bochicchio]

I can't imagine that this is the first time I've used sponsor-patch where the contributor had already correctly set the maintainer field, so this seems to be a regression somewhere... I'd guess that update-maintainer is exiting with the wrong status.

$ sponsor-patch -vs 1002853
sponsor-patch: I: cd /tmp/sponsor-patch-wf1Bh7
sponsor-patch: I: Selected Ubuntu task: bsdiff (Ubuntu): New
sponsor-patch: I: Downloading bsdiff_4.3-13.dsc...
sponsor-patch: I: Downloading bsdiff_4.3.orig.tar.gz...
sponsor-patch: I: Downloading bsdiff_4.3-13.debian.tar.gz...
sponsor-patch: I: Downloading bsdiff.debdiff.
sponsor-patch: I: Ubuntu package: bsdiff
sponsor-patch: I: The task is a merge request.
sponsor-patch: I: dpkg-source --no-preparation -x /tmp/sponsor-patch-wf1Bh7/bsdiff_4.3-13.dsc
dpkg-source: info: extracting bsdiff in bsdiff-4.3
dpkg-source: info: unpacking bsdiff_4.3.orig.tar.gz
dpkg-source: info: unpacking bsdiff_4.3-13.debian.tar.gz
sponsor-patch: I: cd bsdiff-4.3
sponsor-patch: I: patch --merge --force -p 1 -i /tmp/sponsor-patch-wf1Bh7/bsdiff.debdiff
patching file debian/changelog
patching file debian/control
patching file debian/rules
sponsor-patch: I: update-maintainer
The Maintainer email is set to an ubuntu.com address. Doing nothing.
sponsor-patch: Error: update-maintainer script failed.

$ policy ubuntu-dev-tools
ubuntu-dev-tools:
  Installed: 0.142~daily+bzr1315~precise1
  Candidate: 0.142~daily+bzr1315~precise1
  Version table:
 *** 0.142~daily+bzr1315~precise1 0
        500 http://ppa.launchpad.net/udt-developers/daily/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status
     0.141 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages

[Stefano Rivera (stefanor)]

Fallout from my submittodebian patch (LP: #902233)

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-dev-tools - 0.142

---------------
ubuntu-dev-tools (0.142) unstable; urgency=low

  [ Stefano Rivera ]
  * mk-sbuild: Support kmod, when checking for overlayfs availability.
  * pbuilder-dist: improve bash_completion for *.dsc files. Thanks Maarten
    Bezemer. (Closes: #670924, LP: #770529)
  * check-mir, check-symbols, grep-merges, pbuilder-dist-simple,
    setup-packaging-environment, submittodebian, ubuntu-iso:
    Do enough argument parsing to handle --help (LP: #988009)
  * dgetlp: Require a UTF-8 locale, or it'll crash when displaying errors
    (LP: #979117)
  * pbuilder-dist: Don't try to enable -updates for Debian testing
    (LP: #993006)
  * pbuilder-dist, pull-debian-source, pull-lp-source, requestsync,
    reverse-depends, submittodebian, syncpackage:
    Handle outdated distro-info data. Fall back to sane defaults where
    possible. (Closes: #673957)
  * backportpackage: Avoid uploading orig tarballs if they are already present
    in the destination PPA (LP: #691897)
  * Allow mk-sbuild to be run by root if a configuration file exists
    (LP: #888736)
  * backportpackage: Allow unsigned backports (LP: #992739)
  * update-maintainer: Add a function to restore the original maintainer.
    - Update sponsor-patch to use the new API resulting from this change
      (LP: #1002999)
  * submittodebian: Revert Ubuntu Maintainer mangling, and re-build the source
    package before diffing. (LP: #902233)

  [ Evan Broder ]
  * backportpackage: Add -c, --close flag to include a changelog closer.
  * backportpackage: Switch to ~ubuntu12.04.1-style version numbers
    instead of ~precise1, to make our version numbers more future-proof.
  * backportpackage: Pass -v to debuild with last published version
    number. This matches the way backports have traditionally been
    generated by archive admins.

 -- Stefano Rivera <email address hidden> Mon, 28 May 2012 23:35:52 +0100