|
Yocto Project Status WW49`21
Current Dev Position: YP 3.5 M1
Next Deadline: 6th Dec. 2021 YP 3.5 M1 build
Next Team Meetings:
Bug Triage meeting Thursday Dec. 9th at 7:30am PDT
Current Dev Position: YP 3.5 M1
Next Deadline: 6th Dec. 2021 YP 3.5 M1 build
Next Team Meetings:
Bug Triage meeting Thursday Dec. 9th at 7:30am PDT
|
By
Stephen Jolley
·
#55503
·
|
|
Re: Setting BUILDNAME to a string broke in 3.1.12
I think Richard was suggesting that you add
REPRODUCIBLE_TIMESTAMP_ROOTFS to "" to your local.conf.
I did so and confirmed that /etc/version now has BUILDNAME for its
contents as expected.
Richard
I think Richard was suggesting that you add
REPRODUCIBLE_TIMESTAMP_ROOTFS to "" to your local.conf.
I did so and confirmed that /etc/version now has BUILDNAME for its
contents as expected.
Richard
|
By
Steve Sakoman
·
#55502
·
|
|
Re: [meta-rockchip][PATCH] README: Add intstructions to add patch template
Applied to meta-rockchip master branch. Thanks!
Applied to meta-rockchip master branch. Thanks!
|
By
Trevor Woerner
·
#55501
·
|
|
Re: Setting BUILDNAME to a string broke in 3.1.12
Hi
<richard.purdie@...> wrote:
confirmed by commenting out the echo above that that "solves the
issue", so it's in fact this code that is now wrongfully triggered.
/ Henrik
Hi
<richard.purdie@...> wrote:
confirmed by commenting out the echo above that that "solves the
issue", so it's in fact this code that is now wrongfully triggered.
/ Henrik
|
By
Henrik Riomar
·
#55500
·
|
|
ls command
Hi Guys i am new in YOCTO project. i have build images before and the images were included the "ls" and "clear" and all busybox commands. i do not know what happend now the image does not have anymore
Hi Guys i am new in YOCTO project. i have build images before and the images were included the "ls" and "clear" and all busybox commands. i do not know what happend now the image does not have anymore
|
By
msabood2014@...
·
#55499
·
|
|
Re: How to log inside a recipe
#yocto
This is not something I do a lot but from what I know, you should be able
to use `bbnote` expresions etc inside the functions like `do_install` or
`do_compile` only if you inherit the `logging`
This is not something I do a lot but from what I know, you should be able
to use `bbnote` expresions etc inside the functions like `do_install` or
`do_compile` only if you inherit the `logging`
|
By
tomzy
·
#55497
·
|
|
Re: How to log inside a recipe
#yocto
Thanks a lot. That works perfectly, but do you know how to use the log commands inside the recipe? It seems they work inside functions only (`do_install` e.g.)
Thanks a lot. That works perfectly, but do you know how to use the log commands inside the recipe? It seems they work inside functions only (`do_install` e.g.)
|
By
SAM
·
#55496
·
|
|
Is there any recipe for
#frr
Hi
There is an old discussion regarding this in this link:
https://lists.frrouting.org/pipermail/frog/2019-January/000445.html
But I can't find any updated one. Is there an updated recipe to build
Hi
There is an old discussion regarding this in this link:
https://lists.frrouting.org/pipermail/frog/2019-January/000445.html
But I can't find any updated one. Is there an updated recipe to build
|
By
SAM
·
#55495
·
|
|
Re: How to log inside a recipe
#yocto
Hi
To get a value of some variable added in recipe it is best to use bitbake
with `-e` flag which should print the whole environment, then one can just
use `grep` to search for given variable. Let
Hi
To get a value of some variable added in recipe it is best to use bitbake
with `-e` flag which should print the whole environment, then one can just
use `grep` to search for given variable. Let
|
By
tomzy
·
#55494
·
|
|
How to log inside a recipe
#yocto
Hi
There is a variable (or what ever it's called) inside a recipe. I want to know its value.
I've used `bbnote "something"` but this gives a parse error.
How to properly log?
Hi
There is a variable (or what ever it's called) inside a recipe. I want to know its value.
I've used `bbnote "something"` but this gives a parse error.
How to properly log?
|
By
SAM
·
#55493
·
|
|
Help with Inclusive Language in OpenEmbedded/Yocto Project
This email is a follow-up from the session held on Friday at the
OpenEmbedded Developer's Virtual Meeting (see
https://www.openembedded.org/wiki/OEDVM_Nov_2021)
The session was not recorded, but the
This email is a follow-up from the session held on Friday at the
OpenEmbedded Developer's Virtual Meeting (see
https://www.openembedded.org/wiki/OEDVM_Nov_2021)
The session was not recorded, but the
|
By
Jon Mason
·
#55492
·
|
|
Re: Setting BUILDNAME to a string broke in 3.1.12
rootfs-postcommands.bbclass says:
# Perform any additional adjustments needed to make rootf binary reproducible
rootfs_reproducible () {
if [ "${REPRODUCIBLE_TIMESTAMP_ROOTFS}" != "" ]; then
rootfs-postcommands.bbclass says:
# Perform any additional adjustments needed to make rootf binary reproducible
rootfs_reproducible () {
if [ "${REPRODUCIBLE_TIMESTAMP_ROOTFS}" != "" ]; then
|
By
Richard Purdie
·
#55491
·
|
|
Re: Setting BUILDNAME to a string broke in 3.1.12
After doing a bit of bisecting it appears that this commit is the culprit:
reproducible_build: Remove BUILD_REPRODUCIBLE_BINARIES
After doing a bit of bisecting it appears that this commit is the culprit:
reproducible_build: Remove BUILD_REPRODUCIBLE_BINARIES
|
By
Steve Sakoman
·
#55490
·
|
|
spdx: Extending SPDX SBOMs for SDKs
Hello,
I've been working on extending SPDX SBOMs for SDKs. In poky/meta/classes/create-spdx.bbclass I added:
do_populate_sdk[recrdeptask] +=
Hello,
I've been working on extending SPDX SBOMs for SDKs. In poky/meta/classes/create-spdx.bbclass I added:
do_populate_sdk[recrdeptask] +=
|
By
Andres Beltran
·
#55489
·
|
|
Enhancements/Bugs closed WW49!
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
michael.opdenacker@...
1
Grand Total
1
Thanks,
Stephen K. Jolley
Yocto Project Program
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
michael.opdenacker@...
1
Grand Total
1
Thanks,
Stephen K. Jolley
Yocto Project Program
|
By
Stephen Jolley
·
#55488
·
|
|
Current high bug count owners for Yocto Project 3.5
All,
Below is the list as of top 46 bug owners as of the end of WW49 of who have open medium or higher bugs and enhancements against YP 3.5. There are 99 possible work days left until the final
All,
Below is the list as of top 46 bug owners as of the end of WW49 of who have open medium or higher bugs and enhancements against YP 3.5. There are 99 possible work days left until the final
|
By
Stephen Jolley
·
#55487
·
|
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
|
By
Stephen Jolley
·
#55486
·
|
|
Re: Setting BUILDNAME to a string broke in 3.1.12
Hi,
We use build image-buildinfo class:
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-classes-image-buildinfo
Just add INHERIT += "image-buildinfo" to your local.conf to
Hi,
We use build image-buildinfo class:
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-classes-image-buildinfo
Just add INHERIT += "image-buildinfo" to your local.conf to
|
By
Daniel Gomez
·
#55485
·
|
|
Setting BUILDNAME to a string broke in 3.1.12
Hi,
We set the BUILDNAME (via local.conf) variable to the output of "git
describe --long --always" so this info ends up in /etc/version instead
of a date. (i.e to know the exact source version of the
Hi,
We set the BUILDNAME (via local.conf) variable to the output of "git
describe --long --always" so this info ends up in /etc/version instead
of a date. (i.e to know the exact source version of the
|
By
Henrik Riomar
·
#55484
·
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.1.rc1)
Hello everyone,
This is the full report for yocto-3.4.1.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
Hello everyone,
This is the full report for yocto-3.4.1.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
|
By
Teoh, Jay Shen
·
#55483
·
|