I ran a manual build and figured out what the current build problem for the ISO is. It is not a full partition as the 'no space' message at the end lead me to believe. To test yourself, you need to log in via ssh as buil...@administrator.skolelinux.no and run this command:
make --debug=b -C $HOME/src/debian-edu/src/build/CD-administrator \ suite=edu-testing-nolocal-netinst build-test The build output now includes this part a screenfull up from the end: Using older EFI command line for xorriso 10202 (Optionally) making the image bootable for i386: Running tools/boot/stretch/boot-i386 1 /skolelinux/administrator/debmirror/builder_temp_dir/edu-testing-nolocal-netinst/stretch/CD1 --2016-09-20 09:06:39-- https://d-i.debian.org/daily-images/i386/daily/cdrom/initrd.gz Resolving d-i.debian.org (d-i.debian.org)... 130.89.148.14, 140.211.15.34, 149.20.20.22, ... Connecting to d-i.debian.org (d-i.debian.org)|130.89.148.14|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2016-09-20 09:06:41 ERROR 404: Not Found. And sure enough, the https://d-i.debian.org/daily-images/i386/daily/cdrom/initrd.gz URL is broken. The equivalent amd64 URL is not, so I guess there is something special about i386 in d-i at the moment. Someone should check with the d-i team. I only had time to look at the Skolelinux build failure today, and hope someone else can take it further. A workaround for our build is to not use the daily d-i images and instead apply this diff to our build rules: Index: CONF-edu-testing-nolocal-netinst.sh =================================================================== --- CONF-edu-testing-nolocal-netinst.sh (revision 87826) +++ CONF-edu-testing-nolocal-netinst.sh (working copy) @@ -70,7 +70,7 @@ # This may be an url, or "default", which will make it use the default url # for the daily d-i builds. If not set, uses the official d-i images from # the Debian mirror. -export DI_WWW_HOME=default +#export DI_WWW_HOME=default # Use old DI_CODENAME since 2013-05-18 while the d-i images for jessie # are missing I suspect we do not want that to track the latest d-i development. I notice Wolfgang reverted this exact change 2016-08-11 with the commit message "Use daily d-i builds to avoid kernel/modules version mismatch", and thus suspect not using the daily d-i images is going to fail during installation. I tested a build with the patch in place, and it gave us a updated ISO. No idea if it work, but I doubt it. :) -- Happy hacking Petter Reinholdtsen