Mirror of github.com/advancedtelematic/meta-updater https://git.enea.com/cgit/linux/meta-updater.git/atom?h=fix%2Fmeta-python-depend 2019-02-21T15:32:49+00:00 2019-02-21T15:32:49+00:00 Patrick Vacek patrickvacek@gmail.com 2019-02-21T15:27:44+00:00 urn:sha1:202a8c70ba8cdcfb39cf8e2b19a08b5f8850a0f9 To enable simultaneous bitbaking of two images with the same branch name, create a new ref in the OSTree repo using the basename of the image. As @OYTIS has pointed out, this probably won't solve every problem that might come up with simultaneous bitbaking, such as if the two images use different bootloaders. However, it does solve the immediate problem that comes up with our primary-image + secondary-image example. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com> 2019-02-12T08:10:14+00:00 Patrick Vacek patrickvacek@gmail.com 2019-02-12T08:10:14+00:00 urn:sha1:29c3476c8286649210ab8d731bfa063c76907f3b sota.bbclass: fix a variable assignment regression 2019-02-05T11:52:04+00:00 Anton Gerasimov anton.gerasimov@here.com 2019-02-05T11:39:56+00:00 urn:sha1:495f5db09da6a1e5b7a16460d9f4bf26fbee2dff Signed-off-by: Anton Gerasimov <anton.gerasimov@here.com> 2019-01-31T15:41:03+00:00 Ming Liu liu.ming50@gmail.com 2019-01-29T20:05:38+00:00 urn:sha1:168efb38411ed4feae6d99e4ae00c867ceff3fba A regression was introduced by commit 9dcfcdb9: [ classes, images: Use standard variables for initramfs ] it replaced OSTREE_INITRAMFS_IMAGE with INITRAMFS_FSTYPES which is fine, but the '??=' should be changed to "?=" as well, or else it will not take effect since INITRAMFS_FSTYPES's already set in bitbake.conf with '?='. Signed-off-by: Ming Liu <liu.ming50@gmail.com> 2019-01-14T13:15:06+00:00 Ming Liu liu.ming50@gmail.com 2019-01-14T13:06:48+00:00 urn:sha1:d49ae8261680ae2cfd4c0179eff013d2def92e1b Search made with the following regex: getVar ?\((.*), True\), this is to be consistent with OE. Signed-off-by: Ming Liu <liu.ming50@gmail.com> 2019-01-14T13:15:06+00:00 Ming Liu liu.ming50@gmail.com 2019-01-14T13:01:26+00:00 urn:sha1:2782c5c6243736884bcb6f901ed828014601787f type -> size. Signed-off-by: Ming Liu <liu.ming50@gmail.com> 2019-01-11T08:11:31+00:00 Luka Pivk luka.pivk@toradex.com 2019-01-10T10:41:55+00:00 urn:sha1:6cc3ab1c90f84feed212ea5cc2b4e6b1af1b2b2e Adds initramfs and/or devicetree into checksum calculation. According to ostree documentation if devicetree and/or initramfs are included into ostree, checksum should also include them. Signed-off-by: Luka Pivk <luka.pivk@toradex.com> 2019-01-07T13:14:42+00:00 Patrick Vacek patrickvacek@gmail.com 2019-01-07T13:14:42+00:00 urn:sha1:03ed45db93f511ee5fbc766436d5330ca33bf278 We remove GARAGE_SIGN_REPO at the start and end of this task, which causes trouble if two images call this task at the same time. This probably could be fixed in a better fashion (like putting the repo in an image-specific subdirectory) but this is quick and easy, and the task usually doesn't take long to run, so the lack of parallelization is not a big loss. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com> 2018-12-14T10:24:55+00:00 Patrick Vacek patrickvacek@gmail.com 2018-12-14T10:24:55+00:00 urn:sha1:cb8aec948c6c667cb0b0ebffddd2bebda00c7080 classes/image_types_ostree.bbclass: add device tree to boot/devicetree 2018-12-14T08:30:25+00:00 Luka Pivk luka.pivk@toradex.com 2018-11-27T11:42:14+00:00 urn:sha1:4f267b8acf4c0c2401f827c08b0e18da943c873a Include device trees into boot/devicetree-*-checksum. Device trees with this name format get picked up by ostree and copied into boot/. Ostree also generates entry inside uEnv.txt called fdt_file pointing to this device tree. Normaly one would include only one device tree. If KERNEL_DEVICETREE includes more then one device tree this will add all the device trees but ostree will still pick only one device tree and include it into boot. We are working on modifications to ostree so it will pickup all the device trees. Signed-off-by: Luka Pivk <luka.pivk@toradex.com>