Hi Alex,
May I kindly ask you for your opinion?
Thank you,
Petr
From: openembedded-core@lists.openembedded.org
on behalf of Petr Kubizňák - 2N
Sent: Wednesday, February 1, 2023 5:04 PM
To: openembedded-core@lists.openembedded.org
Subject: Re:
V1 got merged, can you rebase ? :)
On 14/02/2023 09:21:56-0800, Saul Wold wrote:
> This change adds a new variable to track which recipe variables
> are added as SPDX Annotations.
>
> Usage: add SPDX_CUSTOM_ANNOTATION_VARS =
>
> The recipe spdx json will contain an annotation stanza that looks
Am Mittwoch, dem 15.02.2023 um 14:43 +0100 schrieb Alexander Kanavin:
> On Wed, 15 Feb 2023 at 12:22, Otavio Salvador
> wrote:
> > > Fair enough, I'm open to the idea. It would be interesting/useful to
> > > see if anyone else in the community is in favour of this or not. I'm
> > > sure you
The following changes since commit cb64ace13db85e143d99627c8803fbb13ba18617:
Fix missing leading whitespace with ':append' (2023-02-01 04:16:52 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
Am Mittwoch, dem 15.02.2023 um 10:53 -0300 schrieb Otavio Salvador:
> Em qua., 15 de fev. de 2023 às 10:44, Alexander Kanavin
> escreveu:
> > On Wed, 15 Feb 2023 at 12:22, Otavio Salvador
> > wrote:
> > > > Fair enough, I'm open to the idea. It would be interesting/useful to
> > > > see if
qemu doesn't always behave well and can hang too.
kill it with force if it was still alive. Move clean up
commands into cleanup() function.
Signed-off-by: Mikko Rapeli
---
scripts/runqemu | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
v3: moved from
When qemu machine hangs, the ssh commands done by tests
are not timing out. do_testimage() task has last logs like this:
DEBUG: time: 1673531086.3155053, endtime: 1673531686.315502
The test process is stuck for hours, or for ever if the
executing command or test case did not set a timeout
Hello Richard,
Em ter., 14 de fev. de 2023 às 10:56, Richard Purdie <
richard.pur...@linuxfoundation.org> escreveu:
> Fair enough, I'm open to the idea. It would be interesting/useful to
> see if anyone else in the community is in favour of this or not. I'm
> sure you appreciate why we need to
Mesa contains several optional tools that can be useful for application
and driver developers. Add a packageconfig option to build a mesa-tools
package containing relevant programs.
Signed-off-by: Dmitry Baryshkov
---
meta/recipes-graphics/mesa/mesa.inc | 19 ++-
1 file changed,
Em qua., 15 de fev. de 2023 às 10:01, Jose Quaresma
escreveu:
>
> The modules-load.d [1] - Configure kernel modules to load at boot
> should install their configuration files in /usr/lib/modules-load.d.
>
> The modprobe.d [2] - Configuration directory for modprobe
> should install their
Em qua., 15 de fev. de 2023 às 10:44, Alexander Kanavin
escreveu:
> On Wed, 15 Feb 2023 at 12:22, Otavio Salvador
> wrote:
> >> Fair enough, I'm open to the idea. It would be interesting/useful to
> >> see if anyone else in the community is in favour of this or not. I'm
> >> sure you appreciate
Em qua., 15 de fev. de 2023 às 11:11, Alexander Kanavin
escreveu:
>
> On Wed, 15 Feb 2023 at 14:53, Otavio Salvador
> wrote:
> > I think the Barebox inside OE-Core allows a bigger integration and
> > reuse of existing tooling for signing and other classes currently well
> > integrated with
On Wed, 15 Feb 2023 at 12:22, Otavio Salvador
wrote:
>> Fair enough, I'm open to the idea. It would be interesting/useful to
>> see if anyone else in the community is in favour of this or not. I'm
>> sure you appreciate why we need to ask the question and why we can't
>> just add everything! :)
The following changes since commit ab39d244cb844c9d183296945a095c17fdfef29e:
Fix missing leading whitespace with ':append' (2023-01-31 13:15:53 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/langdale-next
On Wed, 15 Feb 2023 at 14:25, Dmitry Baryshkov wrote:
> +# dependencies for tools. libconfig is optional, it is a part of meta-oe so
> it needs special treatment
> +TOOLS_DEPS_FREEDRENO_LIBCONFIG = "
> ${@bb.utils.contains('BBFILE_COLLECTIONS', 'openembedded-layer', 'libconfig',
> '', d)} "
On Wed, 15 Feb 2023 at 14:53, Otavio Salvador
wrote:
> I think the Barebox inside OE-Core allows a bigger integration and
> reuse of existing tooling for signing and other classes currently well
> integrated with U-Boot. For me, a critical point for decision is if
> Pengutronix will commit to
On Wed, 15 Feb 2023 at 10:39, Petr Kubizňák - 2N wrote:
> > The way I read gtk4 and graphene source code, what the recipe claims
> > is not true: you can disable introspection in graphene, and it would
> > still build and install graphene-gobject.pc which is what gtk4 is
> > looking for. If the
Signed-off-by: Jose Quaresma
---
meta/classes-recipe/kernel.bbclass | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/classes-recipe/kernel.bbclass
b/meta/classes-recipe/kernel.bbclass
index d327cd6888..5718600eee 100644
--- a/meta/classes-recipe/kernel.bbclass
+++
The modules-load.d [1] - Configure kernel modules to load at boot
should install their configuration files in /usr/lib/modules-load.d.
The modprobe.d [2] - Configuration directory for modprobe
should install their configuration files in /lib/modprobe.d
[1]
Hi Octavio,
Otavio Salvador escreveu no dia quarta,
15/02/2023 à(s) 13:25:
> Em qua., 15 de fev. de 2023 às 10:01, Jose Quaresma
> escreveu:
> >
> > The modules-load.d [1] - Configure kernel modules to load at boot
> > should install their configuration files in /usr/lib/modules-load.d.
> >
>
* I've noticed this, because patchreview.py reports Malformed
Upstream-Status in this one now, but the QA check in insane.bbclass
wasn't reporting it before
* the reason why insane.bbclass doesn't report it is because:
SRC_URI:append:ptest = "
o build a test
>
> -Upstream-Status: Inappropriate[oe specific]
> +Upstream-Status: Inappropriate [oe specific]
>
> Signed-off-by: Changqing Li
The patch is to fix ssh2.sh as a test. The test was disabled here:
https://git.yoctoproject.org/poky/commit/meta/recipes-support/libssh
Am Mittwoch, dem 15.02.2023 um 15:11 +0100 schrieb Alexander Kanavin:
> On Wed, 15 Feb 2023 at 14:53, Otavio Salvador
> wrote:
> > I think the Barebox inside OE-Core allows a bigger integration and
> > reuse of existing tooling for signing and other classes currently well
> > integrated with
There was a parallel conversation on the irc meanwhile; we've
concluded that Enrico will look into adding qemu based tests for
barebox into oe-selftest like we already have for EFI bootloaders, and
there will be a new patchset then.
Alex
On Wed, 15 Feb 2023 at 16:01, Enrico Jörns wrote:
>
> Am
* the idea was to reuse the same function as I've noticed that the
QA check which was added to insane.bbclass in:
https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a
is in some cases more strcit than scripts/contrib/patchreview.py
To be
* this block was using just 3
Signed-off-by: Martin Jansa
---
meta/classes-global/insane.bbclass | 50 +++---
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/meta/classes-global/insane.bbclass
b/meta/classes-global/insane.bbclass
index
* to be used by standalone script scripts/contrib/patchreview.py
as well
Signed-off-by: Martin Jansa
---
meta/classes-global/insane.bbclass | 19 +++
meta/lib/oe/qa.py | 17 +
2 files changed, 20 insertions(+), 16 deletions(-)
diff --git
Please no. Much less readable without a space.
Alex
On Wed 15. Feb 2023 at 20.27, Khem Raj wrote:
> On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa
> wrote:
> >
> > * I've noticed this, because patchreview.py reports Malformed
> > Upstream-Status in this one now, but the QA check in
Upgrade git to latest 2.37.x release to address
security issues CVE-2022-23521 and CVE-2022-41903.
Signed-off-by: Sakib Sajal
---
meta/recipes-devtools/git/{git_2.37.4.bb => git_2.37.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/git/{git_2.37.4.bb =>
On Wed, Feb 15, 2023 at 11:26 AM Khem Raj wrote:
>
> On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa wrote:
> >
> > * I've noticed this, because patchreview.py reports Malformed
> > Upstream-Status in this one now, but the QA check in insane.bbclass
> > wasn't reporting it before
> >
> > * the
On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa wrote:
>
> * I've noticed this, because patchreview.py reports Malformed
> Upstream-Status in this one now, but the QA check in insane.bbclass
> wasn't reporting it before
>
> * the reason why insane.bbclass doesn't report it is because:
>
From: Bruce Ashfield
Backporting a patching from the 2.13.x stable branch of lttng
to fix the build against kernel 6.2+.
Signed-off-by: Bruce Ashfield
---
...ccessor-helpers-into-accessors.h-v6..patch | 45 +++
.../lttng/lttng-modules_2.13.8.bb | 1 +
2 files
On Wed, Feb 15, 2023 at 12:46 PM Martin Jansa wrote:
>
> patchreview.py will care about the space (like insane.bbclass does) if
> https://lists.openembedded.org/g/openembedded-core/message/177207 is merged
>
I see. thanks. I think this should be something every developer should
then be able to
Moves the downloaded items from SRC_URI into separate packages in the
recipe document. This is much better than the previous implementation
because:
1) It can report multiple download locations in SRC_URI, instead of
just the first one reported.
2) It prevents the assumption that the source
Hello,
The series caused different build failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/6713/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/6727/steps/11/logs/stdio
|
patchreview.py will care about the space (like insane.bbclass does) if
https://lists.openembedded.org/g/openembedded-core/message/177207 is merged
On Wed, Feb 15, 2023 at 9:35 PM Khem Raj wrote:
> On Wed, Feb 15, 2023 at 11:26 AM Khem Raj wrote:
> >
> > On Wed, Feb 15, 2023 at 9:18 AM Martin
2.sh need sshd, for cross compile, we need it on target, so
> > don't use SSHD on host to decide weither to build a test
> >
> > -Upstream-Status: Inappropriate[oe specific]
> > +Upstream-Status: Inappropriate [oe specific]
> >
> > Signed-off-by: Changqing Li
Martin Jansa spotted patchreview.py reports Malformed Upstream-Status in a
patch in this recipe. The patch is not being applied since there is no ptest
override.
The test in question was also disabled due to an issue with new versions of
openssh.
Add a workaround for the broken test, enable it,
Joseph,
Currently create-spdx will only report on the recipe itself and the
packages it produces. It's been a long standing TODO to make reporting
of sub-components like NPM packages and rust crates better, but we
haven't gotten there yet, partially because I'm not very familiar with
these
Upgrade git to latest 2.37.x release to address
security issues CVE-2022-23521 and CVE-2022-41903.
Signed-off-by: Sakib Sajal
---
meta/recipes-devtools/git/{git_2.35.5.bb => git_2.35.7.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/git/{git_2.35.5.bb =>
Thanks for confirming. I wouldn't expect OE to be able to have any knowledge
of "sneaky" downloads of additional packages.
I have an idea to enhance create-spdx.bbclass so sneaky recipes can fess-up and
tell create-spdx about any additional packages they downloaded. If you could
implement
On Tue, 2023-02-14 at 17:53 +0100, Alexis Lothoré via
lists.openembedded.org wrote:
> From: Alexis Lothoré
>
> This v2 does not contain any change in patches content, it only sets the From:
> field correctly. Sorry for the noise.
>
> This patch serie is a proposal linked to discussion initiated
This adds a check to ensure we that if a variable is
empty it gets an empty string, this also adds quotes
to indicate the variable contents.
"comment": "CUSTOM_SPECIAL=''"
or
"comment": "CUSTOM_SPECIAL= 'variable contents'"
Signed-off-by: Saul Wold
---
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*63acb96f92473ceb5e21d873d7c0aee266b3d6d3* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.39.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-git-upgrade-2.39.1-2.39.2.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *e2fsprogs* to *1.47.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-e2fsprogs-upgrade-1.46.5-1.47.0.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *openssl* to *3.0.8* has
Succeeded.
Next steps:
- apply the patch: git am 0001-openssl-upgrade-3.0.7-3.0.8.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.20.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-go-upgrade-1.20-1.20.1.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.68.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.66.0-6.68.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hatchling* to
*1.13.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.12.2-1.13.0.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.20.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dpkg* to *1.21.20* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dpkg-upgrade-1.21.19-1.21.20.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to
*67.3.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-upgrade-67.2.0-67.3.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ruby* to *3.2.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ruby-upgrade-3.2.0-3.2.1.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-typing-extensions* to
*4.5.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-typing-extensions-upgrade-4.4.0-4.5.0.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-numpy* to *1.24.2*
has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe python3-numpy failed.
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vala* to *0.56.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-vala-upgrade-0.56.3-0.56.4.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *man-pages* to *6.03* has
Succeeded.
Next steps:
- apply the patch: git am 0001-man-pages-upgrade-6.02-6.03.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to
*590d81bb5fa219353104980108e9f1aa2b1d1b6b* has Succeeded.
Next steps:
- apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch
- check the changes
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography-vectors*
to *39.0.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-cryptography-vectors-upgrade-39.0.0-39.0.1.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mmc-utils* to
*d4c2910981ff99b983734426dfa99632fb81ac6b* has Succeeded.
Next steps:
- apply the patch: git am 0001-mmc-utils-upgrade-to-latest-revision.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *log4cplus* to *2.1.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-log4cplus-upgrade-2.0.8-2.1.0.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to
*3df7dba1b1f428f24cd9a242af78540a518f4b67* has Failed(other errors).
Detailed error information:
'MACHINE=qemux86 bitbake vulkan-samples' failed
WARNING: Host
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libva* to *2.17.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libva-upgrade-2.16.0-2.17.0.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *acpica* to *20221022* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade acpica -V 20221022
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust* to *1.67.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-rust-upgrade-1.67.0-1.67.1.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sudo* to *1.9.13* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe sudo failed.
NOTE: Starting bitbake server...
WARNING: Host
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libwpe* to *1.14.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libwpe-upgrade-1.14.0-1.14.1.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *freetype* to *2.13.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade freetype -V 2.13.0
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *zstd* to *1.5.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-zstd-upgrade-1.5.2-1.5.4.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnutls* to *3.8.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gnutls failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *linux-firmware* to *20230210*
has Succeeded.
Next steps:
- apply the patch: git am
0001-linux-firmware-upgrade-20230117-20230210.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dos2unix* to *7.4.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dos2unix-upgrade-7.4.3-7.4.4.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libva-initial* to *2.17.0*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: finish -f libva-initial
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wireless-regdb* to
*2023.02.13* has Succeeded.
Next steps:
- apply the patch: git am
0001-wireless-regdb-upgrade-2022.08.12-2023.02.13.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dtc* to *1.7.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-dtc-upgrade-1.6.1-1.7.0.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *liburcu* to *0.14.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-liburcu-upgrade-0.13.2-0.14.0.patch
- check the changes to upstream patches and summarize
77 matches
Mail list logo
