Current Issues Affecting Testing

fglrx driver in testing is broken

For more info, see

apt key problems

I believe you can now resolve this for official Debian repositories by simply installing the debian-archive-keyring package.

Here is something that is going on: an apt update now gives: W: GPG error: http://http.us.debian.org testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F

I had a pubkey installed for testing yesterday. Now what? --JoshuaRodman

This email from JoeyHess might be relevant: http://lists.debian.org/debian-user/2006/01/msg00291.html

If you encounter following kind of warning (when running apt-get update) :

W: GPG error: ftp://ftp.belnet.be testing Release: The following signatures couldn't be veri ailable: NO_PUBKEY 010908312D230C5F

Follow the procedure below :

# open console terminal, type su and root password # gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 2D230C5F # gpg --armor --export 2D230C5F | apt-key add - # apt-get update

If you encounter following kind of warning (when running apt-get update) :

W: GPG error: http://secure-testing.debian.net etch/security-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 946AA6E18722E71E W: You may want to run apt-get update to correct these problems

Follow the procedure below :

# Open console terminal, type su and root password # wget http://secure-testing.debian.net/ziyi-2005-7.asc -O - | apt-key add - # apt-get update

If you have other sources in sources.list file, you can get the key for them in a similar manner, just look for the key number in the error message. --?JanJansen

Security

There is security support for lenny, but in general it cannot be expected to be of the same quality as for stable. We will try to find a more exact definition during DebConf 2007. -- ?StefanFritsch

Recently the Testing security team [http://lists.debian.org/debian-devel-announce/2006/05/msg00006.html announced] that the testing archive has been integrated with http://security.debian.org. you should update your SourcesList to include:

Instead of the older urls that included http://security-testing-master.debian.net.

See the [wiki:Security security page] for information about keeping your Debian install secure.