Hello
I successfully run: (as indicated in the web site)
sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys F5CFC95C
And installed trinity, but after a while when running
sudo apt-get update
Again I obtain:
Reading package lists... Done W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4DF9B28CA252A784
Did the key change?
regards
Uwe Brauer
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hello
I successfully run: (as indicated in the web site)
sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys F5CFC95C
And installed trinity, but after a while when running
sudo apt-get update
Again I obtain:
Reading package lists... Done W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4DF9B28CA252A784
Did the key change?
regards
Uwe Brauer
No, they key did not change. Any key changes are broadcasted to all lists including trinity-announce.
The error message you posted refers to ppa.launchpad.net; TDE is hosted on ppa.quickbuild.pearsoncomputing.net. Did you add a Launchpad PPA recently without adding its signing key?
Tim
No, they key did not change. Any key changes are broadcasted to all lists including trinity-announce.
The error message you posted refers to ppa.launchpad.net; TDE is hosted on
oops
ppa.quickbuild.pearsoncomputing.net. Did you add a Launchpad PPA recently without adding its signing key?
Right I did so and because I could not receive the key I deleted the relevant ppa and run apt-get update again, but somehow the ppa remains in the cache...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
No, they key did not change. Any key changes are broadcasted to all
lists
including trinity-announce.
The error message you posted refers to ppa.launchpad.net; TDE is
hosted on oops
ppa.quickbuild.pearsoncomputing.net. Did you add a Launchpad PPA
recently
without adding its signing key?
Right I did so and because I could not receive the key I deleted the relevant ppa and run apt-get update again, but somehow the ppa remains in the cache...
Look in /etc/apt/sources.list.d/ as the faulty PPA may have added additional source lines there.
Tim
-
Timothy Pearson -
Uwe Brauer