<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-virtualization.git/recipes-containers/lxcfs, 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-09-07T21:00:53+00:00</updated>
<entry>
<title>lxcfs: add systemd to REQUIRED_DISTRO_FEATURES</title>
<updated>2023-09-07T21:00:53+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2023-09-07T14:32:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=113af45b75d2a19726d3e084e9ba05826128097b'/>
<id>urn:sha1:113af45b75d2a19726d3e084e9ba05826128097b</id>
<content type='text'>
lxcfs requires systemd, so we add it to the feature check.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>lxcfs: update to 5.0.4 and convert to meson</title>
<updated>2023-08-24T01:38:21+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2023-08-03T15:18:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=4ecc9488d1df262c70e784dabfcf8329ba8fa60c'/>
<id>urn:sha1:4ecc9488d1df262c70e784dabfcf8329ba8fa60c</id>
<content type='text'>
This is a large update to lxcfs, that includes a move to meson as the
build backend.

We drop a couple of uneeded patches, and add a new meson specific one
as the detection of pid_* functions is failing.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>lxcfs: fix build with newer linux-libc-headers</title>
<updated>2023-05-08T22:41:38+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2023-05-03T06:38:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=d1b6bf580edb2ee2dce806a80994601366e3c0cd'/>
<id>urn:sha1:d1b6bf580edb2ee2dce806a80994601366e3c0cd</id>
<content type='text'>
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>treewide: bulk update patches with status field</title>
<updated>2023-01-27T15:32:06+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2023-01-27T15:05:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=211918936180a0b2a5af770bd5c52025d34221db'/>
<id>urn:sha1:211918936180a0b2a5af770bd5c52025d34221db</id>
<content type='text'>
While the insane.bbclass upstream-status check hasn't been made
default, users of meta-virtualization may have it enabled in their
distros .. so the effect is the same. We must have this tracking
tag in out patches.

This is a bulk update to add the tag and silence the QA message.

As packages get updated, the normal/routine process of checking
the patches will continue, and the status fields may (or may not)
get more useful.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>global: update licence values to SPDX values</title>
<updated>2022-02-18T18:07:10+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2022-02-18T18:05:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=108e089f7e844fafd12cfddd7eb6f96bef86c0a3'/>
<id>urn:sha1:108e089f7e844fafd12cfddd7eb6f96bef86c0a3</id>
<content type='text'>
These changes are the result of running the convert-spdx-licenses.py
oe-core script.

There's no impact to the build, but we will avoid issues when
interacting with core QA by the alignment.

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>lxcfs: update to 4.0.7</title>
<updated>2021-02-07T13:20:30+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-02-07T13:14:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=0904b0a7788d22f32d28541197c898e032107c99'/>
<id>urn:sha1:0904b0a7788d22f32d28541197c898e032107c99</id>
<content type='text'>
Bumping to the latest available lxcfs. As part of this update,
the license has changed to LGPL-2.1+ (from Apache-2.0)

We also refresh our systemd patch to continue to apply.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>lxcfs: uprev from v3.0.1 to v3.0.3</title>
<updated>2018-12-04T23:15:14+00:00</updated>
<author>
<name>Mark Asselstine</name>
<email>mark.asselstine@windriver.com</email>
</author>
<published>2018-11-30T21:46:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=8e2ef132c1b1416808c403851206740dcec284db'/>
<id>urn:sha1:8e2ef132c1b1416808c403851206740dcec284db</id>
<content type='text'>
A very small # of new commits. Most are minor bug fixes, no feature
work. I looked at adding ptests but the tests are mostly in an
unusable state at the moment, for example several require cgm despite
cgmanager being deprecated. So I have opted to continue without them
and only when we can work with upstream to improve their testing can
we seriously consider adding them.

Signed-off-by: Mark Asselstine &lt;mark.asselstine@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>lxcfs: move recipe from meta-overc to here</title>
<updated>2018-10-04T13:31:19+00:00</updated>
<author>
<name>Mark Asselstine</name>
<email>mark.asselstine@windriver.com</email>
</author>
<published>2018-10-02T18:43:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=f7738717b864f4d7a454034092c66bf95061bfcf'/>
<id>urn:sha1:f7738717b864f4d7a454034092c66bf95061bfcf</id>
<content type='text'>
This recipe was originally written and included in meta-overc as it
was used by the overc framework so we implemented it there to sort out
the kinks. Since this package is not specific to the OverC framework
and people may be interested in including it in their images without
having any interest in the OverC framework we are moving this recipe
here, alongside lxc and other container related recipes.

Signed-off-by: Mark Asselstine &lt;mark.asselstine@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
</feed>
