linux/meta-virtualization.git/recipes-containers/oci-image-tools/oci-image-tools_git.bb, branch hardknott

global: add explicit branch to all SRC_URIs

2021-12-03T14:01:33+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

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

oci-image-tools: uprev to 0.2.0-dev

2017-09-13T21:23:30+00:00

To work with OCI spec v1.0 images/containers we need to update our tools. Signed-off-by: Bruce Ashfield

oci-image-tools: update to latest and fix symlink issues

2017-06-07T03:44:34+00:00

Updating to the latest oci-image-tools for better support in unpack/creating runtime bundles. With this update, we get a single tool with subcommands, versus separate commands previously. We also add two proposed (but not merged) patches that can deal with existing symlinks when unpacking layers. Without this, we fail to unpack many complex containers due to duplicate files in layers. Signed-off-by: Bruce Ashfield