| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
[dunfell] Fix ota-ext4 IMAGE_FSTYPE
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* it doesn't automatically pass "-t ext4", because here we're calling
mke2fs as mkfs.ota-ext4 instead of mkfs.ext4
so the resulting was now ext2 instead of ext4
$ file image-raspberrypi4.rootfs.ota-ext4
image-raspberrypi4.rootfs.ota-ext4: Linux rev 1.0 ext2 filesystem data, UUID=15862fcd-6204-486b-a4c6-fdf7b1710797, volume name "otaroot" (large files)
after this fix:
$ file image-raspberrypi4.rootfs.ota-ext4
image-raspberrypi4.rootfs.ota-ext4: Linux rev 1.0 ext4 filesystem data, UUID=3709e65c-1d2b-4280-85d1-638f5f9c3cc0, volume name "otaroot" (extents) (64bit) (large files) (huge files)
that's why metadata_csum and other features enabled by default
in ext4 were now missing after
https://github.com/advancedtelematic/meta-updater/pull/787
we can drop 64bit feature as well, it's also enabled in default
recipe-sysroot-native/etc/mke2fs.conf
[defaults]
base_features = sparse_super,large_file,filetype,resize_inode,dir_index,ext_attr
default_mntopts = acl,user_xattr
enable_periodic_fsck = 0
blocksize = 4096
inode_size = 256
inode_ratio = 16384
[fs_types]
ext3 = {
features = has_journal
}
ext4 = {
features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
inode_size = 256
}
...
Signed-off-by: Martin Jansa <martin.jansa@lge.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 4d34fa53db086955adf6bc58941ebf98a16778f8.
This issue exists only because mke2fs is creating ext2 by default
instead of ext4 which enables this by default as shown in
recipe-sysroot-native/etc/mke2fs.conf
[defaults]
base_features = sparse_super,large_file,filetype,resize_inode,dir_index,ext_attr
default_mntopts = acl,user_xattr
enable_periodic_fsck = 0
blocksize = 4096
inode_size = 256
inode_ratio = 16384
[fs_types]
ext3 = {
features = has_journal
}
ext4 = {
features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
inode_size = 256
}
...
Signed-off-by: Martin Jansa <martin.jansa@lge.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|\
| |
| |
| |
| | |
advancedtelematic/feat/refactor-ota-ext4-task-dunfell
calculate_size function is redundant
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a following error:
| Saving Environment to EXT4... Unsupported feature metadata_csum found, not writing
when u-boot tries to write env to EXT4 filesystem.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|/
|
|
|
|
|
|
|
|
|
|
| |
We dont have to maintain our own function calculate_size and use
dd/mkfs.ext4 to generate ota-ext4 image, they have been done in OE
by get_rootfs_size/oe_mkext234fs functions, we could just use them.
The major benefit could be we can sync the future fixes/changes in
these functions from OE, also avoid maintaining some duplicated code in
image_types_ota.bbclass.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|\
| |
| |
| |
| | |
advancedtelematic/feat/dunfell-fix-provisioning-test-timeout
test in quemu on CI may need more time to prepare env
|
|/
|
|
| |
Signed-off-by: Anatoliy Odukha <aodukha@gmail.com>
|
|\
| |
| | |
aktualizr: Upgrade dunfell to 2020.10 release
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previous initramfs fit specific workaround was removed as part of commit
6eecf1593d, causing ostree to provide an init argument as part of the
kernel command line arguments when it is not really needed.
Bring back the workaround by simply generating an empty file in case
kernel image type is fit and initramfs is also used by the target.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
|
| |
| |
| |
| | |
Signed-off-by: Dominik Wild <dominik.wild@glutz.com>
|
|/
|
|
| |
Signed-off-by: Anatoliy Odukha <aodukha@gmail.com>
|
|\
| |
| | |
aktualizr: Don't put unused configs in the image.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because every aktualizr package was depending on aktualizr-configs, all
of the default configs were getting installed to /usr/lib/sota, despite
that by default none of them were ever used on the device. That
dependency has been removed.
The provisioning recipes still install the recipes they need to the
default location that aktualizr actually uses (/usr/lib/sota/conf.d). If
you want to use anything else, a specific recipe should be created to do
so.
This change rendered the aktualizr-host-tools package useless, so it has
been removed.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
networkd-dhcp-conf: fix REQUIRED_DISTRO_FEATURES
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* it's REQUIRED_DISTRO_FEATURES not REQUIRED_DISTRO_FEATURES_
* inherit features_check to actually respect REQUIRED_DISTRO_FEATURES
and fix:
ERROR: networkd-dhcp-conf-1.0-r1 do_package_qa: QA Issue: networkd-dhcp-conf: recipe doesn't inherit features_check [unhandled-features-check]
* fix:
commit 4ae9917bf2475c118e8015ec7a2ce10bd01a0124
Author: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
Date: Fri Nov 1 11:44:44 2019 +0100
OTA-3988: Don't build the networkd-dhcp recipe if systemd is not included into the disto feature list
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|\
| |
| | |
Feat/rm upstreamed packages
|
| |
| |
| |
| |
| |
| | |
It appears to be an almost straight copy of this recipe.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| |
| |
| |
| |
| |
| | |
The version in meta-openembedded already supports a native build.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| |
| |
| |
| |
| |
| | |
The version in poky already supports a native build.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|/
|
|
|
|
| |
And it's a newer version at that!
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| |
| |
| | |
liuming50/introduce-OSTREE_MULTI_DEVICETREE_SUPPORT-for-dunfell
sota: introduce OSTREE_MULTI_DEVICETREE_SUPPORT
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ostree supports multiple devicetrees provided that there is no
/lib/modules/$kversion/devicetree installed on rootfs, in which case,
a uboot variable 'fdtdir' would be written to /boot/loader/uEnv.txt
instead of fdt_file.
Introduce OSTREE_MULTI_DEVICETREE_SUPPORT to control that, when it's
set to '0', there is no functional changes with current implementation,
while it's set to '1', then /lib/modules/$kversion/devicetree would not
be installed and the end users need set their own fdtfile/fdt_file in
boot script to locate the devicetree in 'fdtdir'.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|\
| |
| | |
Feat/dunfell/2020.9
|
| |
| |
| |
| | |
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* failing "which repo" causes the run.buildinfo_manifest task to fail
before it even reaches the test for empty repotool variable:
dash -x some-image/1.0-r2/temp/run.buildinfo_manifest.80233
+ export systemd_system_unitdir=/usr/lib/systemd/system
+ export systemd_unitdir=/usr/lib/systemd
+ export systemd_user_unitdir=/usr/lib/systemd/user
+ buildinfo_manifest
+ which repo
+ repotool=
+ bb_sh_exit_handler
+ ret=1
+ [ 1 != 0 ]
+ echo WARNING: exit code 1 from a shell command.
WARNING: exit code 1 from a shell command.
+ exit 1
causing nasty long python exception from do_image task
with this fix, it just shows an warning again:
dash -x some-image/1.0-r2/temp/run.buildinfo_manifest.80233
+ export systemd_user_unitdir=/usr/lib/systemd/user
+ buildinfo_manifest
+ which repo
+ true
+ repotool=
+ [ -n ]
+ bbwarn Android repo tool not found; manifest not copied.
+ [ -p some-image/1.0-r2/temp/fifo.80233 ]
+ echo WARNING: Android repo tool not found; manifest not copied.
WARNING: Android repo tool not found; manifest not copied.
+ ret=0
+ trap 0
+ exit 0
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now we have changed to inherit python3native to provide python3 binary
for repo, then we need explicitly call python3 to execute repo, or else
it will firstly try to locate python which will fail if python is not
in HOSTTOOLS.
This fixes a following warning:
| Android repo tool failed to run; manifest not copied
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
| |
| |
| |
| | |
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|/
|
|
|
|
|
| |
The functionality was (presumably unintentionally) removed, but the
option was still present.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
aktualizr: Bump to latest and install headers in dev package.
|
|/
|
|
| |
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
Cherry pick nfs utils fixes to dunfell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|\
| |
| | |
Remove boost 1.72 bbappend
|
|/
|
|
|
|
| |
poky switched to 1.73 which includes this patch
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
|\
| |
| | |
sota_raspberrypi: Use new variable for bootfiles path.
|
|/
|
|
|
|
|
|
| |
This was changed in a907c3261ef583f898803706cd596d372c6644cb of
meta-raspberrypi. This also requires
0b5292d13692ba074dc85227233e3a819d944204 in meta-updater-raspberrypi.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|\
| |
| | |
Feat/dunfell/2020.8
|
| |
| |
| |
| | |
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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>
|
| |
| |
| |
| | |
Signed-off-by: antznin <agodard@witekio.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|