backportpackage no longer honors '--dontsign' option

Bug #1183985 reported by Adam Gandelman on 2013-05-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-dev-tools (Ubuntu)
Undecided
Unassigned

Bug Description

Recently upgrade our Jenkins master to raring and, with that, ubuntu-dev-tools 0.147. Our use of backportpackage stopped working, seems the script no longer honors the --dontsign option:

+ backportpackage --dont-sign -s saucy -d precise -r -w . -S '~havana0' d2to1
backportpackage: Downloading d2to1_0.2.10.orig.tar.gz from archive.ubuntu.com (0.040 MiB)
[==============> ] 24%
[=============================> ] 49%
[============================================> ] 74%
[===========================================================>] 98%
[============================================================] 100%

backportpackage: Downloading d2to1_0.2.10-1ubuntu2.debian.tar.gz from archive.ubuntu.com (0.002 MiB)
[============================================================] 100%

gpgv: Signature made Fri 17 May 2013 09:24:11 AM EDT using DSA key ID FA14013B
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./d2to1_0.2.10-1ubuntu2.dsc
dpkg-source: info: extracting d2to1 in d2to1-precise
dpkg-source: info: unpacking d2to1_0.2.10.orig.tar.gz
dpkg-source: info: unpacking d2to1_0.2.10-1ubuntu2.debian.tar.gz
dch warning: new version (0.2.10-1ubuntu2~ubuntu12.04.1~havana0) is less than
the current version number (0.2.10-1ubuntu2).
 dpkg-buildpackage -rfakeroot -d -us -uc -S -nc -sa
dpkg-buildpackage: source package d2to1
dpkg-buildpackage: source version 0.2.10-1ubuntu2~ubuntu12.04.1~havana0
dpkg-buildpackage: source changed by Openstack Ubuntu Testing Bot <email address hidden>
 dpkg-source --before-build d2to1-precise
dpkg-buildpackage: warning: building a source package without cleaning up as you asked; it might contain undesired files
 dpkg-source -b d2to1-precise
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building d2to1 using existing ./d2to1_0.2.10.orig.tar.gz
dpkg-source: info: building d2to1 in d2to1_0.2.10-1ubuntu2~ubuntu12.04.1~havana0.debian.tar.gz
dpkg-source: info: building d2to1 in d2to1_0.2.10-1ubuntu2~ubuntu12.04.1~havana0.dsc
 dpkg-genchanges -S -sa >../d2to1_0.2.10-1ubuntu2~ubuntu12.04.1~havana0_source.changes
dpkg-genchanges: warning: the current version (0.2.10-1ubuntu2~ubuntu12.04.1~havana0) is earlier than the previous one (0.2.10-1ubuntu2)
dpkg-genchanges: including full source code in upload
 dpkg-source --after-build d2to1-precise
dpkg-buildpackage: full upload (original source is included)
 signfile d2to1_0.2.10-1ubuntu2~ubuntu12.04.1~havana0.dsc Openstack Ubuntu Testing Bot <email address hidden>
gpg: skipped "Openstack Ubuntu Testing Bot <email address hidden>": secret key not available
gpg: /tmp/debsign.m8e3uXOy/d2to1_0.2.10-1ubuntu2~ubuntu12.04.1~havana0.dsc: clearsign failed: secret key not available
debsign: gpg error occurred! Aborting....
backportpackage: Error: debsign returned 2.
Build step 'Execute shell' marked build as failure
Finished: FAILURE

Martin Pitt (pitti) on 2013-05-27
Changed in ubuntu-dev-tools (Ubuntu):
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

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

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

  [ Marc Deslauriers ]
  * mk-sbuild: allow specifying the schroot profile.
  * ubuntutools/config.py: properly handle name being None.

  [ Loïc Minier ]
  * ubuntutools.config: decode developer names with the current locale's
    encoding and add corresponding test; fixes handling of non-ascii names.

  [ Adam Gandelman ]
  * backportpackage: Fix destination for --dont-sign option. (LP: #1183985)

  [ Evan Broder ]
  * Only conclude that we don't need an orig tarball if we're sent to the
    librarian (as opposed to the login page from a private PPA).
    (LP: #1106429)

 -- Benjamin Drung <email address hidden> Tue, 13 Aug 2013 23:12:42 +0200

Changed in ubuntu-dev-tools (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers