Nick Posted March 9, 2016 Posted March 9, 2016 I have a really slow internet connection and I'm doing alot of re-building Armbian and target systems etc. I have a copy of apt-cacher running on a local machine, I know how to configure it on target machines but I'm not sure how I would point the Armbian build system at it? At a guess I'm thinking that I probably need to modify debootstrap to create /etc/apt/apt.conf.d/90-apt-proxy.conf but wondered if anyone had any better ideas?
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 debootstrap-ng (EXTENDED_DEBOOTSTRAP=yes) uses apt-cacher-ng (it is installed among other build dependencies).
Nick Posted March 10, 2016 Author Posted March 10, 2016 Thanks Zador I'll look at that tonight, I'm guessing that debootstrap-ng installs a local apt-cacher-ng then? Or does it look for one on the network?
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 prepare_host in general.sh installs apt-cacher-ng along with compilers and other development tools. Right now debootstrap process is configured to use localhost as apt-cacher address, and it cannot be changed (is it needed?).
Nick Posted March 10, 2016 Author Posted March 10, 2016 I'm not sure if it needs to be changed or not for the moment, possibly yes as it would be great if the target boards could talk to the same server. But for the moment I wouldn't worry as I'm just experimenting. I've not used debootstrap-ng before so it will be interesting to play with it. Are you planning on deprecating debootstrap in favour of debootstrap-ng in the future or will you be keeping both around?
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 I'm not sure if it needs to be changed or not for the moment, possibly yes as it would be great if the target boards could talk to the same server. Since it's recommended to run build system in virtual machine, I don't think that setting apt-cacher address on target systems in build process is a good idea. It's easy enough to set this up manually afterwards. Are you planning on deprecating debootstrap in favour of debootstrap-ng in the future or will you be keeping both around? Only thing that prevents switching to ng variant by default is lack of testing and feedback. There may be problems with some boards that have unusual u-boot configuration, or with NAND/USB/SATA install script. Otherwise new process is fast and has some cool features, like FEL boot support and building images with btrfs or f2fs root filesystem.
Nick Posted March 10, 2016 Author Posted March 10, 2016 Since it's recommended to run build system in virtual machine, I don't think that setting apt-cacher address on target systems in build process is a good idea. It's easy enough to set this up manually afterwards. At the moment I have a Netgear NAS drive which is powered up 24/7 it's name is nas-1.local and it is running apt-cacher (could be upgraded to apt-cacher-ng if needed). Ultimately it would be great if both the build system (which I do run in a VM) and the physical boards, OPi, Banana Pi etc. look at nas-1.local for packages. But this is for the future it may be that the physical boards look at the NAS drive and the build system maintains it's own private cache. That wouldn't be the worst situation in the world. Only thing that prevents switching to ng variant by default is lack of testing and feedback. There may be problems with some boards that have unusual u-boot configuration, or with NAND/USB/SATA install script. Otherwise new process is fast and has some cool features, like FEL boot support and building images with btrfs or f2fs root filesystem. Ah you should have said ;-) I have an OPi PC, Banana Pi M1+ and a Banana Pi M2 that I can test on when I get 5 minutes :-)
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 At the moment I have a Netgear NAS drive which is powered up 24/7 it's name is nas-1.local and it is running apt-cacher (could be upgraded to apt-cacher-ng if needed). Ultimately it would be great if both the build system (which I do run in a VM) and the physical boards, OPi, Banana Pi etc. look at nas-1.local for packages. But this is for the future it may be that the physical boards look at the NAS drive and the build system maintains it's own private cache. That wouldn't be the worst situation in the world. Maybe you are interested in running one of your boards with root filesystem on NAS (shared via NFS)? It was added recently (though it needs some manual configuration after building). Also it's easy to override apt-cacher address at build time, but I still think that setting apt-cacher address inside Armbian images should be at least separate, or better to let users do it manually if they want (automating creation of one file is not worth it IMHO).
Nick Posted March 10, 2016 Author Posted March 10, 2016 Maybe you are interested in running one of your boards with root filesystem on NAS (shared via NFS)? It was added recently (though it needs some manual configuration after building). I'm certainly interested in testing that as from what I have read it would speed up my testing hugely and also help with production programming as the board will be able to be booted VIA FEL and write it's own SD card . That said, baby steps, I'll try bootstrap-ng tonight and then I'll probably be back asking for help with FEL boot and NFS ;-) Also it's easy to override apt-cacher address at build time, but I still think that setting apt-cacher address inside Armbian images should be at least separate, or better to let users do it manually if they want (automating creation of one file is not worth it IMHO). The override to force the build to system to use the NAS drive would be great, I can then setup the Armbian image using customize-image as required.
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 The override to force the build to system to use the NAS drive would be great, I can then setup the Armbian image using customize-image as required. Done. New option APT_PROXY_ADDR (should be set to hostname:port or ip:port). May work with apt-cacher, should work with apt-cacher-ng.
Nick Posted March 10, 2016 Author Posted March 10, 2016 Done. New option APT_PROXY_ADDR (should be set to hostname:port or ip:port). May work with apt-cacher, should work with apt-cacher-ng. Thank you very much zador.blood.stained, I'm in the process of trying bootstrap-ng atm (just about to boot it) to I'll test the new proxy address option in a minute or two.
Nick Posted March 10, 2016 Author Posted March 10, 2016 Hi zador.blood.stained, Your new APT_PROXY_ADDR option appears to work well with apt-cache running on my NAS drive. It might be worth mentioning in the documentation that :3142 is needed as well though, as the first time I tried I just provided the URL without the port. Funnily enough it failed haha. Second time around with the addition of the port and it appears to be running as it should.
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 There is no documentation for this option yet but I did mention that port should be specified too Done. New option APT_PROXY_ADDR (should be set to hostname:port or ip:port). May work with apt-cacher, should work with apt-cacher-ng.
Nick Posted March 10, 2016 Author Posted March 10, 2016 (edited) There is no documentation for this option yet but I did mention that port should be specified too So you did haha, I really should start paying more attention Sadly the build failed I: Checking component main on http://nas-1.local:3142/httpredir.debian.org/debian... I: Retrieving acl 2.2.52-2 I: Validating acl 2.2.52-2 I: Retrieving libacl1 2.2.52-2 I: Validating libacl1 2.2.52-2 I: Retrieving adduser 3.113+nmu3 I: Validating adduser 3.113+nmu3 I: Retrieving apt 1.0.9.8.2 I: Validating apt 1.0.9.8.2 I: Retrieving apt-utils 1.0.9.8.2 I: Validating apt-utils 1.0.9.8.2 I: Retrieving libapt-inst1.5 1.0.9.8.2 I: Validating libapt-inst1.5 1.0.9.8.2 I: Retrieving libapt-pkg4.12 1.0.9.8.2 I: Validating libapt-pkg4.12 1.0.9.8.2 I: Retrieving libattr1 1%3a2.4.47-2 I: Validating libattr1 1%3a2.4.47-2 I: Retrieving libaudit-common 1%3a2.4-1 I: Validating libaudit-common 1%3a2.4-1 I: Retrieving libaudit1 1%3a2.4-1+b1 I: Validating libaudit1 1%3a2.4-1+b1 I: Retrieving base-files 8+deb8u3 I: Validating base-files 8+deb8u3 I: Retrieving base-passwd 3.5.37 I: Validating base-passwd 3.5.37 I: Retrieving bash 4.3-11+b1 I: Validating bash 4.3-11+b1 I: Retrieving libdns-export100 1%3a9.9.5.dfsg-9+deb8u4 I: Validating libdns-export100 1%3a9.9.5.dfsg-9+deb8u4 I: Retrieving libirs-export91 1%3a9.9.5.dfsg-9+deb8u4 I: Validating libirs-export91 1%3a9.9.5.dfsg-9+deb8u4 I: Retrieving libisc-export95 1%3a9.9.5.dfsg-9+deb8u4 I: Validating libisc-export95 1%3a9.9.5.dfsg-9+deb8u4 I: Retrieving libisccfg-export90 1%3a9.9.5.dfsg-9+deb8u4 I: Validating libisccfg-export90 1%3a9.9.5.dfsg-9+deb8u4 I: Retrieving libboost-iostreams1.55.0 1.55.0+dfsg-3 I: Validating libboost-iostreams1.55.0 1.55.0+dfsg-3 I: Retrieving bsdmainutils 9.0.6 I: Validating bsdmainutils 9.0.6 I: Retrieving libbz2-1.0 1.0.6-7+b3 I: Validating libbz2-1.0 1.0.6-7+b3 I: Retrieving libdebconfclient0 0.192 I: Validating libdebconfclient0 0.192 I: Retrieving coreutils 8.23-4 I: Validating coreutils 8.23-4 I: Retrieving cpio 2.11+dfsg-4.1 I: Validating cpio 2.11+dfsg-4.1 I: Retrieving cron 3.0pl1-127+deb8u1 I: Validating cron 3.0pl1-127+deb8u1 I: Retrieving libcryptsetup4 2%3a1.6.6-5 I: Validating libcryptsetup4 2%3a1.6.6-5 I: Retrieving dash 0.5.7-4+b1 I: Validating dash 0.5.7-4+b1 I: Retrieving libdb5.3 5.3.28-9 I: Validating libdb5.3 5.3.28-9 I: Retrieving debconf 1.5.56 I: Validating debconf 1.5.56 I: Retrieving debconf-i18n 1.5.56 I: Validating debconf-i18n 1.5.56 I: Retrieving debconf-utils 1.5.56 I: Validating debconf-utils 1.5.56 I: Retrieving debian-archive-keyring 2014.3 I: Validating debian-archive-keyring 2014.3 I: Retrieving debianutils 4.4+b1 I: Validating debianutils 4.4+b1 I: Retrieving diffutils 1%3a3.3-1+b1 I: Validating diffutils 1%3a3.3-1+b1 I: Retrieving dmidecode 2.12-3 I: Validating dmidecode 2.12-3 I: Retrieving dpkg 1.17.26 I: Validating dpkg 1.17.26 I: Retrieving e2fslibs 1.42.12-1.1 I: Validating e2fslibs 1.42.12-1.1 I: Retrieving e2fsprogs 1.42.12-1.1 I: Validating e2fsprogs 1.42.12-1.1 I: Retrieving libcomerr2 1.42.12-1.1 I: Validating libcomerr2 1.42.12-1.1 I: Retrieving libss2 1.42.12-1.1 I: Validating libss2 1.42.12-1.1 I: Retrieving findutils 4.4.2-9+b1 I: Validating findutils 4.4.2-9+b1 I: Retrieving gcc-4.8-base 4.8.4-1 I: Validating gcc-4.8-base 4.8.4-1 I: Retrieving gcc-4.9-base 4.9.2-10 I: Validating gcc-4.9-base 4.9.2-10 I: Retrieving libgcc1 1%3a4.9.2-10 I: Validating libgcc1 1%3a4.9.2-10 I: Retrieving libstdc++6 4.9.2-10 I: Validating libstdc++6 4.9.2-10 I: Retrieving libgdbm3 1.8.3-13.1 I: Validating libgdbm3 1.8.3-13.1 I: Retrieving libc-bin 2.19-18+deb8u2 I: Validating libc-bin 2.19-18+deb8u2 I: Retrieving libc6 2.19-18+deb8u2 I: Validating libc6 2.19-18+deb8u2 I: Retrieving locales 2.19-18+deb8u2 I: Validating locales 2.19-18+deb8u2 I: Retrieving multiarch-support 2.19-18+deb8u2 I: Validating multiarch-support 2.19-18+deb8u2 I: Retrieving libgmp10 2%3a6.0.0+dfsg-6 I: Validating libgmp10 2%3a6.0.0+dfsg-6 I: Retrieving gnupg 1.4.18-7 I: Validating gnupg 1.4.18-7 I: Retrieving gpgv 1.4.18-7 I: Validating gpgv 1.4.18-7 I: Retrieving libgnutls-deb0-28 3.3.8-6+deb8u3 I: Validating libgnutls-deb0-28 3.3.8-6+deb8u3 I: Retrieving libgnutls-openssl27 3.3.8-6+deb8u3 I: Validating libgnutls-openssl27 3.3.8-6+deb8u3 I: Retrieving grep 2.20-4.1 I: Validating grep 2.20-4.1 I: Retrieving groff-base 1.22.2-8 I: Validating groff-base 1.22.2-8 I: Retrieving gzip 1.6-4 I: Validating gzip 1.6-4 I: Retrieving hostname 3.15 I: Validating hostname 3.15 I: Retrieving libicu52 52.1-8+deb8u3 I: Validating libicu52 52.1-8+deb8u3 I: Retrieving ifupdown 0.7.53.1 I: Validating ifupdown 0.7.53.1 I: Retrieving init 1.22 I: Validating init 1.22 I: Retrieving init-system-helpers 1.22 I: Validating init-system-helpers 1.22 I: Retrieving insserv 1.14.0-5 I: Validating insserv 1.14.0-5 I: Retrieving iproute2 3.16.0-2 I: Validating iproute2 3.16.0-2 I: Retrieving iptables 1.4.21-2+b1 I: Validating iptables 1.4.21-2+b1 I: Retrieving libxtables10 1.4.21-2+b1 I: Validating libxtables10 1.4.21-2+b1 I: Retrieving iputils-ping 3%3a20121221-5+b2 I: Validating iputils-ping 3%3a20121221-5+b2 I: Retrieving isc-dhcp-client 4.3.1-6+deb8u2 I: Validating isc-dhcp-client 4.3.1-6+deb8u2 I: Retrieving isc-dhcp-common 4.3.1-6+deb8u2 I: Validating isc-dhcp-common 4.3.1-6+deb8u2 I: Retrieving libjson-c2 0.11-4 I: Validating libjson-c2 0.11-4 I: Retrieving kmod 18-3 I: Validating kmod 18-3 I: Retrieving libkmod2 18-3 I: Validating libkmod2 18-3 I: Retrieving less 458-3 I: Validating less 458-3 I: Retrieving libcap2 1%3a2.24-8 I: Validating libcap2 1%3a2.24-8 I: Retrieving libcap2-bin 1%3a2.24-8 I: Validating libcap2-bin 1%3a2.24-8 I: Retrieving libestr0 0.1.9-1.1 I: Validating libestr0 0.1.9-1.1 I: Retrieving libffi6 3.1-2+b2 I: Validating libffi6 3.1-2+b2 I: Retrieving libgcrypt20 1.6.3-2 I: Validating libgcrypt20 1.6.3-2 I: Retrieving libgpg-error0 1.17-3 I: Validating libgpg-error0 1.17-3 I: Retrieving libidn11 1.29-1+b2 I: Validating libidn11 1.29-1+b2 I: Retrieving liblocale-gettext-perl 1.05-8+b1 I: Validating liblocale-gettext-perl 1.05-8+b1 I: Retrieving liblogging-stdlog0 1.0.4-1 I: Validating liblogging-stdlog0 1.0.4-1 I: Retrieving liblognorm1 1.0.1-3 I: Validating liblognorm1 1.0.1-3 I: Retrieving libmnl0 1.0.3-5 I: Validating libmnl0 1.0.3-5 I: Retrieving libnetfilter-acct1 1.0.2-1.1 I: Validating libnetfilter-acct1 1.0.2-1.1 I: Retrieving libnfnetlink0 1.0.1-3 I: Validating libnfnetlink0 1.0.1-3 I: Retrieving libpipeline1 1.4.0-1 I: Validating libpipeline1 1.4.0-1 I: Retrieving libpsl0 0.5.1-1 I: Validating libpsl0 0.5.1-1 I: Retrieving libselinux1 2.3-2 I: Validating libselinux1 2.3-2 I: Retrieving libsemanage-common 2.3-1 I: Validating libsemanage-common 2.3-1 I: Retrieving libsemanage1 2.3-1+b1 I: Validating libsemanage1 2.3-1+b1 I: Retrieving libsepol1 2.3-2 I: Validating libsepol1 2.3-2 I: Retrieving libsigc++-2.0-0c2a 2.4.0-1 I: Validating libsigc++-2.0-0c2a 2.4.0-1 I: Retrieving libtasn1-6 4.2-3+deb8u1 I: Validating libtasn1-6 4.2-3+deb8u1 I: Retrieving libtext-charwidth-perl 0.04-7+b4 I: Validating libtext-charwidth-perl 0.04-7+b4 I: Retrieving libtext-iconv-perl 1.7-5+b2 I: Validating libtext-iconv-perl 1.7-5+b2 I: Retrieving libtext-wrapi18n-perl 0.06-7 I: Validating libtext-wrapi18n-perl 0.06-7 I: Retrieving libusb-0.1-4 2%3a0.1.12-25 I: Validating libusb-0.1-4 2%3a0.1.12-25 I: Retrieving logrotate 3.8.7-1+b1 I: Validating logrotate 3.8.7-1+b1 I: Retrieving lsb-base 4.1+Debian13+nmu1 I: Validating lsb-base 4.1+Debian13+nmu1 I: Retrieving dmsetup 2%3a1.02.90-2.2 I: Validating dmsetup 2%3a1.02.90-2.2 I: Retrieving libdevmapper1.02.1 2%3a1.02.90-2.2 I: Validating libdevmapper1.02.1 2%3a1.02.90-2.2 I: Retrieving man-db 2.7.0.2-5 I: Validating man-db 2.7.0.2-5 I: Retrieving manpages 3.74-1 I: Validating manpages 3.74-1 I: Retrieving mawk 1.3.3-17 I: Validating mawk 1.3.3-17 I: Retrieving nano 2.2.6-3 I: Validating nano 2.2.6-3 I: Retrieving libncurses5 5.9+20140913-1+b1 I: Validating libncurses5 5.9+20140913-1+b1 I: Retrieving libncursesw5 5.9+20140913-1+b1 I: Validating libncursesw5 5.9+20140913-1+b1 I: Retrieving libtinfo5 5.9+20140913-1+b1 I: Validating libtinfo5 5.9+20140913-1+b1 I: Retrieving ncurses-base 5.9+20140913-1 I: Validating ncurses-base 5.9+20140913-1 I: Retrieving ncurses-bin 5.9+20140913-1+b1 I: Validating ncurses-bin 5.9+20140913-1+b1 I: Retrieving net-tools 1.60-26+b1 I: Validating net-tools 1.60-26+b1 I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb I: Retrieving netbase 5.3 I: Validating netbase 5.3 W: Retrying failed download of http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb W: http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.deb was corrupt W: Couldn't download package netbase (ver 5.3 arch all) I: Retrieving netcat-traditional 1.10-41 I: Validating netcat-traditional 1.10-41 I: Retrieving libhogweed2 2.7.1-5 I: Validating libhogweed2 2.7.1-5 I: Retrieving libnettle4 2.7.1-5 I: Validating libnettle4 2.7.1-5 I: Retrieving libnewt0.52 0.52.17-1+b1 I: Validating libnewt0.52 0.52.17-1+b1 I: Retrieving whiptail 0.52.17-1+b1 I: Validating whiptail 0.52.17-1+b1 I: Retrieving nfacct 1.0.1-1.1 I: Validating nfacct 1.0.1-1.1 I: Retrieving libssl1.0.0 1.0.1k-3+deb8u2 I: Validating libssl1.0.0 1.0.1k-3+deb8u2 I: Retrieving libp11-kit0 0.20.7-1 I: Validating libp11-kit0 0.20.7-1 I: Retrieving libpam-modules 1.1.8-3.1+deb8u1 I: Validating libpam-modules 1.1.8-3.1+deb8u1 I: Retrieving libpam-modules-bin 1.1.8-3.1+deb8u1 I: Validating libpam-modules-bin 1.1.8-3.1+deb8u1 I: Retrieving libpam-runtime 1.1.8-3.1+deb8u1 I: Validating libpam-runtime 1.1.8-3.1+deb8u1 I: Retrieving libpam0g 1.1.8-3.1+deb8u1 I: Validating libpam0g 1.1.8-3.1+deb8u1 I: Retrieving libpcre3 2%3a8.35-3.3+deb8u2 I: Validating libpcre3 2%3a8.35-3.3+deb8u2 I: Retrieving perl-base 5.20.2-3+deb8u3 I: Validating perl-base 5.20.2-3+deb8u3 I: Retrieving libpopt0 1.16-10 I: Validating libpopt0 1.16-10 I: Retrieving libprocps3 2%3a3.3.9-9 I: Validating libprocps3 2%3a3.3.9-9 I: Retrieving procps 2%3a3.3.9-9 I: Validating procps 2%3a3.3.9-9 I: Retrieving libreadline6 6.3-8+b3 I: Validating libreadline6 6.3-8+b3 I: Retrieving readline-common 6.3-8 I: Validating readline-common 6.3-8 I: Retrieving rsyslog 8.4.2-1+deb8u2 I: Validating rsyslog 8.4.2-1+deb8u2 I: Retrieving sed 4.2.2-4+b1 I: Validating sed 4.2.2-4+b1 I: Retrieving sensible-utils 0.0.9 I: Validating sensible-utils 0.0.9 I: Retrieving login 1%3a4.2-3+deb8u1 I: Validating login 1%3a4.2-3+deb8u1 I: Retrieving passwd 1%3a4.2-3+deb8u1 I: Validating passwd 1%3a4.2-3+deb8u1 I: Retrieving libslang2 2.3.0-2 I: Validating libslang2 2.3.0-2 I: Retrieving startpar 0.59-3 I: Validating startpar 0.59-3 I: Retrieving libsystemd0 215-17+deb8u3 I: Validating libsystemd0 215-17+deb8u3 I: Retrieving libudev1 215-17+deb8u3 I: Validating libudev1 215-17+deb8u3 I: Retrieving systemd 215-17+deb8u3 I: Validating systemd 215-17+deb8u3 I: Retrieving systemd-sysv 215-17+deb8u3 I: Validating systemd-sysv 215-17+deb8u3 I: Retrieving udev 215-17+deb8u3 I: Validating udev 215-17+deb8u3 I: Retrieving initscripts 2.88dsf-59 I: Validating initscripts 2.88dsf-59 I: Retrieving sysv-rc 2.88dsf-59 I: Validating sysv-rc 2.88dsf-59 I: Retrieving sysvinit-utils 2.88dsf-59 I: Validating sysvinit-utils 2.88dsf-59 I: Retrieving tar 1.27.1-2+b1 I: Validating tar 1.27.1-2+b1 I: Retrieving tasksel 3.31+deb8u1 I: Validating tasksel 3.31+deb8u1 I: Retrieving tasksel-data 3.31+deb8u1 I: Validating tasksel-data 3.31+deb8u1 I: Retrieving traceroute 1%3a2.0.20-2+b1 I: Validating traceroute 1%3a2.0.20-2+b1 I: Retrieving tzdata 2015g-0+deb8u1 I: Validating tzdata 2015g-0+deb8u1 I: Retrieving libustr-1.0-1 1.0.4-3+b2 I: Validating libustr-1.0-1 1.0.4-3+b2 I: Retrieving bsdutils 1%3a2.25.2-6 I: Validating bsdutils 1%3a2.25.2-6 I: Retrieving libblkid1 2.25.2-6 I: Validating libblkid1 2.25.2-6 I: Retrieving libmount1 2.25.2-6 I: Validating libmount1 2.25.2-6 I: Retrieving libsmartcols1 2.25.2-6 I: Validating libsmartcols1 2.25.2-6 I: Retrieving libuuid1 2.25.2-6 I: Validating libuuid1 2.25.2-6 I: Retrieving mount 2.25.2-6 I: Validating mount 2.25.2-6 I: Retrieving util-linux 2.25.2-6 I: Validating util-linux 2.25.2-6 I: Retrieving vim-common 2%3a7.4.488-7 I: Validating vim-common 2%3a7.4.488-7 I: Retrieving vim-tiny 2%3a7.4.488-7 I: Validating vim-tiny 2%3a7.4.488-7 I: Retrieving wget 1.16-1 I: Validating wget 1.16-1 I: Retrieving liblzma5 5.1.1alpha+20120614-2+b3 I: Validating liblzma5 5.1.1alpha+20120614-2+b3 I: Retrieving zlib1g 1%3a1.2.8.dfsg-2+b1 I: Validating zlib1g 1%3a1.2.8.dfsg-2+b1 E: Couldn't download packages: netbase [ error ] ERROR in function create_rootfs_cache [ debootstrap-ng.sh:164 ] [ error ] Debootstrap base system first stage failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ debootstrap-ng.sh:526 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Possibly my fault? Or maybe because the NAS drive is running apt-cache and not apt-cache-ng? I'll try it again incase it was just a glitch Edited March 12, 2016 by zador.blood.stained Added spoiler
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 Maybe check log of apt-cacher on your NAS to determine why netbase wasn't downloaded? Looks like other packages downloaded without problems.
Nick Posted March 10, 2016 Author Posted March 10, 2016 According to the access log for apt-cache netbase is reported as a hit There is the following in apt-cachers error log: Thu Mar 10 22:44:11 2016|192.168.1.79|--- /usr/sbin/apt-cacher: Usage error Thu Mar 10 22:54:40 2016|info [13443]: Got another status line. Redirected?: HTTP/1.1 200 OK Date: Thu, 10 Mar 2016 22:54:40 GMT Server: Apache Last-Modified: Sat, 23 Jan 2016 13:19:39 GMT ETag: "242fc-52a00301b10c0" Accept-Ranges: bytes Content-Length: 148220 Thu Mar 10 22:54:41 2016|info [13448]: Got another status line. Redirected?: HTTP/1.1 200 OK Date: Thu, 10 Mar 2016 22:54:41 GMT Server: Apache Last-Modified: Sat, 23 Jan 2016 13:31:23 GMT ETag: "945-52a005a1140c0" Accept-Ranges: bytes Content-Length: 2373 However I have no idea what it means or if it is relevant? Edit: I've just tried browsing : http://nas-1.local:3142/httpredir.debian.org/debian/pool/main/n/netbase/netbase_5.3_all.debwith chrome and it happily downloaded the file. The file was also parsed by the package manager so it doesn't appear to be corrupt. Edit 2: I've just upgraded apt-cacher on the NAS to apt-cacher-ng and things are now even worse... [ o.k. ] Using custom apt-cacher-ng address [ nas-1.local:3142 ] [ o.k. ] Installing base system [ Stage 1/2 ] I: Retrieving Release I: Retrieving Release.gpg E: Failed getting release signature file http://nas-1.local:3142/httpredir.debian.org/debian/dists/jessie/Release.gpg [ error ] ERROR in function create_rootfs_cache [ debootstrap-ng.sh:164 ] [ error ] Debootstrap base system first stage failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ debootstrap-ng.sh:526 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Again, I've tried downloading Release.gpg via chrome and all was fine.
zador.blood.stained Posted March 10, 2016 Posted March 10, 2016 FIrst installation log suggests that netbase was downloaded, but didn't pass signature validation. Maybe you were unlucky with mirror selected by httpredir.debian.org, sometimes there are partially broken mirrors. With apt-cacher-ng - maybe it's an old version or something else, try checking it's web ui for error reports or switch back to standard apt-cacher.
Nick Posted March 11, 2016 Author Posted March 11, 2016 I couldn't get apt-cacher-ng to work, however I reinstalled apt-cacher on the NAS drive and deleted all of it's cached *.deb files. This time Armbian downloaded everything and built just fine. Thank you very much for your help and patience. I'll go back to looking at the SD card now. One day I might even get around to testing NFS boot ;-)
Nick Posted March 11, 2016 Author Posted March 11, 2016 Hi zador.blood.stained, Do you have a link to the NFS boot documentation by any chance? I saw the link to the commit logs, but nothing really that pointed me in the write direction. If there is something written down then I'll happily test it tonight.
zador.blood.stained Posted March 12, 2016 Posted March 12, 2016 I'm still testing and fixing small issues here and there, I'll try to write some kind of documentation and post here later.
Recommended Posts