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

SOLVED: Re: apt-get update yields unfamiliar error {Scanned}

jmt wrote:

On Friday 13 October 2006 13:13, Henry Hollenberg wrote:


Hey gang,

I'm not familiar with this error:

andy:/etc/apt# apt-get update
Get: 1 http://ftp.us.debian.org testing Release.gpg [189B]
Hit http://ftp.us.debian.org testing Release
Errhttp://ftp.us.debian.org testing Release

Get: 2 http://ftp.us.debian.org testing Release [74.4kB]
Ign http://ftp.us.debian.org testing Release
Hit http://ftp.us.debian.org testing/main Packages
Hit http://ftp.us.debian.org testing/main Sources
Fetched 74.6kB in 3s (20.6kB/s)
Reading package lists... Done
W: GPG error: http://ftp.us.debian.org testing Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBK                            EY 010908312D230C5F W: You may want to
run apt-get update to correct these problems
andy:/etc/apt# vi sources.list
andy:/etc/apt# apt-get update
Get: 1 http://archive.progeny.com testing Release.gpg [189B]
Get: 2 http://archive.progeny.com testing Release [74.4kB]
Ign http://archive.progeny.com testing Release
Get: 3 http://archive.progeny.com testing/main Packages [4089kB]
Get: 4 http://archive.progeny.com testing/main Sources [1189kB]
Fetched 5353kB in 21s (246kB/s)
Reading package lists... Done
W: GPG error: http://archive.progeny.com testing Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 010908312D230C5F W: You may want to run apt-get update to correct
these problems


Tried two different mirrors.
Any idea what it means?

Thanks hgh.
--
Henry Hollenberg
hgh@rcwm.com






Maybe this is a pointer :

http://www.debian-administration.org/articles/174

hth,
jmt


Used the PUBKEY complained about above like so:

andy:/etc/apt# apt-get update
Get: 1 http://archive.progeny.com testing Release.gpg [189B]
Get: 2 http://archive.progeny.com testing Release [74.4kB]
Ign http://archive.progeny.com testing Release
Get: 3 http://archive.progeny.com testing/main Packages [4100kB]
Get: 4 http://archive.progeny.com testing/main Sources [1193kB]
Fetched 5368kB in 11s (485kB/s)
Reading package lists... Done
W: GPG error: http://archive.progeny.com testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
W: You may want to run apt-get update to correct these problems
andy:/etc/apt# apt-get install gnupg
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  libusb-0.1-4
Suggested packages:
  gnupg-doc xloadimage
The following packages will be upgraded:
  gnupg libusb-0.1-4
2 upgraded, 0 newly installed, 0 to remove and 852 not upgraded.
Need to get 2061kB of archives.
After unpacking 8192B disk space will be freed.
Do you want to continue [Y/n]? y
WARNING: The following packages cannot be authenticated!
  libusb-0.1-4 gnupg
Install these packages without verification [y/N]? y
Get: 1 http://archive.progeny.com testing/main libusb-0.1-4 2:0.1.12-2 [20.1kB]
Get: 2 http://archive.progeny.com testing/main gnupg 1.4.5-1 [2040kB]
Fetched 2061kB in 4s (489kB/s)
(Reading database ... 126854 files and directories currently installed.)
Preparing to replace libusb-0.1-4 2:0.1.11-4 (using .../libusb-0.1-4_2%3a0.1.12-2_amd64.deb) ...
Unpacking replacement libusb-0.1-4 ...
Preparing to replace gnupg 1.4.2.2-1 (using .../gnupg_1.4.5-1_amd64.deb) ...
Unpacking replacement gnupg ...
Setting up libusb-0.1-4 (0.1.12-2) ...
Setting up gnupg (1.4.5-1) ...

Got into chicken or egg thing with gnupg so just installed it without verification, I suppose
like we've been doing for years.

Then tried to get the key that had been complained about above:

andy:/etc/apt# apt-key advanced --keyserver keyring.debian.org --recv 010908312D230C5F
Executing: gpg --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --keyserver keyring.debian.org --recv 010908312D230C5F 
gpg: keyring `/etc/apt/secring.gpg' created
gpg: requesting key 2D230C5F from hkp server keyring.debian.org
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error

FIREWALL!

So added a firewall rule:

iptables        -A FORWARD      -p tcp          -i $PF_IF_INT   -o $PF_IF_EXT           -s $INT_NET     --sport 1024:           -d 0/0          --dport 11371   -j ACCEPT

And tried again and Success!:

andy:/etc/apt# apt-key advanced --keyserver keyring.debian.org --recv 010908312D230C5F
Executing: gpg --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --keyserver keyring.debian.org --recv 010908312D230C5F 
gpg: requesting key 2D230C5F from hkp server keyring.debian.org
gpg: /etc/apt/trustdb.gpg: trustdb created
gpg: key 2D230C5F: public key "Debian Archive Automatic Signing Key (2006) <ftpmaster@debian.org>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1

andy:/etc/apt# apt-get update
Get: 1 http://archive.progeny.com testing Release.gpg [189B]
Hit http://archive.progeny.com testing Release
Hit http://archive.progeny.com testing/main Packages
Hit http://archive.progeny.com testing/main Sources
Fetched 189B in 0s (476B/s)
Reading package lists... Done

Got the release file that time.  Next fired up synaptic to install about
one thousand packages, which I'm doing right now....

hgh.

--
Henry Hollenberg
hgh@rcwm.com

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
Reply to: