Your message dated Mon, 29 Oct 2007 11:14:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line GPG errors only when using apt-cacher
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: apt-cacher
Version: 1.5.3
Severity: normal
aptitude update (run twice) gives
W: GPG error: http://debian.betterworld.us sarge/updates Release: The following
signatures were invalid: BADSIG 010908312D230C5F Debian Archive Automatic
Signing Key (2006) <[EMAIL PROTECTED]>
This error started early this morning, and continues now. In between,
I switched my sources.list to use the archive directly, and the GPG
error went away. The relevant lines are
deb http://debian.betterworld.us:3142/security.debian.org/ sarge/updates main
contrib non-free
#deb http://security.debian.org/ sarge/updates main contrib non-free
It only affects this one line in sources.list; the others are fine.
I also had these errors on May 9 and 10, for the same archive (sarge/updates).
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages apt-cacher depends on:
ii bzip2 1.0.3-2 high-quality block-sorting file co
ii libwww-perl 5.805-1 WWW client/server library for Perl
ii perl 5.8.8-4 Larry Wall's Practical Extraction
apt-cacher recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
As you say, it is going to be difficult to reproduce the exact
circumstances of this with the mirror going down and the disk filling
up.
Since version 1.5.5, apt-cacher now respects the no-cache pragma, so
calling apt-get with -o Acquire::http::No-Cache=true will force refresh
of a cached file enabling the user to flush a corrupt file on the
server. This would seem to have been helpful in this case.
Feel free to reopen, if the problem recurs.
Mark
--- End Message ---
