7 Commits

Author	SHA1	Message	Date
Steve Langasek	83d2176957	chroot hooks are special, they don't get the environment because it gets scrubbed by rootcmd; so we have to call dpkg --print-architecture after all	2016-02-06 02:38:21 -08:00
Steve Langasek	7ec8dd87ac	Fix architecture handling in hooks. We know we're always being invoked ... from a launchpad-buildd-like setup, which passes ARCH and SUBARCH in the environment, because auto/config and auto/build both rely on this. So don't scatter dpkg --print-architecture calls throughout, especially when many of these are not cross-build-aware.	2016-02-05 23:39:56 -08:00
Oliver Grawert	ef219ff9ee	configure /etc/fw_env.config for all arm arches on snappy	2015-12-10 15:05:29 +01:00
Michael Vogt	133addd590	live-build/ubuntu-core/hooks/16-ensure-uboot.chroot: we need to go into redundEnv mode to get the 5byte header that uboot uses by default, don't ask why	2015-07-16 15:58:16 +02:00
Michael Vogt	4d2b68630d	its /etc/fw_env.config	2015-07-16 15:22:20 +02:00
Michael Vogt	b3b321ea92	create fw_env.conf on armhf so that fw_{set,print}env works	2015-07-16 12:33:47 +02:00
Michael Vogt	e0b6feda6c	create /boot/uboot on armhf to ensure that its in the system ... tarball and still on the system if ubuntu-core-upgrader performs a "format" (LP: #1447652)	2015-04-28 16:39:53 +02:00