Hi! > 1) several errors of followig form > Release: The following signatures couldn't be verified because the > public key is not available: NO_PUBKEY xxxxxxxxxxxxxxxx > i used suggestions from > http://lists.debian.org/deity/2005/08/msg00178.html > to remedy the problem. what could cause this? apt tries to verify[1] the GnuPG signature of the Release files of each package server it connects to. By default, apt only knows of the Debian Archive Keys, which are used to sign the Release files of ftp.debian.org (and thus its mirrors, too). If you have external servers listed in your sources.list, their Release files will be signed by some other key - which apt doesn't know. > 2) i can see the following > Get:3 http://security.debian.org stable/updates Release.gpg [197B] > Hit http://security.debian.org stable/updates Release > Ign http://security.debian.org stable/updates/main Packages > Hit http://security.debian.org stable/updates/main Packages > i didn't mentioned it previously, so it's possible that the error is > there for quite some time. btw i use amd64/testing so it may be caused > by conflict between testing and stable. Can't help you with that one - if the Packages file is ignored, there's usually something wrong with the Release file (bad signature, wrong distribution etc. - see below). But I may be wrong here... > 3) i use blackdown java. for both of the following lines from my > sources.list > deb ftp://ftp.gwdg.de/pub/languages/java/linux/debian testing non-free > deb ftp://ftp.tux.org/java/debian/ testing non-free > i get > W: Conflicting distribution: ftp://ftp.tux.org testing Release (expected > testing but got sarge) > W: You may want to run apt-get update to correct these problems > or the same from gwdg.de. i checked the ftp and the appropriate > directories seem to be present. what's wrong here? Look at the corresponding release file, and especially at the Codename: tag. ___@___:~>GET ftp://ftp.tux.org/java/debian/dists/testing/Release Origin: Blackdown Java-Linux Label: blackdown Suite: stable Codename: sarge Date: Wed, 15 Jun 2005 18:42:09 +0000 Architectures: i386 amd64 Components: non-free Description: Blackdown deb archive MD5Sum: 2b81e55d497b1cc0c710dbd2f99807fb 5495 non-free/binary-i386/Packages 2f80ef2c266f13b2d4b3590d6a1605ac 1559 non-free/binary-i386/Packages.gz d2fe46c93c1dce52577b28d9d7dc69ea 136 non-free/binary-i386/Release 1f755f021cb7f1947e75a3c4d57c60e9 5289 non-free/binary-amd64/Packages dc300d9c8b4f4835b0922578fff0200a 1516 non-free/binary-amd64/Packages.gz e3bcda971c3cc16ff43d531dce594eec 137 non-free/binary-amd64/Release b03037091d70f782478963b4792eb345 542 non-free/source/Sources.gz 52836d0149f9f0b9d73584c8daea409c 138 non-free/source/Release The Codename tag has to match the "distribution" field you've specified in your sources.list - and as testing != sarge, apt complains. Change your sources.list, and blackdown should work again. Regards, Jan [1]: Since version 0.6.x, that is. After having been around in unstable and experimental for quite a while, apt 0.6 finally entered testing these days. -- Jan C. Nordholz <jckn At gmx net>
Attachment:
signature.asc
Description: Digital signature