summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* use garage-sign 0.7.3-8-g29f5922. This garage-sign version support command ↵feat/use-cli-0-7-3-8Anatoliy Odukha2021-09-101-3/+3
| | | | target get-unsigned
* Merge pull request #807 from shr-project/jansa/dunfell-fixes-from-masterPatti Vacek2021-04-064-8/+7
|\ | | | | Backport few fixes from master branch
| * big-update: add LIC_FILES_CHKSUMMartin Jansa2021-04-061-0/+1
| | | | | | | | | | | | | | * fixes: ERROR: big-update-2.0-r0 do_populate_lic: QA Issue: big-update: Recipe file fetches files and does not have license file information (LIC_FILES_CHKSUM) [license-checksum] Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
| * big-update: respect libdir variableMartin Jansa2021-04-061-3/+3
| | | | | | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
| * big-update: use python3Martin Jansa2021-04-061-1/+1
| | | | | | | | | | | | | | * the recipe was changed to inherit python3native, but the do_install still calls python(2) not python3 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
| * fit-conf, ostree-initrd, slcand-start: use COMMON_LICENSE_DIR instead of ↵Martin Jansa2021-04-063-5/+3
|/ | | | | | | | | | | | | COREBASE in LIC_FILES_CHKSUM * fixes slcand-start which fails since LICENSE file was changed in 2019 with: https://git.openembedded.org/openembedded-core/commit/LICENSE?id=f8c9c511b5f1b7dbd45b77f345cb6c048ae6763e WARNING: slcand-start-1.0-r0 do_populate_lic: ${COREBASE}/LICENSE is not a valid license file, please use '${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM. This will become an error in the future ERROR: slcand-start-1.0-r0 do_populate_lic: QA Issue: slcand-start: The LIC_FILES_CHKSUM does not match for file://oe-core/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 slcand-start: The new md5 checksum is b97a012949927931feb7793eee5ed924 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Merge pull request #803 from shr-project/jansa/dunfellPatti Vacek2021-03-031-2/+2
|\ | | | | ostree-kernel-initramfs: Use MIT license.
| * ostree-kernel-initramfs: Use MIT license.Patti Vacek2021-03-021-2/+2
|/ | | | | | | It's a metadata-only recipe and all contributors have agreed that MIT would be preferable. Signed-off-by: Patti Vacek <pattivacek@gmail.com>
* Merge pull request #800 from liuming50/cherry-pick-some-patches-to-dunfellPatti Vacek2021-02-052-1/+2
|\ | | | | Cherry pick some patches to dunfell
| * image_types_ostree.bbclass: get lock before accessing OSTREE_REPOMing Liu2021-01-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit d13ec585ae677affd88b9d92c6ea135cc249b2fa: [ image_types_ostree: use OSTree repo location for lockfiles ] A lockfile ${OSTREE_REPO}/ostree.lock was added to prevent concurrent access to the repository by multiple bitbake instances, but it should not only apply to ostreecommit task, but ostreepush task also need it. This fixes a following race condition error: | | ERROR: Execution of '.../temp/run.do_image_ostreecommit.34262' failed with exit code 1: | error: Writing content object: Creating temp file: No such file or directory Signed-off-by: Ming Liu <liu.ming50@gmail.com>
| * image_types_ota.bbclass: use standard ext4 featuresRicardo Salveti2021-01-301-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | Avoid removing 64bit and metadata_csum by default and prefer the standard ext4 features instead. 64bit enables the file system to be larger than 2^32 blocks and metadata_csum enables metadata checksumming, both of which are enabled by default on recent mke2fs releases. It is unclear why 64bit was disabled by looking at the git history, but my assumption would be that either kernel or userspace was old enough for this feature to not be supported/available. Since this option is currently used by most distros by default, it should now be safe to enable it (requires kernel >= 2.6.28). metadata_csum was disabled in 4d34fa53db to make the u-boot tooling work with the ext4 file system (when saving environment), but the correct fix should instead be a fix at the userspace tooling instead, since not every target requires u-boot. Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* Merge pull request #793 from shr-project/jansa/dunfellAnatoliy Odukha2021-01-111-1/+1
|\ | | | | image_types_ota.bbclass: pass -t ext4 to mke2fs
| * image_types_ota.bbclass: pass -t ext4 to mke2fsMartin Jansa2021-01-031-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* Merge pull request #792 from advancedtelematic/revert-790-jansa/dunfellAnatoliy Odukha2020-12-311-1/+1
|\ | | | | Revert "[dunfell] Fix ota-ext4 IMAGE_FSTYPE"
| * Revert "[dunfell] Fix ota-ext4 IMAGE_FSTYPE"revert-790-jansa/dunfellAnatoliy Odukha2020-12-311-1/+1
|/
* Merge pull request #790 from shr-project/jansa/dunfellAnatoliy Odukha2020-12-311-1/+1
|\ | | | | [dunfell] Fix ota-ext4 IMAGE_FSTYPE
| * image_types_ota.bbclass: pass -t ext4 to mke2fsMartin Jansa2020-12-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
| * Revert "image_types_ota.bbclass: add metadata_csum mkfs option"Martin Jansa2020-12-291-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* Merge pull request #789 from ↵Anatoliy Odukha2020-12-171-56/+6
|\ | | | | | | | | advancedtelematic/feat/refactor-ota-ext4-task-dunfell calculate_size function is redundant
| * image_types_ota.bbclass: add metadata_csum mkfs optionfeat/refactor-ota-ext4-task-dunfellMing Liu2020-12-161-1/+1
| | | | | | | | | | | | | | | | | | 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>
| * image_types_ota.bbclass: call oe_mkext234fs to make ota-ext4 imageMing Liu2020-12-161-56/+6
|/ | | | | | | | | | | | 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>
* Merge pull request #786 from ↵Anatoliy Odukha2020-11-081-1/+1
|\ | | | | | | | | advancedtelematic/feat/dunfell-fix-provisioning-test-timeout test in quemu on CI may need more time to prepare env
| * test in quemu on CI may need more time to prepreare env and provision device.feat/dunfell-fix-provisioning-test-timeoutAnatoliy Odukha2020-11-061-1/+1
|/ | | | Signed-off-by: Anatoliy Odukha <aodukha@gmail.com>
* Merge pull request #781 from advancedtelematic/feat/dunfell/2020.10Anatoliy Odukha2020-10-304-11/+16
|\ | | | | aktualizr: Upgrade dunfell to 2020.10 release
| * ostree-kernel-initramfs: add back initramfs fit workaroundfeat/dunfell/2020.10Ricardo Salveti2020-10-292-3/+8
| | | | | | | | | | | | | | | | | | | | | | 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>
| * image_types_ostree: fix chmodDominik Wild2020-10-291-4/+4
| | | | | | | | Signed-off-by: Dominik Wild <dominik.wild@glutz.com>
| * aktualizr: Upgrade to 2020.10 releaseAnatoliy Odukha2020-10-291-4/+4
|/ | | | Signed-off-by: Anatoliy Odukha <aodukha@gmail.com>
* Merge pull request #779 from advancedtelematic/fix/unused-configsPatrick Vacek2020-10-214-9/+6
|\ | | | | aktualizr: Don't put unused configs in the image.
| * aktualizr: Don't put unused configs in the image.fix/unused-configsPatrick Vacek2020-10-214-9/+6
|/ | | | | | | | | | | | | | | | | 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>
* Merge pull request #776 from shr-project/jansa/dunfellPatrick Vacek2020-10-151-2/+2
|\ | | | | networkd-dhcp-conf: fix REQUIRED_DISTRO_FEATURES
| * networkd-dhcp-conf: fix REQUIRED_DISTRO_FEATURESMartin Jansa2020-10-151-2/+2
|/ | | | | | | | | | | | | | | * 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>
* Merge pull request #775 from advancedtelematic/feat/rm-upstreamed-packagesPatrick Vacek2020-09-286-146/+0
|\ | | | | Feat/rm upstreamed packages
| * softhsm: remove since it was added to meta-openembedded last year.feat/rm-upstreamed-packagesPatrick Vacek2020-09-281-26/+0
| | | | | | | | | | | | It appears to be an almost straight copy of this recipe. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
| * libssh2: Remove redundant bbappend.Patrick Vacek2020-09-281-2/+0
| | | | | | | | | | | | The version in meta-openembedded already supports a native build. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
| * gpgme: Remove redundant bbappend.Patrick Vacek2020-09-281-1/+0
| | | | | | | | | | | | The version in poky already supports a native build. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
| * lshw: remove since it's been in meta-openembedded for a long time.Patrick Vacek2020-09-283-117/+0
|/ | | | | | And it's a newer version at that! Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #773 from ↵Anatoliy Odukha2020-09-072-2/+6
|\ | | | | | | | | liuming50/introduce-OSTREE_MULTI_DEVICETREE_SUPPORT-for-dunfell sota: introduce OSTREE_MULTI_DEVICETREE_SUPPORT
| * sota: introduce OSTREE_MULTI_DEVICETREE_SUPPORTMing Liu2020-09-072-2/+6
|/ | | | | | | | | | | | | | | 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>
* Merge pull request #767 from advancedtelematic/feat/dunfell/2020.9Patrick Vacek2020-09-046-8/+18
|\ | | | | Feat/dunfell/2020.9
| * aktualizr: Upgrade to 2020.9 release.feat/dunfell/2020.9Patrick Vacek2020-08-261-4/+4
| | | | | | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
| * image_repo_manifest.bbclass: fix build when there is no repo on hostMartin Jansa2020-08-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
| * image_repo_manifest.bbclass: explicitly call python3Ming Liu2020-08-261-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Inherit python3native instead of using HOSTTOOLS.Patrick Vacek2020-08-264-1/+7
| | | | | | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
| * qemucommand: Restore custom booloader parameter.Patrick Vacek2020-08-261-1/+4
|/ | | | | | | The functionality was (presumably unintentionally) removed, but the option was still present. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #764 from advancedtelematic/feat/dunfell/headersPatrick Vacek2020-08-121-2/+4
|\ | | | | aktualizr: Bump to latest and install headers in dev package.
| * aktualizr: Bump to latest and install headers in dev package.feat/dunfell/headersPatrick Vacek2020-08-111-2/+4
|/ | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #763 from liuming50/cherry-pick-nfs-utils-fixes-to-dunfellPatrick Vacek2020-08-112-0/+38
|\ | | | | Cherry pick nfs utils fixes to dunfell
| * nfs-utils: don't add nfs-home-mount.service without sota enabledMartin Jansa2020-08-111-4/+4
| | | | | | | | | | | | | | | | | | | | | | * 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-utils: fix nfs systemd daemons runtime issuesMing Liu2020-08-112-0/+38
|/ | | | | | | | | | | | | | | | 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>
* Merge pull request #761 from psaavedra/dunfellPatrick Vacek2020-08-102-60/+0
|\ | | | | Remove boost 1.72 bbappend
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-24 18:24:19 +0000