bzr-buildpackage fails GPG signing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-builddeb (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Something in 14.04 has changed with regards to GPG signing of packages.
I have a package I just tried to build locally that has a changelog timestamp like so:
-- Jeff Lane <email address hidden> Thu, 22 May 2014 12:15:56 -0400
Admittedly, it's been a while since I last tried or needed to build a package locally, but I don't recall ever seeing this issue.
I kept getting errors with GPG signing like this:
Now signing changes and any dsc files...
signfile plainbox-
gpg: skipped "Jeff Lane <email address hidden>": secret key not available
gpg: /tmp/debsign.
debsign: gpg error occurred! Aborting....
debuild: fatal error at line 1283:
running debsign failed
bzr: ERROR: The build failed.
Inside my key, I have several addresses listed and nicknames for each like so:
uid Jeff Lane (Primary Canonical) <email address hidden>
After a bit of digging, it seems that I have to now include the nickname in teh control file to get gpg signing to work.
Like this:
-- Jeff Lane (Primary Canonical) <email address hidden> Thu, 22 May 2014 12:15:56 -0400
This is unacceptable, the nick does NOT need to be preserved in debian/changelog.
This is the first time I've used bzr-buildpackage, I've typically just used debuild with -k to specify a key to use.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: bzr-builddeb 2.8.7ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-26-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 9 17:33:06 2014
InstallationDate: Installed on 2012-03-15 (816 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
PackageArchitec
SourcePackage: bzr-builddeb
UpgradeStatus: Upgraded to trusty on 2014-04-20 (50 days ago)
Changed in bzr-builddeb (Ubuntu): | |
status: | Confirmed → Invalid |
Status changed to 'Confirmed' because the bug affects multiple users.