| 2012-05-02 17:43:52 |
Rolf Leggewie |
description |
I am trying to add the GPG key for my "stable" PPA (https://launchpad.net/~r0lf/+archive/stable/) to one of my pbuilders This works fine outside the chroot but fails inside the pbuilder. 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 feeling tells me there is a package missing in a normal pbuilder installation for gpg to work and make a connection here, but of course, the problem could be elsewhere.
JFTR: The key exists of course on the keyserver in question. The apt-key command outside the pbuilder chroot works just fine. Try it!
Command in question run directly on the host:
$ 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
Link to the key page which of course is available
http://keyserver.ubuntu.com:11371/pks/lookup?search=0x14C966D8AC5F7A9119DD574315331454B72FD7EC&op=index |
I am trying to add the GPG key for my "stable" PPA (https://launchpad.net/~r0lf/+archive/stable/) to one of my pbuilders This works fine outside the chroot but fails inside the pbuilder. 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 feeling tells me there is a package missing in a normal pbuilder installation for gpg to work and make a connection here, but of course, the problem could be elsewhere.
JFTR: The key exists of course on the keyserver in question. The apt-key command outside the pbuilder chroot works just fine. Try it!
Command in question run directly on the host:
$ 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: public key "Launchpad PPA for Rolf Leggewie" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
Link to the key which of course is available
http://keyserver.ubuntu.com:11371/pks/lookup?search=0x14C966D8AC5F7A9119DD574315331454B72FD7EC&op=index |
|
