linux/meta-virtualization.git/recipes-extended/hyperstart, branch master

hyperstart: remove recipe

2024-05-29T16:07:56+00:00

hyperstart is in read-only mode, so we drop it from the layer. A replacement will be provided in the future. Signed-off-by: Bruce Ashfield

recipes/classes/scripts: Drop SRCPV usage

2023-08-24T01:38:21+00:00

bitbake has been enhanced such that SRCPV is no longer needed in PV to handle updating git hashes and task signatures. We can simplify our PV by dropping SRCPV Signed-off-by: Bruce Ashfield

treewide: bulk update patches with status field

2023-01-27T15:32:06+00:00

While the insane.bbclass upstream-status check hasn't been made default, users of meta-virtualization may have it enabled in their distros .. so the effect is the same. We must have this tracking tag in out patches. This is a bulk update to add the tag and silence the QA message. As packages get updated, the normal/routine process of checking the patches will continue, and the status fields may (or may not) get more useful. Signed-off-by: Bruce Ashfield

global: update licence values to SPDX values

2022-02-18T18:07:10+00:00

These changes are the result of running the convert-spdx-licenses.py oe-core script. There's no impact to the build, but we will avoid issues when interacting with core QA by the alignment. Signed-off-by: Bruce Ashfield

global: convert github SRC_URIs to use https protocol

2021-11-02T13:57:03+00:00

github is removing git:// access, and fetches will start experiencing interruptions in service, and eventually will fail completely. bitbake will also begin to warn on github src_uri's that don't use https. So we convert the meta-virt instances to use protocol=https (done using the oe-core contrib conversion script) Signed-off-by: Bruce Ashfield

global: add explicit branch to all SRC_URIs

2021-11-02T13:57:03+00:00

As introduced in the oe-core post: https://lists.openembedded.org/g/openembedded-core/message/157623 SRC_URIs without an explicit branch will generate warnings, and eventually be an error. We run the provided conversion script to make sure that meta-virt is ready for the change. Signed-off-by: Bruce Ashfield

global: overrides syntax conversion

2021-08-02T21:17:53+00:00

OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

hyperstart: update to latest commit

2020-10-08T14:50:28+00:00

Although it appears abandoned, and has some build issues, updating hyperstart to its newest commit to be a base for future work, or simply be removed. Signed-off-by: Bruce Ashfield

hyperstart: refresh 0001-container.c-Fix-compiler-errors-that-gcc-8.1.0-repor.patch to apply cleanly

2020-03-04T00:59:18+00:00

ERROR: hyperstart-v0.2+gitAUTOINC+15bb718ad3-r0 do_patch: Fuzz detected: Applying patch 0001-container.c-Fix-compiler-errors-that-gcc-8.1.0-repor.patch patching file src/container.c Hunk #2 succeeded at 118 with fuzz 1 (offset 17 lines). Hunk #3 succeeded at 148 (offset 18 lines). Hunk #4 succeeded at 158 (offset 18 lines). Hunk #5 succeeded at 167 with fuzz 1 (offset 18 lines). Hunk #6 succeeded at 197 (offset 20 lines). Hunk #7 succeeded at 222 (offset 20 lines). Hunk #8 succeeded at 240 (offset 20 lines). Hunk #9 succeeded at 277 (offset 20 lines). Hunk #10 succeeded at 285 (offset 20 lines). Hunk #11 succeeded at 325 (offset 27 lines). Hunk #12 succeeded at 583 (offset 30 lines). Hunk #13 succeeded at 646 (offset 30 lines). Hunk #14 succeeded at 664 (offset 30 lines). Hunk #15 succeeded at 749 (offset 30 lines). Hunk #16 succeeded at 769 (offset 30 lines). Hunk #17 succeeded at 778 (offset 30 lines). The context lines in the patches can be updated with devtool: devtool modify hyperstart devtool finish --force-patch-refresh hyperstart Don't forget to review changes done by devtool! ERROR: hyperstart-v0.2+gitAUTOINC+15bb718ad3-r0 do_patch: QA Issue: Patch log indicates that patches do not apply cleanly. [patch-fuzz] Signed-off-by: Martin Jansa Signed-off-by: Bruce Ashfield

Use SRCPV instead of SRCREV where possible

2019-01-16T15:28:26+00:00

This change reduces the length of ${PV} for several recipes and gives us auto-incrementing version numbers. Signed-off-by: Paul Barker Signed-off-by: Bruce Ashfield