On Thu, 2010-09-02 at 07:16 +0200, Christian PERRIER wrote: > Just a note to mention that daily builds are still failing for weird > archive signing key problems.
Something to do with the new key announced in http://lists.debian.org/debian-devel-announce/2010/08/msg00006.html ? > W: GPG error: ftp://kheops unstable Release: The following signatures > couldn't be verified because the public key is not available: NO_PUBKEY > 9AA38DCD55BE302B This looks like the _old_ signing key though so perhaps not. http://people.debian.org/~joeyh/d-i/build-logs.html now shows only amd64 failing so I guess most issues are fixed. The amd64 log is ends with: + gpg --homedir /tmp --no-default-keyring --keyring /usr/share/keyrings/debian-archive-keyring.gpg --list-keys /usr/share/keyrings/debian-archive-keyring.gpg ---------------------------------------------- pub 1024D/F42584E6 2008-04-06 [expires: 2012-05-15] uid Lenny Stable Release Key <debian-rele...@lists.debian.org> pub 4096R/55BE302B 2009-01-27 [expires: 2012-12-31] uid Debian Archive Automatic Signing Key (5.0/lenny) <ftpmas...@debian.org> pub 2048R/6D849617 2009-01-24 [expires: 2013-01-23] uid Debian-Volatile Archive Automatic Signing Key (5.0/lenny) pub 4096R/B98321F9 2010-08-07 [expires: 2017-08-05] uid Squeeze Stable Release Key <debian-rele...@lists.debian.org> + cp /usr/share/keyrings/debian-archive-keyring.gpg /etc/apt/trusted.gpg cp: cannot create regular file `/etc/apt/trusted.gpg': Permission denied I'm not sure overwriting /etc/apt/trusted.gpg is a valid thing for the build to be doing though... Ian. -- Ian Campbell What passes for woman's intuition is often nothing more than man's transparency. -- George Nathan
signature.asc
Description: This is a digitally signed message part
