<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-virtualization.git/recipes-core/packagegroups, branch nanbield</title>
<subtitle>Mirror of git.yoctoproject.org/meta-virtualization</subtitle>
<id>https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=nanbield</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=nanbield'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/'/>
<updated>2023-11-06T16:21:12+00:00</updated>
<entry>
<title>packagegroup-container: require ipv6 for podman</title>
<updated>2023-11-06T16:21:12+00:00</updated>
<author>
<name>Jörg Sommer</name>
<email>joerg.sommer@navimatix.de</email>
</author>
<published>2023-10-12T11:52:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=002aaf7029b8002acc69c9d4beea89039410d7cd'/>
<id>urn:sha1:002aaf7029b8002acc69c9d4beea89039410d7cd</id>
<content type='text'>
The recipe *podman* requires the distro feature *ipv6*. Using a distro
without it causes the build of *packagegroup-container* fails, even if
*packagegroup-podman* is not used:

    ERROR: Nothing RPROVIDES 'podman' (but /build/../work/layers-3rdparty/meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it)
    podman was skipped: missing required distro feature 'ipv6' (not in DISTRO_FEATURES)
    NOTE: Runtime target 'podman' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['podman']
    NOTE: Runtime target 'packagegroup-docker' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['packagegroup-docker', 'podman']

Signed-off-by: Jörg Sommer &lt;joerg.sommer@navimatix.de&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>packagegroup-kubernetes: set COMPATIBLE_HOST</title>
<updated>2023-09-15T17:30:14+00:00</updated>
<author>
<name>Kai Kang</name>
<email>kai.kang@windriver.com</email>
</author>
<published>2023-09-14T07:52:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=14a3a0393765ac227d7416818fccef68985f63ef'/>
<id>urn:sha1:14a3a0393765ac227d7416818fccef68985f63ef</id>
<content type='text'>
packagegroup-kubernetes requires kubernetes which is only compatible
with x86_64, arm and aarch64, so set COMPATIBLE_HOST for
packagegroup-kubernetes to align with it.

Signed-off-by: Kai Kang &lt;kai.kang@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>packagegroup-container: not compatible with mips and riscv</title>
<updated>2023-09-15T17:30:14+00:00</updated>
<author>
<name>Kai Kang</name>
<email>kai.kang@windriver.com</email>
</author>
<published>2023-09-14T07:52:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=ebcc1cd73d7f1445e5421079e7f337d032458fd3'/>
<id>urn:sha1:ebcc1cd73d7f1445e5421079e7f337d032458fd3</id>
<content type='text'>
The recipe docker-moby which is required by packagegroup-container is
not compatible with mips. And it inherits goarch.bbclass, so it is not
compatible with riscv32 too. Update COMPATIBLE_HOST accordingly for
packagegroup-container.

Signed-off-by: Kai Kang &lt;kai.kang@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>oci-image-tools: don't build for riscv64</title>
<updated>2023-09-04T03:05:49+00:00</updated>
<author>
<name>Changqing Li</name>
<email>changqing.li@windriver.com</email>
</author>
<published>2023-09-01T09:03:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=8f25bfcbae987ed3b1bed82d6d9f937f3739362f'/>
<id>urn:sha1:8f25bfcbae987ed3b1bed82d6d9f937f3739362f</id>
<content type='text'>
Currently oci-image-tools has a do_compile error for riscv64. The
problem could be reproduced by:
    MACHINE=qemuriscv64 bitbake oci-image-tools

So explicitly set COMPATIBLE_HOST here to avoid it building for riscv64.
When someone interested in using this recipe for riscv64 fixes the
compile issue, this setting could be removed.

Also don't build packagegroup-container/packagegroup-kubernetes since
they depends on oci-image-tools

