[sponsor-patch/update-maintainer] Failing when maintainer already is correctly set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-dev-tools (Ubuntu) |
Fix Released
|
Medium
|
Stefano Rivera |
Bug Description
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-
sponsor-patch: I: Selected Ubuntu task: bsdiff (Ubuntu): New
sponsor-patch: I: Downloading bsdiff_
sponsor-patch: I: Downloading bsdiff_
sponsor-patch: I: Downloading bsdiff_
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-
dpkg-source: info: extracting bsdiff in bsdiff-4.3
dpkg-source: info: unpacking bsdiff_
dpkg-source: info: unpacking bsdiff_
sponsor-patch: I: cd bsdiff-4.3
sponsor-patch: I: patch --merge --force -p 1 -i /tmp/sponsor-
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+
Candidate: 0.142~daily+
Version table:
*** 0.142~daily+
500 http://
100 /var/lib/
0.141 0
500 http://
Fallout from my submittodebian patch (LP: #902233)