Am Dienstag, den 03.01.2006, 22:04 +0100 schrieb Klaus Becker: > apt-get update ergibt bei mir: > > W: GPG error: http://www.backports.org sarge-backports Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY EA8E8B2116BA136C > W: GPG error: http://ftp.debian-unofficial.org sarge Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY F82E5CC04B2B2B9E > W: GPG error: http://debian.scribus.net stable Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY DA286F326C5F196B > W: GPG error: ftp://ftp.nerim.net sarge Release: The following signatures > couldn't be verified because the public key is not available: NO_PUBKEY > 07DC563D1F41B907 > W: You may want to run apt-get update to correct these problems > > Kann mir jemand das erklären?
Ja. U.a.: - das Archiv dieser Liste - das Debian Securing Manual - immerhin 3 der 4 Seiten - so ziemlich jede aktuelle Debian FAQ http://www.debian.org/doc/manuals/securing-debian-howto/ch7#s-deb-pack-sign (7.4.2) http://debian-unofficial.org/faq.html http://wiki.scribus.net/index.php/Scribus_on_Debian_GNU/Linux http://ftp.nerim.net/debian-marillat/faq.html http://channel.debian.de/faq/ch-dpkgundco.html#s-apt-key Und das selbst herauszufinden, war dir nicht möglich? MfG Daniel
