|
[meta-cgl][PATCH] recipes: update SRC_URI branch and protocols
Update SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
Update SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
|
By
Yi Zhao
·
#55245
·
|
|
[meta-selinux][PATCH 2/2] bind: remove volatile file
This file is not needed anymore as bind daemon will create them by
itself.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
recipes-connectivity/bind/bind_selinux.inc | 7 -------
This file is not needed anymore as bind daemon will create them by
itself.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
recipes-connectivity/bind/bind_selinux.inc | 7 -------
|
By
Yi Zhao
·
#55244
·
|
|
[meta-selinux][PATCH 1/2] recipes: update SRC_URI branch and protocols
Update SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
Update SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
|
By
Yi Zhao
·
#55243
·
|
|
Re: Bitbake build fails because of a python function
Just wondering, what it /srv/yocto? Can you build in your $HOME?
Otherwise, you can run bitbake under 'strace -ff -o strace-log ...' and try to check exactly what syscall causes cpio to fail.
Alex
Just wondering, what it /srv/yocto? Can you build in your $HOME?
Otherwise, you can run bitbake under 'strace -ff -o strace-log ...' and try to check exactly what syscall causes cpio to fail.
Alex
|
By
Alexander Kanavin
·
#55242
·
|
|
Re: Bitbake build fails because of a python function
Dear Alexander,
Thanks a lot for responding. I've attached the log file.
The only valuable info I could find is the following piece at the end of the log file. Could that be a potential cause for
Dear Alexander,
Thanks a lot for responding. I've attached the log file.
The only valuable info I could find is the following piece at the end of the log file. Could that be a potential cause for
|
By
Maksym Iliev
·
#55241
·
|
|
Minutes: Yocto Project Weekly Triage Meeting 11/4/2021
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage
Attendees: Alexandre, Armin, Bruce, Jon, Joshua, Kiran, Michael, Randy, Richard, Stephen, Steve, Tim, Trevor
ARs:
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage
Attendees: Alexandre, Armin, Bruce, Jon, Joshua, Kiran, Michael, Randy, Richard, Stephen, Steve, Tim, Trevor
ARs:
|
By
Trevor Gamblin
·
#55240
·
|
|
[meta-security][PATCH] tpm2-tss: fix fapi package config
When enabling fapi, the build breaks with:
| configure: error: Package requirements (libcurl) were not met:
| No package 'libcurl' found
This adds the missing dependency and bundles the additional
When enabling fapi, the build breaks with:
| configure: error: Package requirements (libcurl) were not met:
| No package 'libcurl' found
This adds the missing dependency and bundles the additional
|
By
Stefan Mueller-Klieser
·
#55239
·
|
|
User configuration & host contamination
Hi all,
I'm having some difficulty with setting up users and the respective application user assignments. I have a generic recipe which inherits useradd and sets a user, this works great for my
Hi all,
I'm having some difficulty with setting up users and the respective application user assignments. I have a generic recipe which inherits useradd and sets a user, this works great for my
|
By
Jeffrey Simons
·
#55238
·
|
|
Re: Dunfell - ERROR: ca-certificates-20211016-r0 do_fetch: Fetcher failure
Most likely expired Let's Encrypt certificate (which salsa.debian.org where ca-certificates are hoster is using) on your builder (host OS), see e.g. for
Most likely expired Let's Encrypt certificate (which salsa.debian.org where ca-certificates are hoster is using) on your builder (host OS), see e.g. for
|
By
Martin Jansa
·
#55237
·
|
|
Dunfell - ERROR: ca-certificates-20211016-r0 do_fetch: Fetcher failure
Hi,
After syncup of Yocto dunfell, I get the following error:
dwatkins@carmd-ed-n11377-docker-dwatkins_apollo17:64bitbuild $ bitbake ca-certificates -c fetch
Loading cache: 100%
Hi,
After syncup of Yocto dunfell, I get the following error:
dwatkins@carmd-ed-n11377-docker-dwatkins_apollo17:64bitbuild $ bitbake ca-certificates -c fetch
Loading cache: 100%
|
By
Darcy Watkins
·
#55236
·
|
|
Re: Bitbake build fails because of a python function
It's hard to say if we can't replicate the issue. Check /srv/yocto/build/tmp/work/corei7-64-poky-linux/perl/5.30.1-r0/temp/log.do_package_write_rpm, it might have useful debugging info.
Alex
It's hard to say if we can't replicate the issue. Check /srv/yocto/build/tmp/work/corei7-64-poky-linux/perl/5.30.1-r0/temp/log.do_package_write_rpm, it might have useful debugging info.
Alex
|
By
Alexander Kanavin
·
#55235
·
|
|
Bitbake build fails because of a python function
Hello guys. I am brand new to yocto and bitbake and I am looking for any help/advice/hints I can get. I have inherited someone else's code for building yocto project images, but the bitbake fails with
Hello guys. I am brand new to yocto and bitbake and I am looking for any help/advice/hints I can get. I have inherited someone else's code for building yocto project images, but the bitbake fails with
|
By
Maksym Iliev
·
#55234
·
|
|
Re: how to handle third party licenses
Whatever you are setting for LICENSE Variable inside recipe there should be a file with same name stored inside One of LICENSE_PATH directories.
Whatever you are setting for LICENSE Variable inside recipe there should be a file with same name stored inside One of LICENSE_PATH directories.
|
By
Khem Raj
·
#55233
·
|
|
Re: how to handle third party licenses
Hi Steven,
Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> escreveu no dia quarta, 3/11/2021 à(s) 17:57:
You can add the generic license.txt provided by the
Hi Steven,
Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> escreveu no dia quarta, 3/11/2021 à(s) 17:57:
You can add the generic license.txt provided by the
|
By
Jose Quaresma
·
#55232
·
|
|
how to handle third party licenses
Looking for the proper Yocto way to handle third party software ported to Yocto and built into kernel…
I’m not having issues when I recognize the license as a generic license. But the license
Looking for the proper Yocto way to handle third party software ported to Yocto and built into kernel…
I’m not having issues when I recognize the license as a generic license. But the license
|
By
Monsees, Steven C (US)
·
#55231
·
|
|
[meta-security][PATCH] recipes: Update SRC_URI branch and protocols
This patch updates SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls as generated by the conversion script
in OE-Core.
Signed-off-by:
This patch updates SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls as generated by the conversion script
in OE-Core.
Signed-off-by:
|
By
Armin Kuster
·
#55230
·
|
|
Re: preempt-rt
Thanks…
By
Monsees, Steven C (US)
·
#55229
·
|
|
Re: preempt-rt
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Oops, FILES_EXTRAPATHS_prepend isn't necessary in this case. I usually download and store the patch in my layer once I find the right
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Oops, FILES_EXTRAPATHS_prepend isn't necessary in this case. I usually download and store the patch in my layer once I find the right
|
By
codusnocturnus
·
#55228
·
|
|
Re: preempt-rt
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
There are a few details to sort out (like finding a patch compatible with the kernel recipe you want to use, or a compromise of the two),
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
There are a few details to sort out (like finding a patch compatible with the kernel recipe you want to use, or a compromise of the two),
|
By
codusnocturnus
·
#55227
·
|
|
Re: preempt-rt
Cannot…
Generic preempt-rt patch bbappend should be enough…
Cannot…
Generic preempt-rt patch bbappend should be enough…
|
By
Monsees, Steven C (US)
·
#55226
·
|