Ross Boylan wrote: > Starting last night I see > W: GPG error: http://localhost sarge/updates Release: The following > signatures were invalid: BADSIG F1D53D8C4F368D5D Debian Archive Automatic > Signing Key (2005) <[EMAIL PROTECTED]> > > Anyone know what's up? I don't see messages about this latest > occurrence.
The sarge security updates repository has a still valid signature from the 2005 key. A broken cache could certianly cause your problem. -- see shy jo
signature.asc
Description: Digital signature
