I have for some time had TDE key problems on my husband's desktop. I keep thinking that it must have been solved by now and trying again.
He has Wheezy with TDE 3.5.13.2, just as I have. I have no problems with my own key.
Here is my latest attempt:
root@Nyx:/home/peter# apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.pZxq195osY --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --keyring /etc/apt/trusted.gpg.d//pkg-mozilla-archive-keyring.gpg --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 gpg: requesting key 2B8638D0 from hkp server keyserver.quickbuild.pearsoncomputing.net gpg: key 2B8638D0: "QuickBuild Trinity Desktop Environment" not changed gpg: Total number processed: 1 gpg: unchanged: 1
I copied and pasted the apt-key line from the wiki.
And here is why I think that I have a problem:
root@Nyx:/home/peter# aptitude update > key.txt W: GPG error: http://ppa.quickbuild.pearsoncomputing.net wheezy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 099723A280479E11 root@Nyx:/home/peter#
And key.txt is here: http://paste.ubuntu.com/7068342/
I must solve this. He never banks on line, but even so .....
Any ideas?
Lisi
Dne po 10. března 2014 Lisi Reisz napsal(a):
I have for some time had TDE key problems on my husband's desktop. I keep thinking that it must have been solved by now and trying again.
He has Wheezy with TDE 3.5.13.2, just as I have. I have no problems with my own key.
Here is my latest attempt:
root@Nyx:/home/peter# apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.pZxq195osY --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --keyring /etc/apt/trusted.gpg.d//pkg-mozilla-archive-keyring.gpg --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 gpg: requesting key 2B8638D0 from hkp server keyserver.quickbuild.pearsoncomputing.net gpg: key 2B8638D0: "QuickBuild Trinity Desktop Environment" not changed gpg: Total number processed: 1 gpg: unchanged: 1
I copied and pasted the apt-key line from the wiki.
And here is why I think that I have a problem:
root@Nyx:/home/peter# aptitude update > key.txt W: GPG error: http://ppa.quickbuild.pearsoncomputing.net wheezy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 099723A280479E11 root@Nyx:/home/peter#
And key.txt is here: http://paste.ubuntu.com/7068342/
I must solve this. He never banks on line, but even so .....
Any ideas?
Lisi
apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 80479E11
On Monday 10 March 2014 18:16:00 Slávek Banko wrote:
Dne po 10. března 2014 Lisi Reisz napsal(a):
I have for some time had TDE key problems on my husband's desktop. I keep thinking that it must have been solved by now and trying again.
He has Wheezy with TDE 3.5.13.2, just as I have. I have no problems with my own key.
Here is my latest attempt:
root@Nyx:/home/peter# apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.pZxq195osY --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --keyring /etc/apt/trusted.gpg.d//pkg-mozilla-archive-keyring.gpg --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 gpg: requesting key 2B8638D0 from hkp server keyserver.quickbuild.pearsoncomputing.net gpg: key 2B8638D0: "QuickBuild Trinity Desktop Environment" not changed gpg: Total number processed: 1 gpg: unchanged: 1
I copied and pasted the apt-key line from the wiki.
And here is why I think that I have a problem:
root@Nyx:/home/peter# aptitude update > key.txt W: GPG error: http://ppa.quickbuild.pearsoncomputing.net wheezy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 099723A280479E11 root@Nyx:/home/peter#
And key.txt is here: http://paste.ubuntu.com/7068342/
I must solve this. He never banks on line, but even so .....
Any ideas?
Lisi
apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 80479E11
Thank you, Slávek. I could see that the numbers didn't match, but had no idea what to do about it; i.e. how to sort out the right number from the error message.
Lisi
-
Lisi Reisz -
Slávek Banko