Create a sysmocom-nitb-rauc-image and create a rauc packagegroup
with the default depdencies and an include file to be used by
other images. This assumes that sysmocom-image.inc has been
included first.
Depending on the upstream version (dora or not) we need to
use either core2 or core2-32. Use a python block expression
to pick this depending on the distro version.
E.g. when using musl and trying to build the smallest possible
rootfs. Existing builds should not start to use these flags as
they would be likely to force a big rebuild.
While copying one build to a new directory we inherit most of
the config but it is better to collect this in a single place
so external contributors build with the same options we use.
With the ro image we have a cheap way to figure out which
files were changed. We can run cmp between the to be backed
up file. This way the stored data will be minimal in the
sense of changed files.
By using initramfs for the rescue we occupy 8mb + ~3mb for the
kernel and can reduce the size of that slot. With glibc it is
difficult to reduce this even further. Let's see if a uclibc
build can help us
In fido the old autoload feature doesn't work anymore and we
need to remove it. Otherwise our sysmobts.service file will
create the /dev/dspl.. /dev/fpgadl... firmware upload files
and we all think that firmware loading is working.
Splitt of the actual rescue root filesystem to
image-rauc-rescue-initramfs and build image-rauc-ubi using
kernel+initramfs (like normal rauc slots).
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
This reboots the system instead of starting a shell on boot problems.
Because the slot will only be marked as sucessfully booted as the last
step in a normal boot, repeated emergency boots will cause a fallback at
the boot chooser level to the other slot.
Testing this is possible by passing 'emergency' via the kernel command
line.
Hopefully, this installs a different /etc/default/udhcpc file on
sysmocom-idu machines. Not sure if adding a machine subdir suffices.
The idea is that the machine-specific subdir symocom-idu should replace
the udhcpc.default file used for the idu packages, only, which has both
resolv.conf mods and default route disabled by default.
The IDU requires that udhcpc does neither touch resolv.conf nor install a
default route. Add a flag to switch off default route installation, the
resolv.conf part is already switch-off-able.
It looks like a classic src != build dir issue of the
utility breaking the build on Yocto-Master. Try to fix
that.
ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/temp/log.do_install.2455)
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/temp/log.do_install.2455
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
| DEBUG: Executing shell function do_install
| install: cannot stat `/home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/git/rtl8168-eeprom': No such file or directory
| WARNING: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/temp/run.do_install.2455:1 exit 1 from
| install -m 0755 /home/builder/jenkins/workspace/Yocto-
From the obn-test config, I wrongly assumed that the inmarsat config should
be static on a vessel. Instead, we need to figure out a way to use dhcp with
linkmon.
The builds of the stable upgrade and the Yocto-Master failed
because of the commit gone missing (no remote is referencing
it). I created a dummy branch to hold this commit.