Apt-get GPG error: NODATA

[baris.kayadelen]

Hi all,

I am running debian etch on my laptop and yesterday I updated it succesfully but today I have a problem. When I write

Code: Select all

apt-get update

] it gives me that error:

Code: Select all

Get:1 http://ftp.belnet.be etch Release.gpg [189B]
Hit http://ftp.belnet.be etch Release
Hit http://ftp.belnet.be etch/main Packages/DiffIndex
Hit http://ftp.belnet.be etch/main Sources/DiffIndex
Get:2 http://security.debian.org etch/updates Release.gpg
Hit http://security.debian.org etch/updates Release
Err http://security.debian.org etch/updates Release

Get:3 http://security.debian.org etch/updates Release [24.3kB]
Ign http://security.debian.org etch/updates Release
Ign http://security.debian.org etch/updates/main Packages/DiffIndex
Ign http://security.debian.org etch/updates/main Sources/DiffIndex
Hit http://security.debian.org etch/updates/main Packages
Hit http://security.debian.org etch/updates/main Sources
Fetched 24.3kB in 3s (6317B/s)
Reading package lists... Done
W: GPG error: http://security.debian.org etch/updates Release: The following signatures were invalid: NODATA 2
W: You may want to run apt-get update to correct these problems

I have searched all list and found that the errors about NO_PUBKEY how can I solve NODATA 2 problem?

my apt-key list are:

Code: Select all

debian:/# apt-key list
/etc/apt/trusted.gpg
--------------------
pub   1024R/1DB114E0 2004-01-15 [expired: 2005-01-27]
uid                  Debian Archive Automatic Signing Key (2004) <ftpmaster@debian.org>

pub   1024D/4F368D5D 2005-01-31 [expired: 2006-01-31]
uid                  Debian Archive Automatic Signing Key (2005) <ftpmaster@debian.org>

pub   1024D/B5F5BBED 2005-04-24
uid                  Debian AMD64 Archive Key <debian-amd64@lists.debian.org>
sub   2048g/34FC6FE5 2005-04-24

pub   1024D/2D230C5F 2006-01-03 [expires: 2007-02-07]
uid                  Debian Archive Automatic Signing Key (2006) <ftpmaster@debian.org>

[Jeroen]

I think that particular URL is broken at the moment. It's a transitional issue, should get resolved later.