Hello, since some day I have problems with the trinity repository. It started on June 30th with the following message: W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 96C95152F5CFC95C
After updating the key with sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 96C95152F5CFC95C
Since that I get signature errors:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures were invalid: BADSIG 96C95152F5CFC95C QuickBuild Trinity Desktop Environment W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment
Is there anything I can do to solve this issue?
Thanks in advance.
Stefan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hello, since some day I have problems with the trinity repository. It started on June 30th with the following message: W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 96C95152F5CFC95C
After updating the key with sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 96C95152F5CFC95C
Since that I get signature errors:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures were invalid: BADSIG 96C95152F5CFC95C QuickBuild Trinity Desktop Environment W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment
Is there anything I can do to solve this issue?
Thanks in advance.
Stefan
Hi Stefan,
Which version of TDE do you have installed on your system? Posting the relevant /etc/apt/sources.list lines would help us know very quickly.
Around the time you mention the signing key was changed on the R14 repository, with the 3.5.13.2 repository being changed some weeks later. I have personally verified that the signatures on both the R14 and 3.5.13.2 PPAs are valid, so I'm wondering if you have an old line in sources.list or sources.list.d. somewhere.
Thanks!
Tim
On Thursday, 10. July 2014, Timothy Pearson wrote:
Hello, since some day I have problems with the trinity repository. It started on June 30th with the following message: W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 96C95152F5CFC95C
After updating the key with sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 96C95152F5CFC95C
Since that I get signature errors:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures were invalid: BADSIG 96C95152F5CFC95C QuickBuild Trinity Desktop Environment W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment
Is there anything I can do to solve this issue?
Thanks in advance.
Stefan
Hi Stefan,
Which version of TDE do you have installed on your system? Posting the relevant /etc/apt/sources.list lines would help us know very quickly.
Around the time you mention the signing key was changed on the R14 repository, with the 3.5.13.2 repository being changed some weeks later. I have personally verified that the signatures on both the R14 and 3.5.13.2 PPAs are valid, so I'm wondering if you have an old line in sources.list or sources.list.d. somewhere.
Thanks!
Tim
I am using 13.2: My source-lines are:
##Ubuntu Trinity repositories deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise main
deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise main
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13... precise main
deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13... precise main
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Thursday, 10. July 2014, Timothy Pearson wrote:
Hello, since some day I have problems with the trinity repository. It started on June 30th with the following message: W: A error occurred during the signature verification. The repository
is
not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The
following
signatures couldn't be verified because the public key is not
available:
NO_PUBKEY 96C95152F5CFC95C
After updating the key with sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 96C95152F5CFC95C
Since that I get signature errors:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net precise
Release:
The following signatures were invalid: BADSIG 96C95152F5CFC95C QuickBuild Trinity Desktop Environment W: A error occurred during the signature verification. The repository
is
not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The
following
signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment
Is there anything I can do to solve this issue?
Thanks in advance.
Stefan
Hi Stefan,
Which version of TDE do you have installed on your system? Posting the relevant /etc/apt/sources.list lines would help us know very quickly.
Around the time you mention the signing key was changed on the R14 repository, with the 3.5.13.2 repository being changed some weeks later. I have personally verified that the signatures on both the R14 and 3.5.13.2 PPAs are valid, so I'm wondering if you have an old line in sources.list or sources.list.d. somewhere.
Thanks!
Tim
I am using 13.2: My source-lines are:
##Ubuntu Trinity repositories deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise main
deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise main
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13... precise main
deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13... precise main
Those lines look OK. Can you post both the terminal output and the file downloaded when you run this command: wget http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu/di...
Thanks!
Tim
On Thursday, 10. July 2014, Timothy Pearson wrote:
On Thursday, 10. July 2014, Timothy Pearson wrote:
Hello, since some day I have problems with the trinity repository. It started on June 30th with the following message: W: A error occurred during the signature verification. The repository
is
not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The
following
signatures couldn't be verified because the public key is not
available:
NO_PUBKEY 96C95152F5CFC95C
After updating the key with sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 96C95152F5CFC95C
Since that I get signature errors:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net precise
Release:
The following signatures were invalid: BADSIG 96C95152F5CFC95C QuickBuild Trinity Desktop Environment W: A error occurred during the signature verification. The repository
is
not updated and the previous index files will be used. GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The
following
signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment
Is there anything I can do to solve this issue?
Thanks in advance.
Stefan
Hi Stefan,
Which version of TDE do you have installed on your system? Posting the relevant /etc/apt/sources.list lines would help us know very quickly.
Around the time you mention the signing key was changed on the R14 repository, with the 3.5.13.2 repository being changed some weeks later. I have personally verified that the signatures on both the R14 and 3.5.13.2 PPAs are valid, so I'm wondering if you have an old line in sources.list or sources.list.d. somewhere.
Thanks!
Tim
I am using 13.2: My source-lines are:
##Ubuntu Trinity repositories deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise main
deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise main
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5 .13/ubuntu precise main
deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5 .13/ubuntu precise main
Those lines look OK. Can you post both the terminal output and the file downloaded when you run this command: wget http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu/d ists/precise/Release.gpg
Thanks!
Tim
Maybe it´s also related to my local apt-cacher-ng caching proxy? I will try to use the repositories directly... OK here ist the result: The first apt-get update also shows the BADSIG error W: GPG error: http://ppa.quickbuild.pearsoncomputing.net precise Release: The following signatures were invalid: BADSIG 96C95152F5CFC95C QuickBuild Trinity Desktop Environment
but the second run shows no error, so it looks like an apt-cacher-ng related problem. I will try to remove the old file version out of the cache system.
Thanks for your help.
Stefan
-
Timothy Pearson -
update