Subject: install/32765: kernel sets are not copied to $RELEASEDIR
To: None <firstname.lastname@example.org, email@example.com,>
From: None <firstname.lastname@example.org>
Date: 02/07/2006 07:15:00
>Synopsis: kernel sets are not copied to $RELEASEDIR
>Arrival-Date: Tue Feb 07 07:15:00 +0000 2006
Quentin Garnier - email@example.com - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.
Irrelevant. It happens on autobuild machines.
Kernels are not copied to $RELEASEDIR/binary/sets, as they should.
Moreover, the Makefile in /etc doesn't register that as an error.
Logs of autobuilds from releng.netbsd.org show the following output:
echo netbsd | GZIP=-9 /home/builds/ab/HEAD/i386/200602010000Z-tools/bin/nbpax -O -zw -M -N /home/builds/ab/HEAD/src/etc -f /home/builds/ab/HEAD/i386/200602010000Z-rlse/i386/binary/sets/kern-GENERIC.tgz
pax: Failed open to write on /home/builds/ab/HEAD/i386/200602010000Z-rlse/i386/binary/sets/kern-GENERIC.tgz (No such file or directory)
for each of the kernels.
Look at autobuild logs and results in ftp.n.o/pub/NetBSD-daily/HEAD.
Not known. I guess that command happens before the $RELEASEDIR
directory structure is properly created, which means a .WAIT is
missing somewhere. Also, a failing pax at that point should be
considered an error.