| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This was changed in f046b4128c9ca3420614887006101fa2b10fc6e7 of
meta-raspberrypi. This also requires
e947e8590f74477505c754d016d99fc71cadf4e1 in meta-updater-raspberrypi.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
Inherit python3native instead of using HOSTTOOLS.
|
| |
| |
| |
| | |
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\ \
| | |
| | | |
nfs-utils: don't add nfs-home-mount.service without sota enabled
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* nfs-home-mount.service is installed by do_install_append_sota, so only when sota is enabled
but it was always added to SYSTEMD_SERVICE_ even when sota wasn't enabled resulting in
do_patch failure:
nfs-utils-2.5.1-r0 do_package: SYSTEMD_SERVICE_nfs-utils value nfs-home-mount.service does not exist
* use sota override everywhere
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|\ \
| |/
|/| |
qemucommand: Restore custom booloader parameter.
|
|/
|
|
|
|
|
| |
The functionality was (presumably unintentionally) removed, but the
option was still present.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
nfs-utils: fix nfs systemd daemons runtime issues
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
nfs-mountd.service and nfs-statd.service rely on /var/lib/nfs to be
present in rootfs, or else they would run into problems for some files
missing in it.
But a ostree/ota rootfs does not have that directory (removed during
do_image), to fix that, we now copy them to /var/local/lib/nfs and
mount it to /var/lib/nfs at runtime, which is done in
nfs-home-mount.service.
nfs-mountd.service and nfs-statd.service need run after
nfs-home-mount.service.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|\ \
| |/
|/| |
aktualizr: Bump to 2020.8 release.
|
|/
|
|
| |
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
ostree-kernel-initramfs: fix devicetree deployment
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Following the changes in ostree's deployment of the kernel, initramfs
and devicetree in /lib/modules/$kver, the deployment method of the
device tree also changed. Instead of picking the first device tree it
finds at a given location, ostree looks at a file named devicetree, next
to kernel and initramfs in /lib/modules/$kver.
This commit modifies ostree-kernel-initramfs to deploy the devicetree
from the sota-defined variable OSTREE_DEVICETREE. It will pick the
first one from the list of device trees that OSTREE_DEVICETREE defines,
and copy it to /lib/modules/$kver. Note that since OSTREE_DEVICETREE
equals to KERNEL_DEVICETREE when it isn't explicitly defined, it could
indeed be a list of device trees.
Signed-off-by: antznin <agodard@witekio.com>
|
|\ \
| |/
|/| |
image_types_ota.bbclass: change IMAGE_BASENAME to PN
|
|/
|
|
|
|
|
|
|
| |
When setting intertask dependencies, we should use PN instead of
IMAGE_BASENAME to refer to a image recipe, since PN is generated from
recipe file name, while IMAGE_BASENAME is a variable that could be
changed, it's not guaranteed to always equal to PN.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|\
| |
| | |
ostree-kernel-initramfs: skip recipe when OSTREE_KERNEL is not defined
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* otherwise it fails with useless error:
ostree-kernel-initramfs/0.0.1-r0/temp/run.do_install.3011' failed with exit code 1:
cp: -r not specified; omitting directory 'tmp-glibc/deploy/images/qemux86/'
WARNING: exit code 1 from a shell command.
because of
cp ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} $kerneldir/vmlinuz
in do_install will try to copy whole ${DEPLOY_DIR_IMAGE}/ when
${OSTREE_KERNEL} is empty
as reported in:
https://github.com/advancedtelematic/meta-updater/pull/740#issuecomment-651952735
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|\
| |
| | |
ostree-kernel-initramfs: deploy dtbs from OSTREE_DEVICETREE
|
|/
|
|
| |
Signed-off-by: antznin <agodard@witekio.com>
|
|\
| |
| | |
ostree-kernel-initramfs: fix parsing for MACHINEs which don't define …
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
INITRAMFS_IMAGE
* when INITRAMFS_IMAGE isn't defined at all, the "d.getVar('INITRAMFS_IMAGE') == ''" part
doesn't do anything useful, because the unexpanded version of this ends in
do_install[depends] variable and breaks parsing:
meta-updater/recipes-sota/ostree-kernel-initramfs/ostree-kernel-initramfs_0.0.1.bb:do_install[depends], dependency ''][d.getVar('INITRAMFS_IMAGE') in 'virtual/kernel:do_deploy ${@['${INITRAMFS_IMAGE}:do_image_complete', ''][d.getVar('INITRAMFS_IMAGE') == '']} virtual/fakeroot-native:do_populate_sysroot' does not contain exactly one ':' character.
Task 'depends' should be specified in the form 'packagename:task'
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|\
| |
| | |
Put aktualizr-info in a separate package and use it in Secondaries.
|
|/
|
|
|
|
|
|
|
| |
We did the work a while ago to make aktualizr-info work for Secondaries,
but until now we weren't putting the tool into the secondary-image we
use for testing. Now it's there. Actually, it's in every image that
inherits from sota.bbclass, which is probably a good thing.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
Introduce ostree kernel initramfs
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We package kernel image, devicetrees, initramfs and install them to
/usr/lib/modules/${KERNEL_VERSION}, which is the preferred location
according to ostree's new implementation, this could simplify the
deployment.
Reference:
https://github.com/ostreedev/ostree/commit/3ab0d5e6644885440bac6abd17b6d2637df5435f
To let initramfs-ostree-image be able to be depended by
ostree-kernel-initramfs, it must inherit nopackages to avoid a annoying
QA warning like the follows:
| WARNING: initramfs-ostree-image-0.0.1-r0 do_package: Manifest ...initramfs-ostree-image.packagedata
| not found in colibri_imx6 armv7ahf-neon-imx armv7at2hf-neon-imx armv7at2hf-neon armv7ahf-neon armv7at2hf-vfp
| armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp allarch
| x86_64_x86_64-nativesdk (variant '')?
Also we need define OSTREE_KERNEL, OSTREE_DEPLOY_DEVICETREE and
OSTREE_DEVICETREE in sota.bbclass so they could be accessed in other
recipes as well as in image recipes.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|\ \
| |/
|/| |
meta: change virtual/network-configuration to network-configuration
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The name 'virtual' is a recipe specific concept but not a package
specific one, it's confusing that a package provides 'virtual/' names.
Let's drop 'virtual/' from network-configuration, to keep consistent
with yocto naming styles.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|\ \
| | |
| | | |
aktualizr: make use of boot-complete.target
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
From the systemd.special(7) man page section boot-complete.target:
This target is intended as generic synchronization point for services
that shall determine or act on whether the boot process completed
successfully.
Let's make use of the target. Since aktualizr by default marks a boot
as successful, we consider aktualizr.service a service which needs to
be executed on successful boot (hence after the boot-complete.target).
This allows to declare a service as crucial by simply ordering it before
the boot-complete.target. The systemd example service
systemd-boot-check-no-failures.service can serve as an example.
This change does not add any service dependency by default as
boot-complete.target by default does not has any extra dependencies.
Note that rebooting in the failure case is not handled by this
mechanism. This can be added by using FailureAction.
Boot assessement infrastructure got introduced with systemd 240. See
also:
https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|\ \ \
| |/ /
|/| | |
Add recipe to build images with binary primaries
|
|/ /
| |
| |
| | |
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
|\ \
| | |
| | | |
image_types_ostree: allow specifying a device tree to deploy
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When setting `OSTREE_DEPLOY_DEVICETREE` to 1, it will by default deploy
all the device tree blobs present in `KERNEL_DEVICETREE`. Adding
`OSTREE_DEVICETREE` would allow specifying a specific device tree blob
(or several dtbs), thus resulting in only the specified ones in the
image. This is particularely useful because ostree selects the first
device tree it finds in /boot, and discards the remaining ones.
Signed-off-by: antznin <agodard@witekio.com>
|
|\ \ \
| |/ /
|/| | |
Bump aktualizr to 2020.7 revision
|
| | |
| | |
| | |
| | | |
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
|/ /
| |
| |
| |
| |
| | |
And garage-sign to 0.7.1-4
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
|\ \
| | |
| | | |
image_types_ostree: allow to add layer specific OSTree commit arguments
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The OSTree commit command allows to add metadata to the commit. This
might be customized in a distro layer for distribution specific needs.
Allow to pass extra arguments using EXTRA_OSTREE_COMMIT variable
(using a variable named similar to EXTRA_OEMAKE used to pass extra make
arguments).
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|\ \ |
|
|/ /
| |
| |
| |
| |
| | |
poky switched to 1.73 which includes this patch
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
|\ \ |
|
|/ /
| |
| |
| | |
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
|\ \
| | |
| | | |
Use checksum as deployment source and refspec in the deployment
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use named reference when deploying the device tree. This makes sure that
this reference will end up in the deployments .origin file, which will
be visible by the user in ostree admin status. This reference will also
be used when running ostree admin upgrade. This is not really required
when using aktualizr, but can be useful during test/debugging when using
pure OSTree updates. Make sure to make ${OSTREE_REPO} accessible via
http and add a remote on the device called ${OSTREE_OSNAME} pointing to
the http exposed archive OSTree. With that ostree admin upgrade should
work.
Note: We could use the name reference in ostree pull-local already, but
this is potentially racy if multiple builds are committing to the same
branch. Use the OSTree commit hash to get the actual commit and recreate
a local reference to this commit. This makes absolutely sure that we use
the same OSTree commit this bitbake execution committed during the
do_image_ostreecommit task.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Relying on a OSTree branch reference has been problematic in the past
and addressed by adding more attributes to it in commit 202a8c70ba8c
("image_types_ostree: Add a unique ref to fix simultaneous bitbaking.").
However, depening on what kind of OpenEmbedded builds are running in
parallel, even more attributes would need to be taken into account.
Instead of relying on a reference, store the exact ostree commit hash
in a manifest file and reuse it in the do_image_ota deploy task. This
guarantees that the correct reference gets picked even when two builds
with the exact same machine/image name run in parallel.
Note: This gets rid of the second branch name again. If the branch name
with image name is preferred, the variable OSTREE_BRANCHNAME can be
used:
OSTREE_BRANCHNAME = "${SOTA_HARDWARE_ID}-${IMAGE_BASENAME}"
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|\ \
| | |
| | | |
initramfs-ostree-image: drop qemuboot from IMAGE_CLASSES
|
| |/
| |
| |
| |
| |
| |
| | |
To avoid generating a qemuboot.conf for qemu machines, it's useless for
a initramfs image.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|\ \
| |/
|/| |
sota_sanity.bbclass: introduce sota_check_boolean_variable
|
|/
|
|
|
|
|
|
|
|
| |
The current sanity check are too strict for some boolean variables,
introduce sota_check_boolean_variable to allow a boolean value to be
set like yes/y/true/t/1 or no/n/false/f/0.
Also change to use oe.types.boolean to check their values.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|\
| |
| | |
OSTree task improvements
|