From: Mauro Queirós
Function "contains_lfs" was only looking at the master branch when searching
for LFS
content. LFS may be configured in specific branches only, so we need to use the
correct branch.
(Bitbake rev: 4fa67c2af830035a1ddedc14592ee25a15ebff22)
Signed-off-by: Mauro Queiros
Signed-
From: Matt Hoosier
Insert an explicit pass to fetch all blobs needed by Git LFS, during the
fetch() function. This avoids the default behavior of Git LFS to wait
until 'git checkout' to begin downloading the blobs pointed to by LFS records.
Network access is not allowed at that point in the recip
Sorry, third patch needs to be backported from master for git lfs to work
nicely on dunfell. Will send a v2.
-Mikko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52147): https://lists.yoctoproject.org/g/yocto/message/52147
Mute This Topic: https://
From: Mauro Queirós
Git-LFS objects were being fetched even when lfs=0 was not set.
This patch disables LFS smudging when lfs=0. That way, only the LFS pointers
are downloaded during checkout.
(Bitbake rev: 646d86df7de774255246a3d7051c308e43eb257d)
Signed-off-by: Mauro Queiros
Signed-off-by: R
From: Mauro Queirós
Function "contains_lfs" was only looking at the master branch when searching
for LFS
content. LFS may be configured in specific branches only, so we need to use the
correct branch.
(Bitbake rev: 4fa67c2af830035a1ddedc14592ee25a15ebff22)
Signed-off-by: Mauro Queiros
Signed-
From: Matt Hoosier
Insert an explicit pass to fetch all blobs needed by Git LFS, during the
fetch() function. This avoids the default behavior of Git LFS to wait
until 'git checkout' to begin downloading the blobs pointed to by LFS records.
Network access is not allowed at that point in the recip
Hi,
On Tue, Feb 02, 2021 at 03:38:34AM -0500, Robert P. J. Day wrote:
>
> while the "standard" way to disable a systemd service from
> auto-booting is SYSTEMD_AUTO_ENABLE, i just ran across a number of
> examples in an existing project that do this:
>
> SYSTEMD_SERVICE_${PN} = ""
>
> ouch.
Hi,
On Mon, Feb 22, 2021 at 12:12:21PM -0500, Claude Bing wrote:
> Hello all. My organization has been working with Yocto recently, and we
> have noticed that there are often weird errors encountered after
> updating revisions within a release branch (e.g., 3.1.3 -> 3.1.5). Is
> there an accepted
Hi,
I know it's not the best or recommended approach, but I find it
hard to avoid merging linux-libc-headers recipe with the actual
kernel recipe that a distro is using. At least a static copy
of some version of uapi headers from that kernel can be used
instead of the poky side linux-libc-headers.
On Tue, Feb 23, 2021 at 09:24:47AM -0500, Claude Bing wrote:
> I mentioned that we remove that directory, and it does indeed solve a
> lot of problems. Not sure that it was clear from the original message,
> but whenever we get a random error on the first build after the upgrade
> we run a "bitbak
Hi,
On Tue, Feb 23, 2021 at 06:56:02AM -0800, Karthik Poduval wrote:
> Hi Mikko,
>
> Do you have an example on how you do that ? Do you bbapend the
> linux-libc-headers recipe file ?
A kernel recipe will provide linux-libc-headers after a
"make headers_install" call...
So the SRC_URI of linux-l
Hi,
On Fri, Feb 26, 2021 at 10:08:47AM -0500, Jérôme Carretero wrote:
> On Fri, 26 Feb 2021 14:18:59 +
> "Mikko Murto" wrote:
>
> > The crux of the matter is that I need to find packages created by recipes
> > and to link the packages listed in image's manifest files to these
> > packages.
Hi,
On Tue, Apr 20, 2021 at 03:24:25AM -0700, anthony.march...@navocap.com wrote:
> Hello,
> I'm actually migrating a yocto project zeus version to dunfell LTS to build
> my imx6 Linux system on this LTS release.
>
> Almost all works fine except the following message I try to understand when I
From: Armin Kuster
Include example send-email
Signed-off-by: Armin Kuster
Signed-off-by: Joe MacDonald
(cherry picked from commit 48038b45dc114592991c069eb66d174820c0701d)
---
MAINTAINERS | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
ind
Hi,
On Tue, Jan 25, 2022 at 04:30:40PM +, Ross Burton wrote:
> On Mon, 24 Jan 2022 at 16:18, Jon Mason wrote:
> > CVE_CHECK_PN_WHITELIST -> CVE_CHECK_SKIPRECIPE
> > CVE_CHECK_WHITELIST -> CVE_CHECK_IGNORECVE
>
> This is the only one that sticks out to me. I think it needs another
> _, SKIP_
Hi,
On Wed, Mar 16, 2022 at 12:54:14AM -0700, Sourabh Hegde wrote:
> Hello All,
>
> I am using Yocto for one of my project. I know that Yocto needs a good amount
> of disk space for build activities. And also I am working as non-root user in
> Ubuntu 20.04. But I often run into space issues dur
Hi
I set INCOMPATIBLE_LICENSE_append = " GPLv3 GPLv3+ LGPLv3 LGPLv3+"
but then allow compiling several recipes with those licenses as long
as they don't end up on images and in the product. For example:
...
WHITELIST_GPL-3.0+ += "cairo"
PACKAGE_EXCLUDE += "cairo-src cairo-dbg cairo-perf-utils cai
Hi,
On Fri, Apr 08, 2022 at 10:18:22AM +0200, Mans Zigher wrote:
> Hi Ross,
>
> We don't have a ptest set in DISTRO_FEATURE so if that is the only way
> to pull in ptest I would say that is the reason for us at least on why
> there are so many bash dependencies.
> One recipe that I am looking int
Hi,
On Thu, Apr 28, 2022 at 01:04:22PM +0200, Ayoub Zaki via lists.yoctoproject.org
wrote:
> hello,
>
>
> I would like to have a custom DISTRO_VERSION based on "git describe" of my
> layer:
>
>
> 1) In my layer meta-mylayer/conf/layer.conf, I defined the following:
>
> # Set variable to get
On Thu, Apr 28, 2022 at 01:25:03PM +0200, Ayoub Zaki wrote:
> Hi,
>
> thanks for the quick reply I tried your suggestion but I get:
>
> ERROR: Unable to parse Var
> Traceback (most recent call last):
> File "Var ", line 1, in
> bb.data_smart.ExpansionError: Failure expanding variable
> DISTRO
Hi,
On Thu, Apr 28, 2022 at 01:38:35PM +0200, Ayoub Zaki wrote:
> I'm also suing dunfell branch, I did a small modification in
> my_distro_version.bbclass:
>
> def my_distro_version(d):
> > import subprocess
> > project_path = d.getVar('MY_LAYER_BASE', True)
> > cmd = "git describe --
Hi,
On Fri, May 27, 2022 at 08:07:57AM -0700, Daniel Squires wrote:
> Hi,
> We have an internal source tree, I'll call it libA for brevity here, which
> uses cmake and find_package to build against openssl as follows:
>
> find_package(OpenSSL REQUIRED)
>
> The recipe for this source runs fine b
Hi,
On Fri, May 27, 2022 at 04:37:40PM +0100, Daniel Squires wrote:
> We are indeed using
>
> inherit cmake
>
> The CMakeLists.txt adds a few bits to CMAKE_CXX_FLAGS but does not outright
> clobber it. I have noticed in other recipes some things like:
>
> EXTRA_OECONF = " --with-openssl=${STAGI
On Tue, May 31, 2022 at 07:52:05AM -0500, Joshua Watt wrote:
> On Tue, May 31, 2022 at 7:27 AM wrote:
> >
> > On Sat, 2022-05-28 at 07:40 +0300, Marius Vlad wrote:
> > > On Fri, May 27, 2022 at 04:25:00PM -0400, Scott Murray wrote:
> > > > On Fri, 27 May 2022, Tim Orling wrote:
> > > >
> > > > > O
have to
branch off layers over minor details like this.
Signed-off-by: Mikko Rapeli
---
.../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}| 0
.../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}| 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename
have to
branch off layers over minor details like this.
Signed-off-by: Mikko Rapeli
---
.../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}| 0
.../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}| 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename
Hi,
On Wed, Feb 01, 2023 at 08:19:42AM -0500, akuster808 wrote:
>
>
> On 1/30/23 6:01 AM, Mikko Rapeli wrote:
> > These bbappends apply to multiple kernel versions so no
> > need to make them version dependent. Fixes recipe parsing when
> > using meta-security master
Hi,
I don't mind but is the meta-security policy to accept new features in
stable branches?
FWIW, meta-security meta-tpm master branch does work on kirkstone too.
On Wed, Feb 01, 2023 at 08:26:12AM -0500, Armin Kuster wrote:
> Signed-off-by: Armin Kuster
> (cherry picked from commit 50eff83d428
Hi,
On Tue, Feb 14, 2023 at 09:08:29AM +0100, Maciej Borzęcki wrote:
> A cherry pick of patches adding support for EROFS and squashfs in
> dm-verity-img.
Depending on stable branch policies for meta-security, backporting new
features may not be acceptable.
As an alternative, master branch may j
There are multiple kernel versions now and the changes apply to
all of them, e.g. 5.15 and 6.1.
Signed-off-by: Mikko Rapeli
---
.../linux/{linux-yocto_5.%.bbappend => linux-yocto_%.bbappend}| 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename recipes-kernel/linux/{linux-yoct
Building documentation fails due to missing asciidoc, xsltproc etc
so it's better to just disable building them by default.
Signed-off-by: Mikko Rapeli
---
.../recipes-security/ima-evm-utils/ima-evm-utils_1.4.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-integrity/re
s from
poky to maintain list of crates in the .inc file. Tested on qemu that
parsec.service stars correctly and works with swtpm use cases.
Signed-off-by: Mikko Rapeli
---
.../parsec-service/parsec-service-crates.inc | 449 ++
.../parsec-service/parsec-service_1.1.0.inc | 223
Hi,
On Fri, Mar 24, 2023 at 05:24:31AM -0700, Anton Antonov wrote:
> Hi Mikko,
>
> Thank you for the patch. In general I don't mind switching from "cargo
> bitbake" to "bitbake -c update_crates" for Parsec recipes. But, in this case
> when you use a git repository instead of a Parsec crate the
s from
poky to maintain list of crates in the .inc file, but removed entries
for fuzz/Cargo.lock. Tested on qemu that parsec.service stars correctly
and works with swtpm use cases.
Signed-off-by: Mikko Rapeli
---
...ce_1.1.0.inc => parsec-service-crates.inc} | 239 +-
...e_
Hi,
On Fri, Mar 24, 2023 at 08:05:08AM -0700, Anton Antonov wrote:
> Hi Mikko,
>
> >
> > +SRC_URI +=
> > "git://github.com/parallaxsecond/parsec;protocol=https;branch=main \
>
> We noticed another small issue with your patch. Could you use gitsm instead
> of git, so required git submodules wil
s from
poky to maintain list of crates in the .inc file, but removed entries
for fuzz/Cargo.lock. Tested on qemu that parsec.service stars correctly
and works with swtpm use cases.
Signed-off-by: Mikko Rapeli
---
...ce_1.1.0.inc => parsec-service-crates.inc} | 239 +-
...e_
Hi,
On Thu, Apr 13, 2023 at 07:54:13PM +, Philippe Lafontaine via
lists.yoctoproject.org wrote:
> Greeting,
>
> I have a recipe that fetch a pre-built binary from a build machine using an
> access token. Every developer will have different access token, for obvious
> reason. Therefore, the
Hi,
On Fri, Apr 14, 2023 at 09:37:05AM +0200, Leon Woestenberg wrote:
> On Fri, Apr 14, 2023 at 9:24 AM Mikko Rapeli
> wrote:
>
> >
> > The environment variables and thus secrets are easily leaking into build
> > logs so I would not use them.
> >
> >
Hi,
On Fri, Apr 28, 2023 at 08:23:15AM -0400, Stefan Berger wrote:
> Add a temporary patch that resolves a file change notification issue
> with overlayfs where IMA did not become aware of the file changes
> since the 'lower' inode's i_version had not changed. The issue will be
> resolved in later
Hi,
On Tue, May 02, 2023 at 06:17:27PM -0400, Anthony Abboud wrote:
> HI Yocto Community,
>
> I am currently working on build a custom Boot2Qt image to learn about
> How-To's since it's my first time playing with Yocto. I am successfully
> able to build an image for my system; manually inserting
Hi,
On Sun, Dec 01, 2019 at 10:57:15PM +0100, Peter Bergin wrote:
> Hi,
>
> I'm currently working in a project using Yocto 2.6 (thud) release. It has
> default kernel v4.18 and also linux-libc-headers from kernel v4.18. In my
> project we will use kernel v4.1. I would like advice how to handle th
Hi,
On Mon, Dec 02, 2019 at 09:13:47AM +, Mike Looijmans wrote:
> On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote:
> > Hi,
> >
> > I'm currently working in a project using Yocto 2.6 (thud) release. It has
> > default kernel v4.18 and also linux-libc-headers from kernel v4.18
Hi,
On Mon, Dec 02, 2019 at 09:28:03AM +, Mike Looijmans wrote:
> One solution I can think of is to put the header into it's own
> recipe/repository and then refer to it like any other library would. Refer to
> that recipe from the module (or kernel) recipe that needs it. This way you
> hav
On Mon, Dec 02, 2019 at 04:01:41PM +0200, Adrian Bunk wrote:
> On Mon, Dec 02, 2019 at 09:33:33AM +0000, Mikko Rapeli wrote:
> >...
> > On Mon, Dec 02, 2019 at 09:28:03AM +, Mike Looijmans wrote:
> > > One solution I can think of is to put the header into it's own
Hi,
On Fri, Dec 06, 2019 at 02:07:47PM +0100, Mans Zigher wrote:
> Hi,
>
> I am trying to use the sstate cache by using a SSTATE_MIRROR. I have
> built everything from scratch once and pushed my sstate-cache
> directory to the server. I then wen't over to another machine and did
> a clean build b
Hi,
On Fri, Jan 24, 2020 at 11:02:02AM +0200, Anders Montonen wrote:
> Hi,
>
> What's the best way for handling name collisions when using the cve-checker
> tool? For example, there's a ton of Adobe Flex vulnerabilities that are
> reported against the Flex lexical analyzer generator tool. Whiteli
On Mon, Jan 27, 2020 at 10:16:16AM +0200, Anders Montonen wrote:
> On 24 Jan 2020, at 12:54, Ross Burton wrote:
> >
> > On 24/01/2020 09:02, Anders Montonen wrote:
> >> Hi,
> >> What's the best way for handling name collisions when using the
> >> cve-checker tool? For example, there's a ton of A
Hi,
I can't comment on svn fetcher but I use subversion via http
fetcher. This way the local download cache can have the exact same file
and builds can continue off line. One major gotcha is that all files
uploaded to svn must have unique and versioned file names. Updating the
same file to differe
bb.warn("svn fetch has ignored
> externals:\n%s" % output)
> 0154:bb.warn("To disable this warning add
> ';externals=nowarn' to the url.")
> Exception: UnboundLocalError: local variable 'svnfetchcmd' refer
On Mon, Feb 17, 2020 at 01:35:02PM +, Georgi Georgiev via
Lists.Yoctoproject.Org wrote:
> Hi Mikko,
> Your patch is upstreamed and...It is actually released. If you see the error
> output you will see your codeline. I decided to try with your old version
> but the result is the same. Can yo
(trimming lists to yocto only)
Hi,
I think you may be missing volatile-binds package and service from your image.
See poky/meta/recipes-core/volatile-binds/volatile-binds.bb
It may be missing /var/log but with systemd there should not be needs to write
to that location after image builds...
-Mi
On Tue, Feb 18, 2020 at 08:43:01PM +1100, JH wrote:
> Hi Mikko,
>
> On 2/18/20, mikko.rap...@bmw.de wrote:
> > I think you may be missing volatile-binds package and service from your
> > image.
> > See poky/meta/recipes-core/volatile-binds/volatile-binds.bb
>
> I got the source in my build syste
Hi,
On Wed, Feb 19, 2020 at 01:37:19AM -0800, Armando Hernandez wrote:
> Hello,
>
> I have a recipe that builds a library. The recipe specifies an additional
> package "${PN}-systemd" along with other systemd related variables and
> finally it instructs that the package should be built with
>
Hi,
(lets keep this on the list too)
On Wed, Feb 19, 2020 at 04:51:18PM +0100, Armando Hernandez wrote:
> Hi Mikko,
>
> Thanks for your reply. I checked your suggestion but does not work for me.
> I did included a .bbappend file in which I:
>
>- re-set EXTRA_OECMAKE to an empty string (i.e.
Hi,
Good pointers in this thread already. Here are mine:
* Share sstate mirror and download cache from release builds to
developer topic builds. NFS, web server or rsync before calling bitbake
will work.
* I've added buildhistory and prserv database as extra files to sstate mirror
and
Hi,
On Tue, Feb 18, 2020 at 01:20:25PM +0530, amaya jindal wrote:
>Thanks for your prompt reply. But is not there any way similar to add
>support for TLS1.3 instead of moving to new yocto releases
openssl is tricky to update and requires backporting fixes for many, many
recipes
to get bu
On Tue, Feb 18, 2020 at 07:25:15AM +, Georgi Georgiev via
Lists.Yoctoproject.Org wrote:
> OK,
> I read some code and I added the next line:
>
> --- a/bitbake/lib/bb/fetch2/svn.py
> +++ b/bitbake/lib/bb/fetch2/svn.py
> @@ -145,6 +145,7 @@ class Svn(FetchMethod):
>
> if not ("exte
k things until "bitbake -e" shows the right things for the recipes.
-Mikko
> On Wed, Feb 19, 2020 at 10:48 PM Mikko Rapeli wrote:
>
> > Hi,
> >
> > On Wed, Feb 19, 2020 at 01:37:19AM -0800, Armando Hernandez wrote:
> > > Hello,
> > >
> > &
Hi,
On Thu, Feb 20, 2020 at 12:55:43PM +0100, Martin Jansa wrote:
> On Thu, Feb 20, 2020 at 08:14:04AM +, mikko.rap...@bmw.de wrote:
> > On Wed, Feb 19, 2020 at 10:57:41PM +0100, Martin Jansa wrote:
> > > > DEPENDS_class-target += "systemd"
> > >
> > > You surely meant
> > > DEPENDS_append_cl
On Fri, Feb 28, 2020 at 11:25:59PM +, Richard Purdie wrote:
> On Fri, 2020-02-28 at 22:51 +, Sean McKay wrote:
> > This is probably a fairly short question (I hope):
> > I’m working on a branch based on zeus. I found a bug in the way that
> > one of our recipes was handling something during
On Tue, Mar 10, 2020 at 11:37:55AM +, Richard Purdie wrote:
> On Tue, 2020-03-10 at 11:33 +, mikko.rap...@bmw.de wrote:
> > On Fri, Feb 28, 2020 at 11:25:59PM +, Richard Purdie wrote:
> > > On Fri, 2020-02-28 at 22:51 +, Sean McKay wrote:
> > > > This is probably a fairly short ques
On Wed, Mar 18, 2020 at 05:52:37AM -0700, Oliver Westermann wrote:
> Hey,
>
> We're currently using a VM on Windows and it's a lot slower than the native
> linux build (which is expected).
> We're looking into getting a dedicated build server for our team (basically a
> self-build tower PC). Any
On Wed, Mar 18, 2020 at 04:09:39PM +0100, Mike Looijmans wrote:
> On 18-03-2020 15:49, Adrian Bunk via Lists.Yoctoproject.Org wrote:
> > On Wed, Mar 18, 2020 at 10:12:26AM -0400, Jean-Marie Lemetayer wrote:
> > > ...
> > > For example one of our build servers is using:
> > > - AMD Ryzen 9 3900X
> >
On Wed, Mar 18, 2020 at 10:56:50PM +, Ross Burton wrote:
> On 18/03/2020 14:09, Mike Looijmans wrote:
> > Harddisk speed has very little impact on your build time. It helps with
> > the "setscene" parts, but doesn't affect actual compile time at all. I
> > recall someone did a build from RAM di
On Thu, Mar 19, 2020 at 11:04:26AM +, Richard Purdie wrote:
> On Thu, 2020-03-19 at 08:05 +0000, Mikko Rapeli wrote:
> > Once this is done, IO still happens when anything calls sync() and
> > fsync() and worst offenders are package management tools. In yocto
> > builds, pa
Hi,
Generic approaches for reducing yocto target image size where buildhistory
is an important source of information:
* review and minimize distro features, enable only what you need
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#ref-features-distro
* review and mini
On Mon, Mar 30, 2020 at 03:00:05AM +, Ajam Ali wrote:
> Hi khemraj,
>
> Please suggest the way to reduce the image size. Your earlier suggestion is
> not that much helpful.
Actually suggestion to use buildhistory is the first critical step because
without
this you can't easily see where the
Hi,
On Wed, May 13, 2020 at 10:36:49AM +0200, Mans Zigher wrote:
> I am using a build environment based on the yocto project from one of
> the big HW suppliers in the mobile industries. They are continuously
> breaking the principles behind the yocto project and at one point they
> managed to brea
Hi,
On Wed, May 27, 2020 at 10:58:55AM +0200, Mans Zigher wrote:
> This is maybe more related to bitbake but I start by posting it here.
> I am for the first time trying to make use of a distributed sstate
> cache but I am getting some unexpected results and wanted to hear if
> my expectations are
Hi,
On Tue, Jun 30, 2020 at 09:34:39AM +, John Ernberg wrote:
> Hi,
>
> I have been trying to use INCOMPATIBLE_LICENSE to filter out undesirable
> licenses for us from our images. I started simple and picked the
> examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).
>
> Currently we'
Hi,
On Wed, Jul 08, 2020 at 07:52:30AM -0700, Pankaj Vinadrao Joshi wrote:
> I am trying to build yocto image for RPI4 but i am getting following error
>
> pankaj@exaleap-Inspiron-3584:~/raspberrypi4_image$ bitbake core-image-sato
> Parsing recipes: 100%
> |#
Hi,
On Tue, Jul 14, 2020 at 02:08:37PM +0200, Mans Zigher wrote:
> I figured it out the problem was that in meta-layer1 we had
> SRC_URI_append_machine1 += "file://0001-patch-one.patch" this
> apparently will always be added to the end of SRC_URI list and
> thereby the meta-layer2 patches will be
On Fri, Jul 31, 2020 at 08:45:17AM -0400, Rob Prowel wrote:
> What I really need is information about introspection or the ability to
> query an existing yocto distro to return data about features included and
> more to the point, to understand EXACTLY where recipes or classes are
> overridden or a
Hi,
On Mon, Aug 24, 2020 at 02:38:54PM +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
>
> I am having trouble with configuring my SDK for meta-clang...
>
> When I build my SDK, I setup the following:
>
> SDKMACHINE = "x86_64"
> SDKIMAGE_FEATURES_append = " staticdev-pkgs"
> TO
Hi,
On Mon, Aug 31, 2020 at 11:32:56AM +0200, Alexander Kanavin wrote:
> The best is to ask your BSP supplier to provide a new version of the BSP
> that is compatible with recent Yocto versions.
>
> Backporting userspace stuff is difficult or impossible.
For those who aren't afraid to digging de
Hi,
On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:
> Hi,
>
> I'm using poky release thud and would like to bump python3 to 3.8.x. I
> took recipe from most recent poky version but I'm hitting issue with
> e.g. meson build like:
> Log data follows:
> | DEBUG: Executing shell functi
On Wed, Nov 11, 2020 at 08:39:42AM +0100, Belisko Marek wrote:
> On Wed, Nov 11, 2020 at 8:04 AM wrote:
> >
> > Hi,
> >
> > On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:
> > > Hi,
> > >
> > > I'm using poky release thud and would like to bump python3 to 3.8.x. I
> > > took recipe
Hi,
Since master has 4.0.1 and CVE is impacting:
https://nvd.nist.gov/vuln/detail/CVE-2023-22745
"Up to (including)
4.0.0"
then I guess master branch and 4.0.1 is not impacted. Would be nice to
have this info in commit message though.
Cheers,
-Mikko
On Mon, May 08, 2023 at 03:23:34PM +0200,
Hi,
On Wed, May 10, 2023 at 08:23:18AM -0400, Stefan Berger wrote:
>
>
> On 5/10/23 07:44, Armin Kuster wrote:
> >
> >
> > On 5/9/23 2:56 PM, Jose Quaresma wrote:
> > > This reverts commit 9de807705b27b05bbf84e9f16502fe6cdaa8928f.
> > >
> > > The full patchset are overriding the do_configure
Hi,
On Wed, May 10, 2023 at 10:20:22AM -0400, Stefan Berger wrote:
>
>
> On 5/10/23 09:15, Mikko Rapeli wrote:
> > Hi,
> >
> > On Wed, May 10, 2023 at 08:23:18AM -0400, Stefan Berger wrote:
> > >
> > >
> > > On 5/10/23 07:44, Armin Kus
From: Mikko Rapeli
arm, arm64 and other machines can also have tpm and tpm2 devices
and the config snippets tpm.scc and tpm2.scc work there too.
Signed-off-by: Mikko Rapeli
---
meta-tpm/recipes-kernel/linux/linux-yocto_tpm.inc | 11 +--
1 file changed, 1 insertion(+), 10 deletions
From: Mikko Rapeli
It's not used by linux-yocto bbappends in any configuration.
Signed-off-by: Mikko Rapeli
---
meta-tpm/recipes-kernel/linux/linux-yocto/tpm_x86.cfg | 4
1 file changed, 4 deletions(-)
delete mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm_x86.cfg
diff
From: Mikko Rapeli
After latest changes to ${S}, parsec-service fails to apply systemd.patch:
ERROR: parsec-service-1.2.0-r0 do_patch: Applying patch 'systemd.patch' on
target directory
'/home/builder/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.2.0-r0/car
From: Mikko Rapeli
After latest changes to ${S}, parsec-service fails to apply systemd.patch:
ERROR: parsec-service-1.2.0-r0 do_patch: Applying patch 'systemd.patch' on
target directory
'/home/builder/build/tmp_trs-qemuarm64/work/cortexa57-trs-linux/parsec-service/1.2.0-r0/car
From: Mikko Rapeli
Currently build fails with:
| error: manifest path
`/home/builder/build/tmp_qemuarm64/work/cortexa57-linux/parsec-tool/0.6.0-r0/cargo_home/bitbake/parsec-tool-0.6.0//Cargo.toml`
does not exist
Normal source directory has Cargo.toml so only set ${B} to the
new path.
Signed
Hi,
On Mon, Jun 05, 2023 at 08:31:55AM +, Peter Marko via
lists.yoctoproject.org wrote:
> Hello maintainers,
>
> I'd be interested to know if meta-security repository for kirkstone is still
> maintained.
> Looking at commit history, there are only two commits since July 2022 (almost
> a ye
Hi,
On Wed, Jun 28, 2023 at 05:47:21PM +0100, Richard Purdie wrote:
> On Wed, 2023-06-28 at 08:56 -0400, Armin Kuster wrote:
> > Signed-off-by: Armin Kuster
> > ---
> > conf/layer.conf | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/conf/layer.conf b/conf/layer.conf
> > index
Hi,
On Thu, Jun 29, 2023 at 01:45:41PM +0300, Mikko Rapeli via
lists.yoctoproject.org wrote:
> Currently these belong logically to machine config but what about generic
> machine targets. Could an image config define how much memory is needed
> to run the image on qemu?
Done already i
Hi,
On Wed, Aug 16, 2023 at 03:54:38AM -0700, Nicolas Wirth via
lists.yoctoproject.org wrote:
> Hello everyone, I hope you're all doing well.
>
> I began learning how to use Yocto three months ago. I believe I now have a
> general understanding of how Yocto operates and how to integrate it into
Hi,
On Wed, Aug 16, 2023 at 04:55:53AM -0700, Nicolas Wirth via
lists.yoctoproject.org wrote:
> Hi Mikko, thank you for you're answer which was very insightful.
>
> >
> > If that is not available, check if you can change the branch of an existing
> > meta layer to provide what you need. Note th
Hi,
On Wed, Aug 16, 2023 at 05:32:23PM +0200, Alexander Kanavin wrote:
> On Wed, 16 Aug 2023 at 14:05, Mikko Rapeli wrote:
> > There isn't much documentation. It's more about just doing it and resolving
> > any issues
> > you find. For example BSP deliveries from
Hi,
On Thu, Aug 17, 2023 at 09:37:51AM +0200, Alexander Kanavin wrote:
> On Thu, 17 Aug 2023 at 06:41, Mikko Rapeli wrote:
> > One of the major problems with yocto major updates is that it becomes a big
> > bang,
> > everything must be updated at once. This can be spli
Hi,
One related improvement is to avoid IO to disk completely as long as RAM is
available. By default file systems like ext4 will start writing all buffers
in the background after few seconds which is wasted IO if memory is available
and
rm_work will anyway wipe the tmp to produce a target filesy
Hi,
On Wed, Sep 13, 2023 at 01:52:19PM +0200, Marta Rybczynska wrote:
> Hello,
> I've been working recently on collecting what works and what doesn't
> in YP security processes. The goal is to go forward and define an
> actionable strategy!
>
> Today, I'd like to share with you the summary of wha
Hi,
On Mon, Oct 02, 2023 at 10:41:37AM +, Danter, Richard via
lists.yoctoproject.org wrote:
> Hi all,
>
> We have a customer using hardknott & kirkstone who needs a newer cmake
> version. Looking at mickledore, it has a version of cmake that has the
> features they require.
>
> Would it be
Hi,
On Wed, Oct 04, 2023 at 01:50:18AM -0700, Dave Hitchman wrote:
> So I hav a custom recipe, gpsd is in place and functioning along with cgps, I
> can see the position nicely.
>
> I have also added per instructions I found the whole list of programs related
> to gps utils...
> SUMMARY_gps-uti
Hi,
On Fri, Oct 06, 2023 at 01:15:02PM +, Dave Hitchman wrote:
> Has anyone added this to a yocto build?
> I am sure it is possible but cant find any info, maybe someone has done it
Layerindex is the place to search for packages and recipes.
Sadly aptly isn't found from there:
https://layers
Hi,
On Mon, Oct 16, 2023 at 03:27:01PM +, Dave Hitchman wrote:
> So my current recipe for the project works, including building various C, C++
> files
> I wanted to now add a library of someone elses creation.
> On my machine this library builds using the tools installed so the code is ok
>
Hi,
On Tue, Oct 17, 2023 at 09:21:27AM +, Dave Hitchman wrote:
> Oh I dont know. This is getting to be a bit annoying.
> I had already included the inherit cmake line but now it seems maybe that you
> dont need to put any cmake commands in... not 100% sure, no one seems to
> explain this, I
Hi,
On Tue, Oct 17, 2023 at 10:09:42AM +, Dave Hitchman wrote:
> Thanks
>
> So, first, I thought - as I had seen examples that I had to put these flags
> etc. in the configuration function but it appears that was a wrong thing.
> Now my recipe looks like:
> SUMMARY = "mylib"
> DESCRIPTION =
1 - 100 of 119 matches
Mail list logo
