This does not seem correct. These two packages have FILES specified, and
ALLOW_EMPTY:${PN} is set to "1". I suspect the actually problem lies in
somewhere else.
Regards,
Qi
On 2/10/23 15:34, leimaohui wrote:
Problem: conflicting requests
- nothing provides nghttp2-client >= 1.51.0 needed b
If neither client nor server packages contain any files, then what is
installed? Is there some other useful package than nghttp2 package
pulls in, or does it itself contain something useful?
Alex
On Fri, 10 Feb 2023 at 08:35, leimaohui wrote:
>
> Problem: conflicting requests
> - nothing provi
Problem: conflicting requests
- nothing provides nghttp2-client >= 1.51.0 needed by
nghttp2-1.51.0-r0.core2_64
- nothing provides nghttp2-server >= 1.51.0 needed by
nghttp2-1.51.0-r0.core2_64
Signed-off-by: Lei Maohui
---
meta/recipes-support/nghttp2/nghttp2_1.51.0.bb | 2 ++
1 file change
Signed-off-by: Alexander Kanavin
---
...ove-fix-ALWAYS_INLINE-compiler-error.patch | 36 ---
.../{mesa-gl_22.3.3.bb => mesa-gl_22.3.5.bb} | 0
meta/recipes-graphics/mesa/mesa.inc | 3 +-
.../mesa/{mesa_22.3.3.bb => mesa_22.3.5.bb} | 0
4 files changed, 1 insertion(
Drop xingmux license snippet from plugins-ugly as it moved to plugins-good;
the license was LGPL in any case:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/d132592423be64ec18a223b67810ac89f391277e/subprojects/gst-plugins-good/tests/check/elements/xingmux.c
videoconvert/videoscale plgin
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/vim/vim.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 9bc6881fce..fcb5cf6334 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/r
The recipe was building native go against build host headers and libraries,
and then installing it as a nativesdk item, which is entirely incorrect. This
has
been working by coincidence (go generally uses C and C libraries lightly)
but with go 1.20 this turned into hard breakage.
Also nativesdk s
From: Adrian Freihofer
Without this patch:
$ bitbake-layers create-layers-setup /home/adrian/temp/poky-clone
NOTE: Starting bitbake server...
Traceback (most recent call last):
File "/home/adrian/projects/poky/bitbake/lib/bb/process.py", line 169, in run
pipe = Popen(cmd, **options)
File
Signed-off-by: Alexander Kanavin
---
meta/lib/bblayers/makesetup.py | 10 ++
1 file changed, 10 insertions(+)
diff --git a/meta/lib/bblayers/makesetup.py b/meta/lib/bblayers/makesetup.py
index 834e9338bc..5fb6f1469e 100644
--- a/meta/lib/bblayers/makesetup.py
+++ b/meta/lib/bblayers/make
Signed-off-by: Alexander Kanavin
---
scripts/oe-setup-layers | 6 ++
1 file changed, 6 insertions(+)
diff --git a/scripts/oe-setup-layers b/scripts/oe-setup-layers
index d0bc9f1667..461560de9f 100755
--- a/scripts/oe-setup-layers
+++ b/scripts/oe-setup-layers
@@ -46,6 +46,9 @@ def _is_layer_
From: Chee Yang Lee
upgrade include fix for CVE-2022-23521 and CVE-2022-41903
Signed-off-by: Chee Yang Lee
---
meta/recipes-devtools/git/{git_2.35.5.bb => git_2.35.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/git/{git_2.35.5.bb => git_2.35.6.bb} (98
From: Chee Yang Lee
upgrade include fix for CVE-2022-23521 and CVE-2022-41903
Signed-off-by: Chee Yang Lee
---
meta/recipes-devtools/git/{git_2.37.4.bb => git_2.37.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/git/{git_2.37.4.bb => git_2.37.5.bb} (98
From: Xiangyu Chen
Backport patch to fix dhcpcd start failed on qemuppc64.
Signed-off-by: Xiangyu Chen
---
.../dhcpcd/dhcpcd_9.4.1.bb| 1 +
...x-SECCOMP_AUDIT_ARCH-missing-ppc64le.patch | 34 +++
2 files changed, 35 insertions(+)
create mode 100644
meta/r
On Thu, Feb 9, 2023 at 10:15 AM Khem Raj wrote:
> Is there some reading material for quick highlights of dnf5 and its future
> ?
>
The Fedora change wiki has some important caveats:
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
The above references this:
https://dnf5.readthedocs.io/
Hello Lee Chee,
On Thu, 9 Feb 2023 21:02:29 +0800
"Lee Chee Yang" wrote:
> From: Chee Yang Lee
>
> This is a security release to address CVE-2023-22742: when compiled
> using the optional, included libssh2 backend, libgit2 fails to verify
> SSH keys by default.
>
> When using an SSH remote w
From: Mateusz Marciniec
Symbolic links to the files are included during the output hash
calculation but symlinks to the directories are missed.
So if the new symlink to a directory was the only change made,
then the output hash won't change,
and the Hash Equivalence server may change unihash.
In
One additional comment on the content of your subject line:
You should start with the base recipe name so reviewers know what
recipe you are changing, so something like "openssl: upgrade 3.0.7 ->
3.0.8" would be appropriate for this patch.
Thanks!
Steve
On Thu, Feb 9, 2023 at 4:37 AM mv wrot
If the user invokes the devshell on the linux-yocto kernel, add
python3-dtschema-native to their native sysroot so they can do
things like:
devshell> make dtbs_check
Signed-off-by: Trevor Woerner
---
meta/recipes-kernel/linux/linux-yocto.inc | 1 +
1 file changed, 1 insertion(+)
diff -
dt-schema has a dependency on pylibfdt.
Signed-off-by: Trevor Woerner
---
.../python/python3-dtschema_2023.1.bb | 2 +-
.../python/python3-pylibfdt_1.6.1.bb | 14 ++
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-devtools
Is there some reading material for quick highlights of dnf5 and its future ?
On Thu, Feb 9, 2023 at 4:05 AM Ross Burton wrote:
>
> Hi,
>
> At FOSDEM there were was a session about DNF 5 and someone (sorry if you’re
> reading this, I can’t remember your name) came to the stand to ask if we’ve
>
This allows to specify partition with fstype=none in the wks file
to have partition created but without following mkfs. The none fstype
is in the list already but the usage is not documented.
Example;
part /data --ondisk mmcblk0 --fstype=none --align 4096 --fixed-size 512
will create a partition
thanks for finding and fixing it. It has happened with every upgrade
that this file goes out of sync due to copyright headers change.
its perhaps worth trying to use a symlink instead try this patch and
see if it works in your settings
https://uclibc.org/~kraj/0001-wordsize.h-Unify-the-header-bet
openldap is added as a dependency so the build will not fail,
as otherwise ldap headers are not found during configure phase
Note: due to upstream bug (now fixed) building LDAP/LDAPS support
with minimal configurations can sometimes not work, see details at:
https://github.com/curl/curl/pull/10445
From: Kai Kang
According to the ANNOUNCE of xorg-server 21.1.7[1]:
This release contains the fix for CVE-2023-0494 in today's security
advisory: https://lists.x.org/archives/xorg-announce/2023-February/003320.html
It also fixes a second possible OOB access during EnqueueEvent and a
crasher cause
Per feedback from users, remove the top level image SPDX file and the
JSON index file from DEPLOYDIR. Having these files here is confusing to
end users because these files are not very useful by themselves, and
having them in DEPLOYDIR makes it unclear which they should be using.
Signed-off-by: Jo
Append to cleandirs in do_populate_sdk so that other classes
(specifically, create-spdx-2.2) can add additional directories
Signed-off-by: Joshua Watt
---
meta/classes-recipe/populate_sdk_base.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes-recipe/populat
Per feedback from users, remove the top level image SPDX file and the
JSON index file from DEPLOYDIR. Having these files here is confusing to
end users because these files are not very useful by themselves, and
having them in DEPLOYDIR makes it unclear which they should be using.
Joshua Watt (2):
Hi Luca,
Thank-you for your feedback. Yes, the patch was a mistake. I have rectified it
and submitted version-2 for the same.
However, i am looking into how to change the name which unfortunately i am not
able to do currently even though my git credentials are in sync.
By the next patch submis
From: Siddharth Doshi
OpenSSL 3.0.8 fixes 1 HIGH level security vulnerability and 7 MODERATE level
security vulnerability [1].
Upgrade the recipe to point to 3.0.8.
CVE-2022-3996 is reported fixed in 3.0.8, so drop the patch for that as
well.
[1] https://www.openssl.org/news/vulnerabilities.h
From: Siddharth Doshi
OpenSSL 3.0.8 fixes 1 HIGH level security vulnerability and 7 MODERATE level
security vulnerability [1].
Upgrade the recipe to point to 3.0.8.
CVE-2022-3996 is reported fixed in 3.0.8, so drop the patch for that as
well.
[1] https://www.openssl.org/news/vulnerabilities.h
From: Siddharth Doshi
OpenSSL 3.0.8 fixes 1 HIGH level security vulnerability and 7 MODERATE level
security vulnerability [1].
Upgrade the recipe to point to 3.0.8.
CVE-2022-3996 is reported fixed in 3.0.8, so drop the patch for that as
well.
[1] https://www.openssl.org/news/vulnerabilities.h
From: Chee Yang Lee
This is a security release to address CVE-2023-22742: when compiled
using the optional, included libssh2 backend, libgit2 fails to verify
SSH keys by default.
When using an SSH remote with the optional, included libssh2 backend,
libgit2 does not perform certificate checking b
On Wed, 8 Feb 2023 at 12:49, Pawan Badganchi wrote:
> +CVE: CVE-2023-22809
> +Upstream-Staus: Backport
> [http://archive.ubuntu.com/ubuntu/pool/main/s/sudo/sudo_1.8.31-1ubuntu1.4.debian.tar.xz]
This is not a backport location. Please check if the fix is available
in the upstream repository, and
From: Chee Yang Lee
Signed-off-by: Chee Yang Lee
---
.../tar/files/CVE-2022-48303.patch| 36 +++
meta/recipes-extended/tar/tar_1.34.bb | 4 ++-
2 files changed, 39 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-extended/tar/files/CVE-2022-4830
Hi,
On Thu, Feb 09, 2023 at 12:42:09PM +0100, Alexander Kanavin wrote:
> On Thu, 9 Feb 2023 at 12:12, Mikko Rapeli wrote:
> > select() returns with any data, even single character. Fancy readers
> > will read larger chunks but will read more data than is available and thus
> > block for ever. Pla
Hi,
At FOSDEM there were was a session about DNF 5 and someone (sorry if you’re
reading this, I can’t remember your name) came to the stand to ask if we’ve
looked at it. I was aware of a DNF replacement but wasn’t aware that it had
actually started making releases.
I’ve just pushed a branch t
On Thu, 9 Feb 2023 at 12:12, Mikko Rapeli wrote:
> select() returns with any data, even single character. Fancy readers
> will read larger chunks but will read more data than is available and thus
> block for ever. Plain read() will read the data which is available from
> select() and thus really
Hi Siddharth,
thank you for our patch!
There are a couple issues you should fix though.
First, the subject line of your mail is non-standard as it has square
brackets around other square brackets: "[[master][PATCH]]". When
applying the patch with 'git am' this results in a commit message
startin
Have submitted the patch to master branch. Do you want me to re-submit to LTS
branches ?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176946):
https://lists.openembedded.org/g/openembedded-core/message/176946
Mute This Topic: https://lists.opene
From: Siddharth Doshi
OpenSSL 3.0.8 fixes 1 HIGH level security vulnerability and 7 MODERATE level
security vulnerability [1].
Upgrade the recipe to point to 3.0.8.
CVE-2022-3996 is reported fixed in 3.0.8, so drop the patch for that as
well.
[1] https://www.openssl.org/news/vulnerabilities.h
Hi,
On Thu, Feb 09, 2023 at 11:53:00AM +0100, Alexander Kanavin wrote:
> On Thu, 9 Feb 2023 at 10:36, Mikko Rapeli wrote:
> > I think sleep() is ok in this case to reduce busy looping over serial
> > console and read() more data than what select() initially saw. Reading
> > single character at a
On Thu, 2023-02-09 at 11:53 +0100, Alexander Kanavin wrote:
> On Thu, 9 Feb 2023 at 10:36, Mikko Rapeli wrote:
> > I think sleep() is ok in this case to reduce busy looping over serial
> > console and read() more data than what select() initially saw. Reading
> > single character at a time is a bi
On Thu, 9 Feb 2023 at 10:36, Mikko Rapeli wrote:
> I think sleep() is ok in this case to reduce busy looping over serial
> console and read() more data than what select() initially saw. Reading
> single character at a time is a bit silly and just wastes CPU time when
> we don't need ms level accur
On Thu, 2023-02-09 at 12:35 +0200, Mikko Rapeli wrote:
> Hi,
>
> On Thu, Feb 09, 2023 at 10:20:36AM +, Richard Purdie wrote:
> > On Thu, 2023-02-09 at 10:09 +0200, Mikko Rapeli wrote:
> > > When qemu machine hangs, the ssh commands done by tests
> > > are not timing out. do_testimage() task ha
Hi,
On Thu, Feb 09, 2023 at 10:20:36AM +, Richard Purdie wrote:
> On Thu, 2023-02-09 at 10:09 +0200, Mikko Rapeli wrote:
> > 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, en
On Thu, 2023-02-09 at 10:09 +0200, Mikko Rapeli wrote:
> 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
On Thu, 9 Feb 2023 at 10:56, Mikko Rapeli wrote:
> It doesn't currently. Should the sigterm_handler() also use SIGKILL if
> it has to?
Yes please. Let's not duplicate functionality. And please do try to
avoid adding hard sleep(), there are usually ways to do things
synchronously.
Alex
-=-=-=-=-
There is a redundant change in
0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch that
causes wordsize.h to be different in arm and aarch64. This causes the
build error when enable multilib:
Error: Transaction test error:
file /usr/include/bits/wordsize.h conflicts between attempted
Hi,
On Thu, Feb 09, 2023 at 10:45:36AM +0100, Alexander Kanavin wrote:
> Isn't the code waiting 5 seconds and then sending SIGKILL, regardless
> of whether SIGTERM was successful or not here?
Yes. Not nice but better than leaking the process completely.
> I would actually remove this function al
Isn't the code waiting 5 seconds and then sending SIGKILL, regardless
of whether SIGTERM was successful or not here?
I would actually remove this function altogether. qemu process is
started by runqemu and it's the job of that to clean up the actual
qemu process properly.
Alex
On Thu, 9 Feb 2023
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Mateusz Marciniec
> Sent: den 9 februari 2023 00:50
> To: openembedded-core@lists.openembedded.org
> Cc: Mateusz Marciniec ; Tomasz Dziendzielski
>
> Subject: [OE-core][PATCH] sstatesig: Improve output
Hi,
On Thu, Feb 09, 2023 at 09:15:10AM +, Richard Purdie wrote:
> On Thu, 2023-02-09 at 10:09 +0200, Mikko Rapeli wrote:
> > 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, en
Thank you, but please submit for master first, and only then for LTS branches.
Alex
On Thu, 9 Feb 2023 at 09:26, mv wrote:
>
> From: Siddharth Doshi
>
> OpenSSL 3.0.8 fixes 1 HIGH level security vulnerability and 7 MODERATE level
> security vulnerability [1].
>
> Upgrade the recipe to point to
On Thu, 9 Feb 2023 at 09:58, Richard Purdie
wrote:
> This failure could have many causes. To try and help narrow it down,
> does another oe-selftest that uses runqemu work ok? That would tell us
> if this is specific to the rust test or a more general issue since the
> other tests are known to wor
On Thu, 2023-02-09 at 10:09 +0200, Mikko Rapeli wrote:
> 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
On Thu, 2023-02-09 at 06:38 +, Shinde, Yash wrote:
> I got the following error while logging in to qemu for Rust Oe-
> Selftest forx86 target:
>
> 2023-02-07 04:09:21,688 - oe-selftest - INFO - Traceback (most recent
> call last):
>
> File "/ala-lpggp31/yshinde/rust-
> oe/poky/meta/lib/oeqa
From: Siddharth Doshi
OpenSSL 3.0.8 fixes 1 HIGH level security vulnerability and 7 MODERATE level
security vulnerability [1].
Upgrade the recipe to point to 3.0.8.
CVE-2022-3996 is reported fixed in 3.0.8, so drop the patch for that as
well.
[1] https://www.openssl.org/news/vulnerabilities.h
When a qemu machine hangs, the QMP calls can hang for ever
too, and when this happens any failing test commands from ssh
runner may be followed by dump_monitor() calls which
then also hang. Hangs followed by hangs.
Use runqemutime at setup and run_monitor() specific timeout
for later calls.
Signe
qemu doesn't always behave well and can hang too.
kill it with force if was still alive.
Signed-off-by: Mikko Rapeli
---
meta/lib/oeqa/utils/qemurunner.py | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/lib/oeqa/utils/qemurunner.py
b/meta/lib/oeqa/utils/qemurunner.py
index bce00
Read from serial console with a small delay to bundle data to e.g.
full lines. Reading one character at a time is not needed and causes
busy looping.
Signed-off-by: Mikko Rapeli
---
meta/lib/oeqa/utils/qemurunner.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/utils/qemuru
If test target qemu machine hangs completely, dump_target() calls
over serial console are taking a long time to time out, possibly
for every failing ssh command execution and a lot of test cases,
and same with dump_monitor().
Instead of trying for ever, count errors and after 5 stop trying
to dump
Use a short sleep to bundle serial console reads so that
we are not reading one character at a time which reduces busy
looping.
Signed-off-by: Mikko Rapeli
---
meta/lib/oeqa/utils/qemurunner.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils/qemurunner.
Configure ssh client to test that connection with server is up.
If the server does not respond within a minute then the connection,
target machine or sshd daemon are stuck and it's better to exit
the command execution with errors.
Some tests can execute a long time without returning stdout/stderro
I get a qemu hang on kirkstone, swtpm and optee. One of the
optee-test/xtest hangs the qemu machine in some kind of deadlock.
While this needs to be debugged and fixed, the oeqa runtime tests
also hanged and never returned. Thus this patch set. With these changes
qemu deadlock is detected and do_te
The output from is garbled otherwise and it's not
easy to remove debug output form real command output on target.
Signed-off-by: Mikko Rapeli
---
meta/lib/oeqa/core/target/ssh.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/lib/oeqa/core/target/ssh.py b/meta/lib
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 correct
From: Siddharth Doshi
OpenSSL 3.0.8 fixes 1 HIGH level security vulnerability and 7 MODERATE level
security vulnerability [1].
Upgrade the recipe to point to 3.0.8.
CVE-2022-3996 is reported fixed in 3.0.8, so drop the patch for that as
well.
[1] https://www.openssl.org/news/vulnerabilities.h
67 matches
Mail list logo