adding a PPA key in pbuilder fails

Bug #993048 reported by Rolf Leggewie
This bug report is a duplicate of:  Bug #993426: adding a PPA key in pbuilder fails. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnupg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am trying to add the GPG key for one of my PPA to one of my pbuilders. Both the host and the pbuilder chroot are lucid. Here's what I do.

$ sudo pbuilder --login --save-after-login
[...] #pbuilder starts up
 # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 15331454B72FD7EC
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 15331454B72FD7EC
gpg: requesting key B72FD7EC from hkp server keyserver.ubuntu.com
gpgkeys: key 15331454B72FD7EC not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
# gpg import --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg /tmp/gpg.txt
gpg: fatal: can't create directory `/home/rolf/.gnupg': No such file or directory
secmem usage: 0/0 bytes in 0/0 blocks of pool 0/32768
# aptitude search ~i\!~M
i apt - Advanced front-end for dpkg
i aptitude - terminal-based package manager
i build-essential - Informational list of build-essential packages
i debhelper - helper programs for debian/rules
i dpkg-dev - Debian package development tools
i less - pager program similar to more
i libcapi20-3 - ISDN utilities - CAPI support libraries
i libcapi20-dev - ISDN utilities - CAPI development libraries
i nano - small, friendly text editor inspired by Pico
i sudo - Provide limited super user privileges to specific users

The second command was a desperate attempt to install the gpg key directly. The last command shows which packages are explicitly installed. My gut tells me there is a package missing in a normal pbuilder installation for this to work.

JFTR: The key exists of course on the keyserver in question. The apt-key command outside the pbuilder chroot works just fine. Try it!

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

About your first attempt: Please use a key server that holds the key you want to add. keyserver.ubuntu.com appearently does not have it.

About the second attempt: The $HOME variable in your environment is preserved running sudo and the directory appearently does not exist in your pbuilder CHROOT. You either want to read the sudo manual page or the gpg manual page (--homedir /dev/null).

Your gut is wrong. Please read the error messages carefully next time. Closing as invalid.

Changed in gnupg (Ubuntu):
status: New → Invalid
Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

JFTR: If /tmp/gpg.txt contains the key you want to add, why don't you use `apt-key add /tmp/gpg.txt'?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

On 02.05.2012 23:15, Daniel Leidert wrote:
> About your first attempt: Please use a key server that holds the key you want to add.
> keyserver.ubuntu.com appearently does not have it.

how about you properly check next time? Makes you sound less like an unhelpful dork.

> Your gut is wrong. Please read the error messages carefully next time.
> Closing as invalid.

Take some of your own medicine, dude. You ACTUALLY try above command and learn.

Reopening. Please do better next time.

Changed in gnupg (Ubuntu):
status: Invalid → New
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I apologize for the name-calling, but you did do a terrible job here. You suggest to read properly but fail to do so yourself, incorrectly closed it and made yourself look unfavourable ;-)

description: updated
Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

What yout reading the manual pages instead of being insulting? gpg knows a debugging switch to read the keyserver response, which on the webinterface indeed is: no keys found (*I* checked the web-servers response before my answer)?! Closing as invalid. And JFTR: EOD for me "dork" (some better names come to my mind). A member of the release time should better know how to write a bug report and how to treat people.

Changed in gnupg (Ubuntu):
status: New → Invalid
Revision history for this message
Rolf Leggewie (r0lf) wrote :

since you are being learn-resistent, here is the key: http://keyserver.ubuntu.com:11371/pks/lookup?search=0x14C966D8AC5F7A9119DD574315331454B72FD7EC&op=index Do you know how to click on a link?

But I'm afraid you might still not believe me, so here is the output from the command line (outside the chroot)

$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 15331454B72FD7EC
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 15331454B72FD7EC
gpg: requesting key B72FD7EC from hkp server keyserver.ubuntu.com
gpg: key B72FD7EC: "Launchpad PPA for Rolf Leggewie" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

This ticket is now hopeless. Thanks, dude. You should abstain from stuff you don't understand. There is no race to close tickets, there is a race to fix problems. And you (almost) prevented fixing one. Congratulate yourself and ask more questions in the future.

I'll open a new ticket and hope you will be embarassed enough to stay out of it.

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.