Re: Daily builds still failing
On Thu, 2010-09-02 at 08:07 +0100, Ian Campbell wrote:
> 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:
> [...]
> I'm not sure overwriting /etc/apt/trusted.gpg is a valid thing for the
> build to be doing though...
Is it possible that the amd64 build machine has some local change?
Looks at the log, everything up to:
+ apt-ftparchive packages localudebs
+ cat localudebs/Packages
+ gzip
+ [ -s localudebs/Packages ]
+ pwd
+ pwd
+ pwd
+ pwd
+ dpkg-architecture -qDEB_HOST_ARCH
+ APT_GET=apt-get --assume-yes -o Dir::Etc::sourcelist=/di/installer/build/sources.list.udeb[...]
looks like a completely regular invocation
of ./installer/build/util/get-packages however the actual script next
has:
# Prepare APTDIR
mkdir -p $APTDIR/state/lists/partial
mkdir -p $APTDIR/state/mirrors/partial
mkdir -p $APTDIR/cache/archives/partial
echo -n > $APTDIR/state/status
if [ "$TYPE" = "deb" ]; then
APT_GET="$APT_GET -o Dir::State::Status=`pwd`/$APTDIR/state/status"
while the log continues with:
+ echo /usr/share/keyrings/debian-archive-keyring.gpg
/usr/share/keyrings/debian-archive-keyring.gpg
+ 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-release@lists.debian.org>
pub 4096R/55BE302B 2009-01-27 [expires: 2012-12-31]
uid Debian Archive Automatic Signing Key (5.0/lenny) <ftpmaster@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-release@lists.debian.org>
+ cp /usr/share/keyrings/debian-archive-keyring.gpg /etc/apt/trusted.gpg
I can't see any historical version of util/get-packages in SVN which has
the echo+gpg+cp commands at this point. So it looks like some local
build admin debug or something. Looking back over the historical amd64
logs it seems the build was previously failing with other gpg errors --
someone was probably trying to workaround/diagnose those?
Ian.
--
Ian Campbell
Current Noise: Queens Of The Stone Age - Give The Mule What He Wants
Where there's no emotion, there's no motive for violence.
-- Spock, "Dagger of the Mind", stardate 2715.1
Reply to: