[backportpackage] fails if no GPG present

Bug #992739 reported by Tessa
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
ubuntu-dev-tools (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

backportpackage seems to assume you always want to gpg sign a package, and fails if gpg info isn't present. For local backporting and automated testing, this is a completely un-necessary dependency.

Now signing changes and any dsc files...
 signfile btrfs-tools_0.19+20120328-1~oneiric1.dsc graeme <graeme@galvatron>
gpg: skipped "graeme <graeme@galvatron>": secret key not available
gpg: /tmp/debsign.58LnPsSl/btrfs-tools_0.19+20120328-1~oneiric1.dsc: clearsign failed: secret key not available
debsign: gpg error occurred! Aborting....
debuild: fatal error at line 1269:
running debsign failed
backportpackage: Error: debuild returned 29.

It would be very good to have a flag to skip GPG signing.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubuntu-dev-tools 0.132ubuntu0.2
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue May 1 10:29:35 2012
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-dev-tools
UpgradeStatus: Upgraded to oneiric on 2011-10-25 (189 days ago)

Revision history for this message
Tessa (unit3) wrote :
Benjamin Drung (bdrung)
summary: - backportpackage fails if no GPG present
+ [backportpackage] fails if no GPG present
Changed in ubuntu-dev-tools (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Oibaf (oibaf) wrote :

I also found no way to specify the key to use: there is no -k option and DEBSIGN_KEYID env variable do nothing.

Benjamin Drung (bdrung)
Changed in ubuntu-dev-tools (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-dev-tools (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Dac Chartrand (conner-bw) wrote :

Sorry, this says "0.142, Fix Released" but 12.04 LTS still lists "ubuntu-dev-tools 0.141"

Where exactly is this fix released? How can I determine this information on my own next time I stare at this screen?

Regards,

Revision history for this message
Richard Hansen (rhansen) wrote :

New versions are always released to the current development version of Ubuntu, which is currently 12.10 Quantal.

You can see the versions available in the different Ubuntu releases by visiting the package's overview page:
    https://launchpad.net/ubuntu/+source/ubuntu-dev-tools

If you would like the new version for 12.04 Precise, you have some options:
  * backport it yourself using backportpackage :)
  * request a backport: https://wiki.ubuntu.com/UbuntuBackports
  * see if the SRU team thinks this is a good candidate for a stable release update: https://wiki.ubuntu.com/StableReleaseUpdates

Revision history for this message
Stefano Rivera (stefanor) wrote :
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Stefano, could you do an SRU for precise?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.