summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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 #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>
* Merge pull request #771 from shr-project/jansa/masterPatrick Vacek2020-08-311-2/+2
|\ | | | | networkd-dhcp-conf: fix REQUIRED_DISTRO_FEATURES
| * networkd-dhcp-conf: fix REQUIRED_DISTRO_FEATURESMartin Jansa2020-08-291-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 #766 from advancedtelematic/feat/2020.9Patrick Vacek2020-08-271-4/+4
|\ | | | | aktualizr: Upgrade to 2020.9 release.
| * aktualizr: Upgrade to 2020.9 release.feat/2020.9Patrick Vacek2020-08-261-4/+4
|/ | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #765 from shr-project/jansa/masterPatrick Vacek2020-08-181-1/+1
|\ | | | | image_repo_manifest.bbclass: fix build when there is no repo on host
| * image_repo_manifest.bbclass: fix build when there is no repo on hostMartin Jansa2020-08-181-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>
* Merge pull request #762 from liuming50/fix-a-repo-tool-failed-issuePatrick Vacek2020-08-111-2/+3
|\ | | | | image_repo_manifest.bbclass: explicitly call python3
| * image_repo_manifest.bbclass: explicitly call python3Ming Liu2020-08-101-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>
* Merge pull request #759 from advancedtelematic/feat/headersPatrick Vacek2020-08-071-2/+4
|\ | | | | aktualizr: Bump to latest and install headers in dev package.
| * aktualizr: Bump to latest and install headers in dev package.feat/headersPatrick Vacek2020-08-061-2/+4
| | | | | | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* | Merge pull request #760 from advancedtelematic/fix/master/rpi-bootfiles-appendPatrick Vacek2020-08-071-2/+3
|\ \ | |/ |/| sota_raspberrypi: Use new variable for bootfiles path.
| * sota_raspberrypi: Use new variable for bootfiles path.fix/master/rpi-bootfiles-appendPatrick Vacek2020-08-071-2/+3
|/ | | | | | | | This was changed in f046b4128c9ca3420614887006101fa2b10fc6e7 of meta-raspberrypi. This also requires e947e8590f74477505c754d016d99fc71cadf4e1 in meta-updater-raspberrypi. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #757 from advancedtelematic/fix/pythonnativePatrick Vacek2020-08-034-1/+7
|\ | | | | Inherit python3native instead of using HOSTTOOLS.
| * Inherit python3native instead of using HOSTTOOLS.fix/pythonnativePatrick Vacek2020-08-034-1/+7
| | | | | | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* | Merge pull request #754 from shr-project/jansa/masterPatrick Vacek2020-07-301-4/+4
|\ \ | | | | | | nfs-utils: don't add nfs-home-mount.service without sota enabled
| * | nfs-utils: don't add nfs-home-mount.service without sota enabledMartin Jansa2020-07-261-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>
* | Merge pull request #756 from advancedtelematic/fix/restore-bootloader-optionPatrick Vacek2020-07-291-1/+4
|\ \ | |/ |/| qemucommand: Restore custom booloader parameter.
| * qemucommand: Restore custom booloader parameter.fix/restore-bootloader-optionPatrick Vacek2020-07-291-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 #753 from liuming50/fix-nfs-utils-issuesPatrick Vacek2020-07-142-0/+38
|\ | | | | nfs-utils: fix nfs systemd daemons runtime issues
| * nfs-utils: fix nfs systemd daemons runtime issuesMing Liu2020-07-102-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 #748 from advancedtelematic/feat/2020.8Patrick Vacek2020-07-131-4/+4
|\ \ | |/ |/| aktualizr: Bump to 2020.8 release.
| * aktualizr: Bump to 2020.8 release.feat/2020.8Patrick Vacek2020-07-091-4/+4
|/ | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Merge pull request #745 from antznin/fix-dtb-deploymentPatrick Vacek2020-07-071-1/+4
|\ | | | | ostree-kernel-initramfs: fix devicetree deployment
| * ostree-kernel-initramfs: fix devicetree deploymentantznin2020-07-031-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Merge pull request #746 from liuming50/fix-a-naming-issuePatrick Vacek2020-07-071-1/+1
|\ \ | |/ |/| image_types_ota.bbclass: change IMAGE_BASENAME to PN
| * image_types_ota.bbclass: change IMAGE_BASENAME to PNMing Liu2020-07-041-1/+1
|/ | | | | | | | | 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-09 21:22:51 +0000