summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Return python2 to Docker imagefeat/Return-python2-dockerfileOleh Avramenko2021-07-121-0/+2
| | | | Signed-off-by: Oleh Avramenko <ext-oleh.avramenko@here.com>
* Merge pull request #810 from liuming50/drop-prepare_ostree_rootfs-prefuncPatti Vacek2021-07-011-15/+4
|\ | | | | image_types_ostree.bbclass: drop prepare_ostree_rootfs prefunc
| * image_types_ostree.bbclass: drop prepare_ostree_rootfs prefuncMing Liu2021-06-191-15/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The purpose of prepare_ostree_rootfs prefunc is to ensure do_image_rootfs runs from a clean ${OSTREE_ROOTFS} and call oe.path.copyhardlinktree from ${IMAGE_ROOTFS} to ${OSTREE_ROOTFS}. We dont have to maintain a prefunc to achieve that, it could be easily done in do_image_ostree itself. But the major reason for this change is to avoid hard links from ${IMAGE_ROOTFS} to ${OSTREE_ROOTFS}, which might lead to a Pseudo abortion in some cases, which was observed when IMA/EVM is enabled in rootfs. There was a commit aiming to fix the Pseudo abortion, commit db099053: [ image_types_ostree.bbclass: add fakeroot varflag to prepare_ostree_rootfs ] but it's incomplete per later tests, there is still the case some old inodes being used in ${IMAGE_ROOTFS} when do_rootfs runs, which causes 'rm -rf ${IMAGE_ROOTFS}' fail on a Pseudo abortion error. This fixes the Pseudo abortion completely. Signed-off-by: Ming Liu <liu.ming50@gmail.com>
* | Merge pull request #811 from liuming50/support-readonly-sysrootPatti Vacek2021-07-012-0/+5
|\ \ | |/ |/| meta: support readonly sysroot
| * meta: support readonly sysrootMing Liu2021-06-302-0/+5
|/ | | | | | | | Currently ostree sysroot is being mounted as RW by ostree-remount systemd service, add a variable OSTREE_SYSROOT_READONLY to control that, so the end users could choose to mount sysroot as RO. Signed-off-by: Ming Liu <liu.ming50@gmail.com>
* Merge pull request #809 from shr-project/jansa/aktualizrPatti Vacek2021-05-061-8/+0
|\ | | | | aktualizr: drop unnecessary do_configure_prepend
| * aktualizr: drop unnecessary do_configure_prependMartin Jansa2021-04-301-8/+0
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * fails with latest oe-core/master with: https://git.openembedded.org/openembedded-core/commit/meta/classes/cmake.bbclass?id=0fb6280432a36985590d9a714a5f11164aaebb51 because this prepend does "cd ${S}" and doesn't go back to ${B} and cmake_do_configure function doesn't cd to ${B} anymore, resulting in: | CMake Error at CMakeLists.txt:42 (message): | Aktualizr does not support building in the source tree. Please remove | CMakeCache.txt and the CMakeFiles/ directory, then create a subdirectory to | build in: mkdir build; cd build; cmake .. * drop this whole do_configure_prepend as git-native works fine: aktualizr-native/1.0+gitAUTOINC+1255aa24fe-7/git$ grep Setting ../temp/log.do_configure -- Setting version to 2020.10-0-g1255aa24f aktualizr/1.0+gitAUTOINC+1255aa24fe-7/temp$ grep Setting ../temp/log.do_configure -- Setting version to 2020.10-0-g1255aa24f aktualizr/1.0+gitAUTOINC+1255aa24fe-7/build$ which git /OE/build/oe-core/tmp-musl/hosttools/git aktualizr/1.0+gitAUTOINC+1255aa24fe-7/build$ grep GIT CMakeCache.txt GITCOMMAND:FILEPATH=/OE/build/oe-core/tmp-musl/hosttools/git GIT_EXECUTABLE:FILEPATH=/OE/build/oe-core/tmp-musl/hosttools/git //ADVANCED property for variable: GITCOMMAND GITCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Merge pull request #808 from ↵Patti Vacek2021-04-281-0/+1
|\ | | | | | | | | liuming50/add-fakeroot-varflag-to-prepare_ostree_rootfs image_types_ostree.bbclass: add fakeroot varflag to prepare_ostree_ro…
| * image_types_ostree.bbclass: add fakeroot varflag to prepare_ostree_rootfsMing Liu2021-04-081-0/+1
|/ | | | | | | | | | | Since the ostree rootfs is generated by fakeroot, we should make prepare_ostree_rootfs run with fakeroot as well, or else we might run into a pseudo abort issue when removing OSTREE_ROOTFS directory. Reference: https://wiki.yoctoproject.org/wiki/Pseudo_Abort Signed-off-by: Ming Liu <liu.ming50@gmail.com>
* Merge pull request #806 from shr-project/jansa/fixes-licPatti Vacek2021-04-063-5/+3
|\ | | | | fit-conf, ostree-initrd, slcand-start: use COMMON_LICENSE_DIR instead…
| * fit-conf, ostree-initrd, slcand-start: use COMMON_LICENSE_DIR instead of ↵Martin Jansa2021-04-033-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 #805 from shr-project/jansa/fixesPatti Vacek2021-04-061-3/+4
|\ \ | |/ |/| Fix big-update recipe
| * big-update: add LIC_FILES_CHKSUMMartin Jansa2021-04-031-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-031-3/+3
| | | | | | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
| * big-update: use python3Martin Jansa2021-04-031-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>
* Merge pull request #804 from shr-project/jansa/hardknottPatti Vacek2021-03-291-1/+1
|\ | | | | layer.conf: update LAYERSERIES_COMPAT for hardknott
| * layer.conf: update LAYERSERIES_COMPAT for hardknottMartin Jansa2021-03-171-1/+1
|/ | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Merge pull request #802 from advancedtelematic/fix/ostree-kernel-initramfs-mitPatti Vacek2021-02-241-2/+2
|\ | | | | ostree-kernel-initramfs: Use MIT license.
| * ostree-kernel-initramfs: Use MIT license.fix/ostree-kernel-initramfs-mitPatti Vacek2021-02-241-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 #799 from advancedtelematic/fix/python3-repo-bitbakePatti Vacek2021-02-012-11/+10
|\ | | | | Update dockerfiles to use Debian Buster.
| * Update dockerfiles to use Debian Buster.fix/python3-repo-bitbakePatti Vacek2021-01-292-11/+10
| | | | | | | | | | | | This should hopefully resolve some python3/repo issues. Signed-off-by: Patti Vacek <pattivacek@gmail.com>
* | Merge pull request #796 from ricardosalveti/masterPatti Vacek2021-01-291-1/+1
|\ \ | | | | | | image_types_ota.bbclass: use standard ext4 features
| * | image_types_ota.bbclass: use standard ext4 featuresRicardo Salveti2021-01-111-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 #797 from ↵Patti Vacek2021-01-291-0/+1
|\ \ | | | | | | | | | | | | liuming50/fix-race-problems-of-ostreecommit-ota-tasks image_types_ota.bbclass: get lock before accessing OSTREE_REPO
| * | image_types_ostree.bbclass: get lock before accessing OSTREE_REPOMing Liu2021-01-281-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>
* | Merge pull request #798 from wilddom/fix-image_repo_manifestPatti Vacek2021-01-291-1/+1
|\ \ | |/ |/| image_repo_manifest.bbclass: Improvement for builds outside the .repo…
| * image_repo_manifest.bbclass: Improvement for builds outside the .repo directoryDominik Wild2021-01-191-1/+1
|/ | | | | | | The repo tool searches up the directory tree to find the .repo directory, which doesn't work in a separated build directory. Signed-off-by: Dominik Wild <dominik.wild@glutz.com>
* Merge pull request #791 from shr-project/jansa/masterAnatoliy Odukha2021-01-111-1/+1
|\ | | | | [master] Fix ota-ext4 IMAGE_FSTYPE
| * 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 #787 from liuming50/refactor-ota-ext4-taskAnatoliy Odukha2020-12-211-56/+6
|\ | | | | image_types_ota.bbclass: call oe_mkext234fs to make ota-ext4 image
| * image_types_ota.bbclass: add metadata_csum mkfs optionMing Liu2020-11-251-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-11-251-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 #788 from advancedtelematic/fix/python3-for-repoPatti Vacek2020-12-151-2/+5
|\ \ | |/ |/| Use python3 to get repo working again.
| * Use python3 to get repo working again.fix/python3-for-repoPatrick Vacek2020-12-151-2/+5
|/ | | | | | | | The latest version of repo requires python3.6+, but the default Debian package is fine with the default python3 package (although it complains about experimental support). Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #780 from advancedtelematic/feat/2020.10feat/fix-provisioning-test-timeoutAnatoliy Odukha2020-11-034-13/+10
|\ | | | | aktualizr: Upgrade to 2020.10 release
| * aktualizr: Don't put unused configs in the image.feat/2020.10Patrick Vacek2020-11-034-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>
| * aktualizr: Upgrade to 2020.10 releaseAnatoliy Odukha2020-11-031-4/+4
|/ | | | Signed-off-by: Anatoliy Odukha <aodukha@gmail.com>
* Merge pull request #785 from ricardosalveti/sync-dunfellAnatoliy Odukha2020-11-036-146/+0
|\ | | | | Sync recipe/append removals from the dunfell branch
| * softhsm: remove since it was added to meta-openembedded last year.Patrick Vacek2020-10-301-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-10-301-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-10-301-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-10-303-117/+0
|/ | | | | | And it's a newer version at that! Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #778 from ricardosalveti/masterPatrick Vacek2020-10-191-1/+1
|\ | | | | layer.conf: add gatesgarth to LAYERSERIES_COMPAT
| * layer.conf: add gatesgarth to LAYERSERIES_COMPATRicardo Salveti2020-10-161-1/+1
|/ | | | Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* Merge pull request #777 from ricardosalveti/fitPatrick Vacek2020-10-162-3/+8
|\ | | | | ostree-kernel-initramfs: add back initramfs fit workaround
| * ostree-kernel-initramfs: add back initramfs fit workaroundRicardo Salveti2020-10-152-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>
* Merge pull request #774 from wilddom/fix-chmodAnatoliy Odukha2020-09-231-4/+4
|\ | | | | image_types_ostree: fix chmod
| * image_types_ostree: fix chmodDominik Wild2020-09-171-4/+4
|/ | | | Signed-off-by: Dominik Wild <dominik.wild@glutz.com>
* Merge pull request #772 from ↵Patrick Vacek2020-09-072-2/+6
|\ | | | | | | | | liuming50/introduce-OSTREE_MULTI_DEVICETREES_SUPPORT sota: introduce OSTREE_MULTI_DEVICETREE_SUPPORT
| * sota: introduce OSTREE_MULTI_DEVICETREE_SUPPORTMing Liu2020-09-032-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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-09 22:35:02 +0000