Ack'd. Holding on the queueing of the change. I don't see a problem, I typically just follow whatever the project is either putting in the README or their git tags. I just did a check, and indeed,

Nothing in Xen respects --enable-sdl, and nothing in Xen links to libSDL, so this PACKAGECONFIG is obsolete. It looks like the last user of SDL in Xen was removed in "Remove internal tools/ioemu

Stand by for a v2 on this one. It needs a musl fix. Also, do you see any issues in using 1.9 vs 1.9.0 as a version? They both are semver compliant. -- Andrei Gherzan gpg: rsa4096/D4D94F67AD0E9640

Hello Bruce, How do you generate the images and import them? Could you describe a bit more the use case? With podman for example you can load the image by using `podman load -i

<vasileios.anagnostopoulos@...> wrote: The tar file was never actually intended to be used in that way, hence why the directory is maintained. It is just there for easier transport of the oci

Hi Christopher, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Also I applied this in kirkstone and did a build and run on arm64, arm32 and x86 with success so: Tested-by: Bertrand Marquis

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- ...-Fix-buffer-overflow-on-workdir-path.patch | 32 +++++++++++++++++++

From: Andrei Gherzan <andrei.gherzan@...> This support is disabled by default and exposed via PACKAGECONFIG. Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- docs/00-INDEX

From: Andrei Gherzan <andrei.gherzan@...> Podman can run in via a docker symlink emulating docker commands. By default this generates a runtime warning. This change silences it via the

From: Andrei Gherzan <andrei.gherzan@...> slirp4netns uses a TAP device to connect to the internet in an unprivileged way. Without the required kernel support (TAP/TUN), slirp4netns will fail

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- ...-Fix-buffer-overflow-on-workdir-path.patch | 32 -------------------

Skip the inclusion of the parent directory in the tar file. Most tools expect a tar file without it. An example of this use case is skopeo, where the skopeo copy oci-archive command will not work with

Add an optional parameter that allows to override the stop signal that is used. Signed-off-by: Vasileios Anagnostopoulos <vasileios.anagnostopoulos@...> --- classes/image-oci-umoci.inc | 4

From: Pascal Bach <pascal.bach@...> Signed-off-by: Pascal Bach <pascal.bach@...> --- classes/image-oci-umoci.inc | 34 +++++++++++++++++----------------- 1 file changed, 17

FWIW, that's more than just bug fixes, so we wouldn't want that much of a version bump on any of the -stable branches. They'd stay within the .x series of a release. What you are describing is

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- ...-Fix-buffer-overflow-on-workdir-path.patch | 32 +++++++++++++++++++

From: Andrei Gherzan <andrei.gherzan@...> This support is disabled by default and exposed via PACKAGECONFIG. Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- docs/00-INDEX

From: Andrei Gherzan <andrei.gherzan@...> Podman can run in via a docker symlink emulating docker commands. By default this generates a runtime warning. This change silences it via the

From: Andrei Gherzan <andrei.gherzan@...> slirp4netns uses a TAP device to connect to the internet in an unprivileged way. Without the required kernel support (TAP/TUN), slirp4netns will fail

Perhaps someone here can help point me to relevant documentation. I'm wondering if there are some guidelines about which version(s) of docker/containerd/runc are compatible. I've searched through