meta-virtualization@lists.yoctoproject.org

Home Messages Hashtags Subgroups

Messages

Between

and

Re: thoughts on k3s and supporting builds of more than one k8s version

Please don't use "Yocto" as your name on this list, it may come across to folks who are new to our community as if you're speaking for the project. -- Paul Barker https://pbarker.dev/

By Paul Barker · #6767 ·

[PATCH] libvirt: fix CVE-2021-3631

From: Zqiang <qiang.zhang@...> Selinux MCS generate a single category context and may be accessed by another machine. link: https://gitlab.com/libvirt/libvirt/-/issues/153 Signed-off-by:

By Zhang, Qiang <qiang.zhang@...> · #6766 ·

Re: thoughts on k3s and supporting builds of more than one k8s version

Kubernetes 1.21 version: someone perhaps wants, say, 1.20 to go with a system with 1.21, while someone else perhaps wants 1.21 to go with 1.21 components. for the versions, and small recipes with the

By Yocto · #6765 ·

thoughts on k3s and supporting builds of more than one k8s version

Hi! I was thinking about k3s, and now that the latest stable k3s is a Kubernetes 1.21 version: Do we want to have recipes for multiple k3s versions? I'm thinking someone perhaps wants, say, 1.20 to

By Joakim Roubert · #6764 ·

[PATCH] openvswitch: fix CVE-2021-36980

From: Zqiang <qiang.zhang@...> Open vSwitch (aka openvswitch) 2.11.0 through 2.15.0 has a use-after-free in decode_NXAST_RAW_ENCAP (called from ofpact_decode and ofpacts_decode) during the

By Zhang, Qiang <qiang.zhang@...> · #6763 ·

container build not pulling in libraries

I have a question regarding containers and was curious if you could provide some assistance. I have built container image using my own recipe. The recipe pulls in other recipes such as mono

By al.smith@fujitsu.com · #6762 ·

Re: [PATCH dunfell] containers: Explictly reference a valid branch

Hi Bruce, Excellent, I am able to build dunfell now. Thanks! Fabio Estevam -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194

By Fabio Estevam · #6761 ·

Re: [master][PATCHv2] lxc: Enable seccomp support for lxc

v2 is now merged. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II

By Bruce Ashfield · #6760 ·

Re: [PATCH 0/4] Xen Test Framework OEQA

In message: [meta-virtualization][PATCH 0/4] Xen Test Framework OEQA on 31/08/2021 Christopher Clark wrote: These have now been merged to master! Thanks for the series. Bruce

By Bruce Ashfield · #6759 ·

Re: [PATCH dunfell] containers: Explictly reference a valid branch

These have been cherry-picked into dunfell. Cheers, Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II

By Bruce Ashfield · #6758 ·

Re: [PATCH dunfell] containers: Explictly reference a valid branch

Hi Bruce, I am working on dunfell. Could you please cherry-pick the four commits below to dunfell to fix the build? oci-image-spec_git:

By Fabio Estevam · #6757 ·

Re: [PATCH v3] python3: remove the no-longer required bbappend

Cherry-picked and pushed. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II

By Bruce Ashfield · #6756 ·

Re: [PATCH dunfell] containers: Explictly reference a valid branch

You are working on an out of date master, or an old branch. If you want some of the branch changes cherry picked, specify the commit and branch, and I can do that. Bruce -- - Thou shalt not follow

By Bruce Ashfield · #6755 ·

[PATCH dunfell] containers: Explictly reference a valid branch

These repositories have dropped their master branches, so the fetcher default no longer works. Point to an existing branch to fix the fetch failure. Signed-off-by: Fabio Estevam

By Fabio Estevam · #6754 ·

Re: [PATCH 2/2] skopeo: Upgrade to 1.4.1

There's no value in doing that. There aren't specific "more stable" or "development" releases. That simply doubles maintenance and splits our testing. By the time meta-virt 'releases' against

By Bruce Ashfield · #6753 ·

Re: [PATCH v3] python3: remove the no-longer required bbappend

On 8/2/21 11:45 AM, Bruce Ashfield wrote: Hi, Bruce Can this be cherry-picked into hardnott please? python3-native build also failed on hardnott. Thanks

By Changqing Li · #6752 ·

Re: [PATCH 2/2] skopeo: Upgrade to 1.4.1

If so, could we put two recipes here? one is for dev version such as podman-dev.bb and one such as podman_git.bb to track the latest release? Thanks,

By Yu, Mingli · #6751 ·

Re: [PATCH 2/2] skopeo: Upgrade to 1.4.1

In this case, it is just a commit that bumps the version in preparation for more changes (for 3.3.2), if you look at the historical SRCREV bumps, I always take those changes. There's no reason to

By Bruce Ashfield · #6750 ·

Re: [PATCH 2/2] skopeo: Upgrade to 1.4.1

Okay, I will send the packageconfig part then. BTW, why is there dev version, I think the latest release version should satisfy most of our needs. Thanks,

By Yu, Mingli · #6749 ·

Re: [PATCH 2/2] skopeo: Upgrade to 1.4.1

Actually cancel that. I have more -dev versions under test (I got my uprev's confused for a moment). But we don't want this SRCREV change. I put it to the tip of the release branch on purpose, this

By Bruce Ashfield · #6748 ·

1321 - 1340 of 8081

Home Hashtags Subgroups Terms