Yocto is now using iproute2 4.4 and the tools we packaged into
the main package are now available as extra packages and we can
just drop our extension for master.
libexecdir is now a dedicated directory and empty in our ntpd
build. Avoid QA issue of an empty directory not belonging to
anyone. Clean it if it is empty
Exception: OSError: [Errno 36] File name too long: '/home/oebuilds/jenkins/workspace/Yocto-Master/label/OE/build/tmp/deploy/sources/allarch-poky-linux/Firmware-AbilisFirmware-agereFirmware-amd-ucodeFirmware-atheros_firmwareFirmware-broadcom_bcm43xxFirmware-ca0132Firmware-chelsio_firmwareFirmware-cw1200Firmware-dib0700Firmware-ene_firmwareFirmware-fw_sst_0f28Firmware-go7007Firmware-i2400mFirmware-ibt_firmwareFirmware-it913xFirmware-iwlwifi_firmwareFirmware-IntcSST2Firmware-MarvellFirmware-mwl8335Firmware-myri10ge_firmwareFirmware-OLPCFirmware-phanfwFirmware-qat_dh895xcc_firmwareFirmware-qla2xxxFirmware-r8a779x_usb3Firmware-radeonFirmware-ralink_a_mediatek_company_firmwareFirmware-ralink-firmwareFirmware-rtlwifi_firmwareFirmware-tda7706-firmwareFirmware-ti-connectivityFirmware-ueagle-atm4-firmwareFirmware-via_vt6656Firmware-wl1251Firmware-xc4000Firmware-xc5000Firmware-xc5000cFirmware-sianoFirmware-qualcommAthos_ar3kFirmware-qualcommAthos_ath10k'
Our initramfs images are supposed to be small and don't have a
/etc/opkg folder so attempting to put feed config in there will
fail. Reset the FEED_URIS that come from our local.conf.
When restoring the backup the rootfs is mounted in /rootfs/data
and the symlink to the real file would then not work. Attempt to
change the directory first to get a relative symlink.
Untested change and needed for rauc
The configuration scripts are named for the systemd units for which they
generate configuration files. The generator causes them to run before
those units are started.
* the ntpdate cron job turned into
a shell script which now checks
for running timeserver before
updating the time via ntpdate
* install the cron stanza to the
cron.d directory like serval
other packages does
* comment the entry in the old
crontab file when found
Fixes: SYS#1841
Yocto master has introduced GCC5 and this doesn't like to compile
the older linux kernels yet. This year it is time to move to a newer
LTS kernel and this can be Linux-4.1. Make space for the upgrade
by moving the recipe to a new name.
This change adds an initramfs module to mount the data partition and
restore the backup to the overlay. It is enabled by adding it to the
image-rauc-slot-initramfs recipe.
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
[hfreyther: keep udev out of the dependencies]
The new version searches mounted slots for matching files referenced by
the new manifest. This avoids downloading files we already have on the
system.
Additionally, the new version includes better error handling and more
unit tests.
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
Journald being the typical GNOME application is leaking memory left
and right. Let's backport some of the patches that were done in
later versions.
Fixes: SYS#1843
* use printf instead of echo
* add missing /etc/ for the udhcpc-default file
* add log-entries for all shell actions in the
post image setup
* generate comments in all files which are touched
Related: SYS#1774
We can not have sysmocom-backup-default and sysmocom-backup-data-default
installed at the same time. I don't want to play games with RREPLACE and
RPROVIDES either. So simply use one of the two files. Copy the two more
default values over to the other recipe.
The distro is included after the machine so we can not rely
on the DISTRO_VERSION here. Use the AVAILTUNES and see if the
core2-32 is listed and then pick it.
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.