[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Solved]Re: Problems with apt-get update



Joseph A. Nagy, Jr. wrote:
W: GPG error: http://http.us.debian.org stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B629A24C38C6029A W: GPG error: http://non-us.debian.org stable/non-US Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B629A24C38C6029A W: GPG error: http://non-us.debian.org testing/non-US Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B629A24C38C6029A W: GPG error: http://non-us.debian.org unstable/non-US Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B629A24C38C6029A
W: You may want to run apt-get update to correct these problems

What's going on here? I can't do anything (at least not without commenting out those sources) with apt-get because of this problem.

apt-get install debian-keys -t experimental
gpg --import /usr/share/keyrings/debian-keyring.gpg
apt-get update (after uncomment some sources)

I should note that http://http.us.debian.org stable is still unverifiable via GPG even though I imported 859 keys.

gpg: Total number processed: 850
gpg:           w/o user IDs: 1
gpg:               imported: 849  (RSA: 5)

sorry to the folks I haven't responded to, I got involved with a huge update (159 packages) after switching to a friends sources.list

Yes, I am using packages from experimental (not many, but a few) because testing and stable are too far behind (sorry, GAIM .58 and .64 are really old news) for me (I use Yahoo, MSN, ICQ and AIM, as well as really old packages for other programs).

--
Joseph A. Nagy, Jr.
Student at Motlow State Community College
Political Activist Extrodinaire
The only fallacy is the inaction on our part to stave off the worst of horrors, the stripping of personal freedom.



Reply to: