Package: mirrors
Severity: normal

aptitude update gave me these errors on Nov 30/Dec 1:
------------------------
W: GPG error: http://http.us.debian.org testing Release: The following
signatures were invalid: BADSIG F1D53D8C4F368D5D Debian Archive
Automatic Signing Key (2005) <[EMAIL PROTECTED]>
W: GPG error: http://http.us.debian.org unstable Release: The following
signatures were invalid: BADSIG F1D53D8C4F368D5D Debian Archive
Automatic Signing Key (2005) <[EMAIL PROTECTED]>

apt-key  showed
pub   1024D/4F368D5D 2005-01-31 [expires: 2006-01-31]
uid                  Debian Archive Automatic Signing Key (2005)
<[EMAIL PROTECTED]>
--------------------------

  I don't think I've seen the errors since, but apparently one of the
servers behind the url had or has a problem.  I may just not have it
again.  Just today Jacob Elder reported that he had isolated the
problem as being with ftp-chi.osuosl.org.  He did some good sleuthing
to find it out.


Here's the text of our correspondence; I've rearranged it so the
oldest bit is first:
----------------


        >         > Ross Boylan wrote:
        >         > > aptitude update gives the errors
        >         > > W: GPG error: http://http.us.debian.org testing Release:
        >         The following
        >         > > signatures were invalid: BADSIG F1D53D8C4F368D5D Debian
        >         Archive
        >         > > Automatic Signing Key (2005) < [EMAIL PROTECTED]>
        >         > > W: GPG error: http://http.us.debian.org unstable Release:
        >         The following
        >         > > signatures were invalid: BADSIG F1D53D8C4F368D5D Debian
        >         Archive
        >         > > Automatic Signing Key (2005) <[EMAIL PROTECTED] >
        >         > >
        >         > > apt-key still shows
        >         > > pub   1024D/4F368D5D 2005-01-31 [expires: 2006-01-31]
        >         > > uid                  Debian Archive Automatic Signing Key 
        >         (2005)
        >         > > <[EMAIL PROTECTED]>
        >         > >
        >         > > This just started yesterday; perhaps something magic 
        >         happened Dec 1?  It
        >         > > was working before.
        >         > >
        >         > > I'm surprised there don't seem to be any reports of this;
        >         I found some 
        >         > > messages when apt first started using keys, but nothing
        >         recent.
        >         > >
        >         > > I tried apt-key update, but do not have debian-keyring
        >         installed. 
        >         > >
        >         > > Before I start randomly installing things (from untrusted
        >         archives) I
        >         > > thought I'd check what's going on.  Does anybody know?
        >         > >
        >         > > If you could cc this edress I'd appreciate it, as I'm  not
        >         subscribed
        >         > > through it.
------

        >         On Tue, 2006-01-03 at 10:00 -0800, Jake wrote:
        >         > This looks like a problem with one of the mirrors,
        >         ftp-chi.osuosl.org.
        >         > http.us.debian.org is a round-robin DNS entry for 5 hosts in
        >         the US.
        >         > Try specifying one of these other servers until the archive 
        >         admins
        >         > notice this.
        >         >
        >         > deb http://rama.progeny.com/debian/ testing main
        >         > deb http://ike.egr.msu.edu/debian/ testing main
        >         > deb http://debian-mirror.cs.umn.edu/debian/ testing main
        >         > deb http://mirrors1.kernel.org/debian/ testing main
        >         >
        >         >

--------------------------

        > On 1/3/06, Ross Boylan <[EMAIL PROTECTED]> wrote:
        >         Thanks for the tip.  The problem seems to have gone away, but
        >         perhaps I
        >         just haven't hit the unlucky mirror.  Should I file a bug 
        >         somewhere?
        >
        >         Ross
--------------------------------------
On Tue, 2006-01-03 at 15:06 -0500, Jacob Elder wrote:
        > Filling a bug would seem appropriate. I'm a bit rusty but I think 
        > there's a psuedepackage for each mirror...?
        >
--------------------
On 1/3/06, Ross Boylan <[EMAIL PROTECTED]> wrote: 
        How did you know which particular server was the problem?
-------------------------------------------
For mirror in `host http.us.debian.org | cut -f3` ; do host $mirror ; done | 
tee mirrors
for mirror in `grep Name mirrors | cut -f2 -d' '` ; do echo "deb 
http://$mirror/debian testing" >> /etc/apt/sources.list ; done
 
Then I uncommented all but one mirror at a time, and run apt-get update for 
each until I found the one that caused gpgv to choke. Then I ran this command 
to pick the mirror with the best latency. I'm using mirrors1.kernel.org.
 
for mirror in `grep Name mirrors | cut -f2 -d' '` ; do ping -c 1 $mirror ; done

 

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27adnvcd
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to