Signed-off-by: Changqing Li &lt;changqing.li@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>kubernetes: install kubeadm and misc for nodes</title>
<updated>2021-12-15T17:59:18+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-12-15T17:57:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=d4415a1ff705e1439a54d73938aede6b7058ca15'/>
<id>urn:sha1:d4415a1ff705e1439a54d73938aede6b7058ca15</id>
<content type='text'>
To ensure nodes can join the cluster, and have the proper configuration
of some kernel options we add two more packages to the packagegroup

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>k8s: add kubernetes to host packagegroup</title>
<updated>2021-12-13T17:27:11+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-12-10T21:09:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=fc5fdd79e082e69f3e0c145412516314fbf00f0b'/>
<id>urn:sha1:fc5fdd79e082e69f3e0c145412516314fbf00f0b</id>
<content type='text'>
Install the core kubernetes package (and RDEPENDS) as part of the
host packagegroup.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>virtual/containerd: don't rprovide virtual/</title>
<updated>2021-09-06T14:57:17+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-09-06T14:28:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=7b46286b34b35f8c1aba7adcccd1d84bc901caf5'/>
<id>urn:sha1:7b46286b34b35f8c1aba7adcccd1d84bc901caf5</id>
<content type='text'>
Similar to the oe-core commit:

   commit 93ac180d8c389f16964bce8bd5538d9389e970e6
   Author: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
   Date:   Wed Sep 1 11:20:20 2021 +0200

       meta: stop using "virtual/" in RPROVIDES and RDEPENDS

       Fixes [YOCTO #14538]

       Recipes shouldn't use the "virtual/" string in RPROVIDES and RDEPENDS.

       That's confusing because "virtual/" has no special meaning in
       RPROVIDES and RDEPENDS (unlike in PROVIDES and DEPENDS).

       Instead, using "virtual-" instead of "virtual/"
       as already done in the glibc recipe.

We stop rproviding virtual/containerd to keep the namespace clean.
There aren't many users of this virtual provides, but we keep
it around (for now) to maintain compatibility.

At the same time we convert the RPROVIDES to virtual-containerd, to keep
it available and consistent with oe-core use virtual-libc, etc.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>virtual/runc: don't rprovide virtual/</title>
<updated>2021-09-06T14:57:17+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-09-06T14:28:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=263e4d3d4e36ccdbd660ba252f5eee6309a130cf'/>
<id>urn:sha1:263e4d3d4e36ccdbd660ba252f5eee6309a130cf</id>
<content type='text'>
Similar to the oe-core commit:

   commit 93ac180d8c389f16964bce8bd5538d9389e970e6
   Author: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
   Date:   Wed Sep 1 11:20:20 2021 +0200

       meta: stop using "virtual/" in RPROVIDES and RDEPENDS

       Fixes [YOCTO #14538]

       Recipes shouldn't use the "virtual/" string in RPROVIDES and RDEPENDS.

       That's confusing because "virtual/" has no special meaning in
       RPROVIDES and RDEPENDS (unlike in PROVIDES and DEPENDS).

       Instead, using "virtual-" instead of "virtual/"
       as already done in the glibc recipe.

We stop rproviding virtual/runc to keep the namespace clean.
There aren't many users of this virtual provides, but we keep
it around (for now) to maintain compatibility.

At the same time we convert the RPROVIDES to virtual-runc, to keep
it available and consistent with oe-core use virtual-libc, etc.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>global: overrides syntax conversion</title>
<updated>2021-08-02T21:17:53+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-07-28T18:22:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=d876cfc5bfafa516dee55d04b50b319a22165640'/>
<id>urn:sha1:d876cfc5bfafa516dee55d04b50b319a22165640</id>
<content type='text'>
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 &lt;richard.purdie@linuxfoundation.org&gt;
    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 &lt;richard.purdie@linuxfoundation.org&gt;

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>packagegroup-container: Include podman if seccomp is in DISTRO_FEATURES</title>
<updated>2021-06-30T15:19:21+00:00</updated>
<author>
<name>Diego Sueiro</name>
<email>diego.sueiro@arm.com</email>
</author>
<published>2021-06-24T18:59:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=66994bf37e6a94949f12fd3393f2f7e0927ded62'/>
<id>urn:sha1:66994bf37e6a94949f12fd3393f2f7e0927ded62</id>
<content type='text'>
Signed-off-by: Diego Sueiro &lt;diego.sueiro@arm.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
</feed>
