Problem reports for version control systems

2021-04-29 Thread Lloyd Parkes
Hi all, The problem reports people have in their emails are completely inadequate for trying to determine what is going wrong for people trying to access the NetBSD source. Since I was the first person to post an inadequate report in this first batch, I'll go first at trying to do better.

daily CVS update output

2021-04-29 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/base/shl.mi P src/distrib/sets/lists/debug/shl.mi P src/doc/3RDPARTY P src/doc/CHANGES P src/external/bsd/elftoolchain/dist/common/Makefile P src/external/bsd/elftoolchain/dist/common/elfdefinitions.h P

Re: -current build.sh install-image failure

2021-04-29 Thread Paul Goyette
On Thu, 29 Apr 2021, Chavdar Ivanov wrote: ... Populating `work.efi' Image `work.efi' complete cat work.mbr.truncated work.efi imgroot.fs work.gpt > work.img /home/sysbuild/amd64/tools/bin/nbgpt work.img biosboot -i 2 -c

Automated report: NetBSD-current/i386 build success

2021-04-29 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2021.04.29.17.26.09 christos src/external/mpl/bind/dist/bin/dig/dighost.c,v 1.11 2021.04.29.17.26.09 christos

-current build.sh install-image failure

2021-04-29 Thread Chavdar Ivanov
Hi, I see some failure reports at the moment; today my build stopped at install-image ( live-image was successful; as iso-image runs after install-image, it didn't take place). The excerpt of the log follows: . Preparing spec files for makefs... rm -f work.spec cat work/etc/mtree/* |

Automated report: NetBSD-current/i386 build failure

2021-04-29 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2021.04.29.16.46.34. An extract from the build.sh output follows: ${MAKEDIRTARGET} .