Port to Yocto scarthgap [Part2]#1540
Conversation
974846e to
ab3f112
Compare
|
Mostly fine, but please improve the commit message saying why things were removed, renamed or reverted. |
Covert the recipe with the oe-go-mod-autogen [1] helper script. The tool will autogenerate all the required files: modules.txt relocation.inc src_uri.in Main step to perform: | ../meta-virtualization/scripts/oe-go-mod-autogen.py --repo https://github.com/docker/compose --rev v2.21.0 | mv modules.txt ../meta-lmp/meta-lmp-base/recipes-containers/docker-compose/files | mv relocation.inc src_uri.inc ../meta-lmp/meta-lmp-base/recipes-containers/docker-compose | # manualy update PV and SRCREV [1] https://git.yoctoproject.org/meta-virtualization/tree/scripts/README-oe-go-mod-autogen.txt Signed-off-by: Jose Quaresma <[email protected]>
Signed-off-by: Jose Quaresma <[email protected]>
Included in openssl 3.2.0 https://git.yoctoproject.org/poky/commit/?id=5369e2f5c5db497b798fcce96eb597235e4c952a Signed-off-by: Jose Quaresma <[email protected]>
ab3f112 to
eec74d1
Compare
Suggestions added and fixed. |
There was a problem hiding this comment.
I understand we are reverting this commit as a consequence of PACKAGECONFIG:remove = "static" in the previous commit
There was a problem hiding this comment.
I still have the impression that static will be required, but would need to validate at runtime.
There was a problem hiding this comment.
I understand we are reverting this commit as a consequence of PACKAGECONFIG:remove = "static" in the previous commit
Yes, the reason of the revert is the previous commit but I will mention that on message.
I still have the impression that static will be required, but would need to validate at runtime.
The main reason of this was to support the composefs.
There was a problem hiding this comment.
What is the plan for the documentation of this process, @igoropaniuk ?
Signed-off-by: Jose Quaresma <[email protected]>
Added to fix the lack of systemd in the initramfs [1] but look like is not need anymore. [1] foundriesio@17d647d Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit 0abb08c. Since we disabled the static, we no longer need this. Signed-off-by: Jose Quaresma <[email protected]>
Signed-off-by: Jose Quaresma <[email protected]>
Signed-off-by: Jose Quaresma <[email protected]>
- Switch to meta-virt[scarthgap] 1.2.0-rc.2: from 1.1.12 Signed-off-by: Jose Quaresma <[email protected]>
- Switch to meta-virt[scarthgap] v2.0.0-beta.0: from v1.7.13 Signed-off-by: Jose Quaresma <[email protected]>
- Switch to meta-virt[scarthgap] v2.28.1: from v2.21.0 - We will keep our cli-config-support-default-system-config.patch applied Signed-off-by: Jose Quaresma <[email protected]>
- Switch to meta-virt[scarthgap] 27.0.3: from 25.0.2-ce+git-fce6e0c Signed-off-by: Jose Quaresma <[email protected]>
The meta-virt scarthgap branch has droped the docker-ce and only keeps docker-moby. So curretly only one version exist and the PREFERRED_PROVIDER is not more need. Signed-off-by: Jose Quaresma <[email protected]>
The meta-virt scarthgap branch has droped the docker-ce and only keeps docker-moby. Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit 36ab4c6. - Switch to meta-security[scarthgap] 5.7: from 5.5 Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit aee51bd. - Switch to meta-security[scarthgap] 3.0.0: from 3.0.0 Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit 17f5095. - Switch to meta-security[scarthgap] 4.0.2: from 4.0.1 Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit 67c2334. - Switch to meta-security[scarthgap] 1.9.0: from 1.9.0 Signed-off-by: Jose Quaresma <[email protected]>
…hanges Includes: - 733b9787 tegra-helper-scripts: remove fuselevel settings in initrd-flash script OE4T/meta-tegra@733b978 Signed-off-by: Jose Quaresma <[email protected]>
The master branch have the 1.18 witch don't need it Signed-off-by: Jose Quaresma <[email protected]>
the generic-arm64 machine was removed from the meta-arm layer and is now part of the meta-yocto-bsp layer. also renamed: generic-arm64 -> genericarm64 https://git.yoctoproject.org/meta-arm/commit/meta-arm/conf/machine?h=scarthgap&id=10e23fe1dfa66513dbda668d807ea3e384eff49c https://git.yoctoproject.org/poky/commit/meta-yocto-bsp/conf/machine?h=scarthgap&id=2f4f72fff2b642beff179530a74403fa2c608b64 Signed-off-by: Jose Quaresma <[email protected]>
Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit 9986c69. Not need anymore with the scarthgap, fix the error: | ERROR: Layer stm-st-stm32mp is not compatible with the core layer which only supports these series: scarthgap (layer is compatible with kirkstone) Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit 915af2c. - Reverts scarthgap meson backport bsp: meson: Backport 1.3.1.imx from scarthgap foundriesio#1459 Signed-off-by: Jose Quaresma <[email protected]>
This reverts commit c8db41e. - Reverts scarthgap meson backport bsp: meson: Backport 1.3.1.imx from scarthgap foundriesio#1459 Signed-off-by: Jose Quaresma <[email protected]>
I will move the fioefi patchset again to the scarthgap-next branch that contains what is still pending |
eec74d1 to
e0dfbbc
Compare
|
Thanks for the review |
When you create it, please add me to the reviewers. I'm afraid github inbox don't notify me, and it's still pending in my mind what level of documentation the change requires. Thanks |
I have already move it to https://github.com/foundriesio/meta-lmp/commits/scarthgap-next |
The full PR was submitted #1532 but it was very big and we decided to break it down into smaller parts to facilitate the review process.
These small parts have not been tested at all and only the complete PR has been, so it is quite possible that they will not work separately as they are submitted now.
The full list of changes that have been tested are at https://github.com/foundriesio/meta-lmp/tree/scarthgap-next
Rebased on top of #1538