linux/meta-virtualization.git/recipes-containers/oci-image-tools, branch master-wip

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

oci-image-tools: export GO111MODULE=off

2021-03-01T20:52:39+00:00

With the latest go version bump in oe-core export GO111MODULE is on by default. Our build is not setup to use go modules, so we disable it and avoid configuration errors: no required module provides package ... : working directory is not part of a module Signed-off-by: Bruce Ashfield

oci-image-tools: use GO flags/compiler from recipe

2019-10-15T15:38:53+00:00

The image tools were not building with the oe/cross GO compiler and flags. As such, you could end up with a binary on target with the wong elf interpreter (the host one). With this, we properly use the settings from our build. We also bump the SRCREV to pickup a few minor fixes to the package. Signed-off-by: Bruce Ashfield

oci-image-tools: refresh to tip of master

2019-07-12T14:50:34+00:00

Updating the oci-image-tools to the tip of the master branch. This gets us official integrations of some backported patches (along with other associated minor fixes). Signed-off-by: Bruce Ashfield

oci-image-tools: fix do package qa warning

2018-10-11T18:38:18+00:00

1. After security flag PIE is enabled by default, we might met below QA warning on some arch, like aarch64, fix it by skip textrel QA check refer commit b689c72a of oe-core oci-image-tools-0.2.0-dev+gitAUTOINC+4abe1a166f-r0 do_package_qa: QA Issue: ELF binary 'work/aarch64-poky-linux/oci-image-tools/ 0.2.0-dev+gitAUTOINC+4abe1a166f-r0/packages-split/oci-image-tools/ usr/sbin/oci-image-tool' has relocations in .text [textrel] 2. This problem is caused since security_flags.inc is used by default. so alternative work around is: SECURITY_CFLAGS_pn-oci-image-tools = "${SECURITY_NOPIE_CFLAGS}" SECURITY_LDFLAGS_pn-oci-image-tools = "" Signed-off-by: Changqing Li Signed-off-by: Bruce Ashfield

oci-image-tools: make Config.User mapping errors a warning

2017-11-17T16:06:03+00:00

Rather than throwing an error if we can't map a user to a uid, output a warning. We aren't actually running the code, but are just extracting it .. so the user not existing isn't an issue. With this, we avoid the not-so-useful traces like this: config.User: unsupported format github.com/opencontainers/image-tools/image.(*config).runtimeSpec oci-image-tools/0.2.0-dev+gitAUTOINC+4abe1a166f-r0/oci-image-tools-0.2.0-dev+gitAUTOINC+4abe1a16 6f/src/import/vendor/src/github.com/opencontainers/image-tools/image/config.go:109 <...> src/import/cmd/oci-image-tool/main.go:57 runtime.main /usr/lib64/go/src/runtime/proc.go:185 runtime.goexit /usr/lib64/go/src/runtime/asm_amd64.s:2337 Signed-off-by: Bruce Ashfield

oci-image-tools: fix LICENSE file location

2017-09-14T20:00:43+00:00

Signed-off-by: Bruce Ashfield

nets, docker, runc, oci-*tools: go.bbclass compile fixes

2017-09-14T13:49:00+00:00

Recently in the oe-core the go.bbclass changed and requires the defition of the GO_IMPORT variable. This was intended to simplify how the compilation works with go packages and it is still a work in progress. This patch set makes the recipes compatible to generate the same end result as before using the new go.bbclass from oe-core. Any patches that were included in the recipes had to have the paths adjusted because the new go.bbclass manipulates the notion of S to be S + "src" + "$GO_IMPORT" internally for the purpose of unpack, patch and compile. Signed-off-by: Jason Wessel Signed-off-by: Bruce Ashfield