[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Henry Bremridge wrote: > Been away for a week and while away turned off my machine. Got back last > night , turned on and ran apt-get update and received the following error > > W: GPG error: http://security.debian.org etch/updates Release: Unknown > error executing gpgv > W: You may want to run apt-get update to correct these problems This can be for several reasons - it may simply be bad timing. You may have inadvertently requested a file whilst the archive itself is being updated. The message doesn't say there was a missing key or any other (more common) error, it could simply be a bad packet. Running three Debian machines on different architectures, I've noticed that different architectures get updated at different times and this can lead to differences in which packages get held back, but this only holds those packages back by a day. > > Needless to say rerunning apt-get update did nothing. Please clarify: Did nothing? Do you mean there was no output (i.e. it succeeded) or that the output was unchanged? > Packages were > downloaded and apt-get upgrade worked (with the exception of gnucash-docs > that was held back. No idea why, have not looked yet) Your cache does need another update. gnucash-docs is waiting for the latest gnucash update that fixes a bug in the packaging. The change went into unstable last week, it'll be in testing (etch) soon. For information on things like this, check the information page for the package involved: http://packages.qa.debian.org/g/gnucash.html You'll see that Testing Status is : Too young, only 9 of 10 days old. The version in unstable will therefore be checked to see if it is a valid candidate tomorrow and could migrate to testing the day after. However, the testing status also shows that there may be a delay before this particular package reaches testing. In contrast: http://packages.qa.debian.org/g/gnucash-docs.html [2006-06-20] gnucash-docs 1.9.0-1 MIGRATED to testing (Britney) > On google the common reason mentioned for this error is wrong gpg keys but > > - apt-key list showed that I have the current key -------------------- pub 1024R/1DB114E0 2004-01-15 [expired: 2005-01-27] uid Debian Archive Automatic Signing Key (2004) <ftpmaster@xxxxxxxxxx> pub 1024D/4F368D5D 2005-01-31 [expired: 2006-01-31] uid Debian Archive Automatic Signing Key (2005) <ftpmaster@xxxxxxxxxx> pub 1024D/B5F5BBED 2005-04-24 uid Debian AMD64 Archive Key <debian-amd64@xxxxxxxxxxxxxxxx> sub 2048g/34FC6FE5 2005-04-24 pub 1024D/2D230C5F 2006-01-03 [expires: 2007-02-07] uid Debian Archive Automatic Signing Key (2006) <ftpmaster@xxxxxxxxxx> OK, you won't need the AMD64 one unless you're also on amd_64. > - apt-key update did nothing > > Any suggestions gratefully received I wouldn't worry about it unless it is still happening in a day or so. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: OpenPGP digital signature
-- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html