date:20220601

This is effectively updating to a development snapshot, would it be
better to backport just the CVE fix like was just sent for dunfell?

Alex

On Tue, 31 May 2022 at 16:16, Davide Gardenal  wrote:
>
> CVE: CVE-2022-29458
>
> Signed-off-by: Davide Gardenal 
> ---
>  meta/recipes-core/ncurses/ncurses.inc | 2 +-
>  .../ncurses/{ncurses_6.3.bb => ncurses_6.3+20220423.bb}   | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
>  rename meta/recipes-core/ncurses/{ncurses_6.3.bb => ncurses_6.3+20220423.bb} 
> (77%)
>
> diff --git a/meta/recipes-core/ncurses/ncurses.inc 
> b/meta/recipes-core/ncurses/ncurses.inc
> index 7a7c7dd227..1abcfae1fe 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -2,7 +2,7 @@ SUMMARY = "The New Curses library"
>  DESCRIPTION = "SVr4 and XSI-Curses compatible curses library and terminfo 
> tools including tic, infocmp, captoinfo. Supports color, multiple highlights, 
> forms-drawing characters, and automatic recognition of keypad and 
> function-key sequences. Extensions include resizable windows and mouse 
> support on both xterm and Linux console using the gpm library."
>  HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html";
>  LICENSE = "MIT"
> -LIC_FILES_CHKSUM = 
> "file://COPYING;md5=9529289636145d1bf093c96af067695a;endline=27"
> +LIC_FILES_CHKSUM = 
> "file://COPYING;md5=c5a4600fdef86384c41ca33ecc70a4b8;endline=27"
>  SECTION = "libs"
>  DEPENDS = "ncurses-native"
>  DEPENDS:class-native = ""
> diff --git a/meta/recipes-core/ncurses/ncurses_6.3.bb 
> b/meta/recipes-core/ncurses/ncurses_6.3+20220423.bb
> similarity index 77%
> rename from meta/recipes-core/ncurses/ncurses_6.3.bb
> rename to meta/recipes-core/ncurses/ncurses_6.3+20220423.bb
> index f0256dad22..f67a3f5bf4 100644
> --- a/meta/recipes-core/ncurses/ncurses_6.3.bb
> +++ b/meta/recipes-core/ncurses/ncurses_6.3+20220423.bb
> @@ -5,10 +5,10 @@ SRC_URI += "file://0001-tic-hang.patch \
> 
> file://0003-gen-pkgconfig.in-Do-not-include-LDFLAGS-in-generated.patch \
> "
>  # commit id corresponds to the revision in package version
> -SRCREV = "51d0fd9cc3edb975f04224f29f777f8f448e8ced"
> +SRCREV = "a0bc708bc6954b5d3c0a38d92b683c3ec3135260"
>  S = "${WORKDIR}/git"
>  EXTRA_OECONF += "--with-abi-version=5"
>  UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+(\.\d+)+)$"
>
>  # This is needed when using patchlevel versions like 6.1+20181013
> -#CVE_VERSION = 
> "${@d.getVar("PV").split('+')[0]}.${@d.getVar("PV").split('+')[1]}"
> +CVE_VERSION = 
> "${@d.getVar("PV").split('+')[0]}.${@d.getVar("PV").split('+')[1]}"
> --
> 2.32.0
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166357): 
https://lists.openembedded.org/g/openembedded-core/message/166357
Mute This Topic: https://lists.openembedded.org/mt/91451965/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

This should go to meta-oe I think. Does it have to be in core, and if so why?

Alex

On Tue, 31 May 2022 at 23:32, Marcel Ziswiler  wrote:
>
> From: Peter Bergin 
>
> In order to enable configuration option aaf (AVTP Audio Format)
> used for AVB the library libavtp is a dependency but no recipe for
> this library was present. aaf support for alsa-plugins was
> introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
>
> Signed-off-by: Peter Bergin 
> Signed-off-by: Marcel Ziswiler 
>
> ---
> Resurrect from mailing list [1] as this is still not upstream.
> End-to-end tested on Verdin iMX8M Plus.
> Will talk about it at the Embedded World Conference in the TSN & Linux
> track next month [2].
>
> [1] 
> https://lore.kernel.org/all/20210604090216.553285-1-pe...@berginkonsult.se/
> [2] https://events.weka-fachmedien.de/embedded-world-conference/program/
>
> Changes in v3:
> - Rename recipe to officially released PV of 0.2.0.
> - Drop PROVIDES of avtp which just works around alsa-plugins refering to
>   it as such instead of libavtp. Will update PACKAGECONFIG in
>   alsa-plugins instead.
>
> Changes in v2:
> - Updated SRC_URI specifying mandatory protocol as https.
> - Updated SRCREV to latest.
>
>  meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb | 14 ++
>  1 file changed, 14 insertions(+)
>  create mode 100644 meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
>
> diff --git a/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb 
> b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> new file mode 100644
> index 00..563debde3c
> --- /dev/null
> +++ b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> @@ -0,0 +1,14 @@
> +DESCRIPTION = "Open source implementation of Audio Video Transport Protocol 
> (AVTP) \
> +   specified in IEEE 1722-2016 spec."
> +HOMEPAGE = "https://github.com/Avnu/libavtp";
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=7fcb4331e23e45e171cd5693c1ff7d3e"
> +
> +SRC_URI = 
> "git://github.com/Avnu/libavtp.git;branch=v${PV};protocol=https;nobranch=1"
> +SRCREV = "3599a5bf2d18fc3ae89b64f208d8380e6ee3a866"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit meson pkgconfig
> +
> +EXTRA_OEMESON = "-Dtests=disabled"
> --
> 2.36.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166358): 
https://lists.openembedded.org/g/openembedded-core/message/166358
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [master][kirkstone][PATCH] ncurses: update to patchlevel 20220423

2022-06-01 Thread Davide Gardenal

Are you sure that this is a development snapshot?
I took this branch 
https://salsa.debian.org/debian/ncurses/-/tree/upstream/6.3+20220423
Sorry I'm not that familiar with ncurses version naming scheme.

Davide

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166359): 
https://lists.openembedded.org/g/openembedded-core/message/166359
Mute This Topic: https://lists.openembedded.org/mt/91451965/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [master][kirkstone][PATCH] ncurses: update to patchlevel 20220423

That is debian-specific versioning, but upstream has its releases here:
https://ftp.gnu.org/pub/gnu/ncurses/

On top of that there are patches, each numbered with a date, but
they're not releases:
https://salsa.debian.org/debian/ncurses/-/commits/upstream/6.3+20220423

Alex

On Wed, 1 Jun 2022 at 09:35, Davide Gardenal  wrote:
>
> Are you sure that this is a development snapshot?
> I took this branch 
> https://salsa.debian.org/debian/ncurses/-/tree/upstream/6.3+20220423
> Sorry I'm not that familiar with ncurses version naming scheme.
>
> Davide
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166360): 
https://lists.openembedded.org/g/openembedded-core/message/166360
Mute This Topic: https://lists.openembedded.org/mt/91451965/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/4] qemu: fix CVE-2021-3750

2022-06-01 Thread Davide Gardenal

Could you send this one for kirkstone too?
You just need to change qemu.inc diff in theory.

Thanks,
Davide

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166361): 
https://lists.openembedded.org/g/openembedded-core/message/166361
Mute This Topic: https://lists.openembedded.org/mt/91468556/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

On Wed, 2022-06-01 at 09:30 +0200, Alexander Kanavin wrote:
> This should go to meta-oe I think. Does it have to be in core, and if so why?

Good question. However, alsa-plugins (and gstreamer1.0-plugins-bad for that 
matter) also live there and may
depend on it.

> Alex

Cheers

Marcel

> On Tue, 31 May 2022 at 23:32, Marcel Ziswiler  wrote:
> > 
> > From: Peter Bergin 
> > 
> > In order to enable configuration option aaf (AVTP Audio Format)
> > used for AVB the library libavtp is a dependency but no recipe for
> > this library was present. aaf support for alsa-plugins was
> > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > 
> > Signed-off-by: Peter Bergin 
> > Signed-off-by: Marcel Ziswiler 
> > 
> > ---
> > Resurrect from mailing list [1] as this is still not upstream.
> > End-to-end tested on Verdin iMX8M Plus.
> > Will talk about it at the Embedded World Conference in the TSN & Linux
> > track next month [2].
> > 
> > [1] 
> > https://lore.kernel.org/all/20210604090216.553285-1-pe...@berginkonsult.se/
> > [2] https://events.weka-fachmedien.de/embedded-world-conference/program/
> > 
> > Changes in v3:
> > - Rename recipe to officially released PV of 0.2.0.
> > - Drop PROVIDES of avtp which just works around alsa-plugins refering to
> >   it as such instead of libavtp. Will update PACKAGECONFIG in
> >   alsa-plugins instead.
> > 
> > Changes in v2:
> > - Updated SRC_URI specifying mandatory protocol as https.
> > - Updated SRCREV to latest.
> > 
> >  meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb | 14 ++
> >  1 file changed, 14 insertions(+)
> >  create mode 100644 meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > 
> > diff --git a/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb 
> > b/meta/recipes-
> > multimedia/libavtp/libavtp_0.2.0.bb
> > new file mode 100644
> > index 00..563debde3c
> > --- /dev/null
> > +++ b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > @@ -0,0 +1,14 @@
> > +DESCRIPTION = "Open source implementation of Audio Video Transport 
> > Protocol (AVTP) \
> > +   specified in IEEE 1722-2016 spec."
> > +HOMEPAGE = "https://github.com/Avnu/libavtp";
> > +LICENSE = "BSD-3-Clause"
> > +LIC_FILES_CHKSUM = "file://LICENSE;md5=7fcb4331e23e45e171cd5693c1ff7d3e"
> > +
> > +SRC_URI = 
> > "git://github.com/Avnu/libavtp.git;branch=v${PV};protocol=https;nobranch=1"
> > +SRCREV = "3599a5bf2d18fc3ae89b64f208d8380e6ee3a866"
> > +
> > +S = "${WORKDIR}/git"
> > +
> > +inherit meson pkgconfig
> > +
> > +EXTRA_OEMESON = "-Dtests=disabled"
> > --
> > 2.36.1
> > 
> > 
> > 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166362): 
https://lists.openembedded.org/g/openembedded-core/message/166362
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

2022-06-01 Thread Quentin Schulz


Marcel, Peter,

On 5/31/22 23:32, Marcel Ziswiler wrote:

From: Peter Bergin 

In order to enable configuration option aaf (AVTP Audio Format)
used for AVB the library libavtp is a dependency but no recipe for
this library was present. aaf support for alsa-plugins was
introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.

Signed-off-by: Peter Bergin 
Signed-off-by: Marcel Ziswiler 

---
Resurrect from mailing list [1] as this is still not upstream.
End-to-end tested on Verdin iMX8M Plus.
Will talk about it at the Embedded World Conference in the TSN & Linux
track next month [2].

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__lore.kernel.org_all_20210604090216.553285-2D1-2Dpeter-40berginkonsult.se_&d=DwIDAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=j5mDhOeNcVWNco5eYp6S60KnL4GmuLwFOeDnKizzUfY4ScAsBe2IQUQckKzHOrVn&s=1nRYQeY7NOzqrW7qZafcgBMa2RIx8BtF-kVsHpEX-5c&e=
[2] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__events.weka-2Dfachmedien.de_embedded-2Dworld-2Dconference_program_&d=DwIDAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=j5mDhOeNcVWNco5eYp6S60KnL4GmuLwFOeDnKizzUfY4ScAsBe2IQUQckKzHOrVn&s=EnuuWrWZcXP5wNN4T2S7S57HMhsQNkAZRpv0q1iyMW8&e=

Changes in v3:
- Rename recipe to officially released PV of 0.2.0.
- Drop PROVIDES of avtp which just works around alsa-plugins refering to
   it as such instead of libavtp. Will update PACKAGECONFIG in
   alsa-plugins instead.

Changes in v2:
- Updated SRC_URI specifying mandatory protocol as https.
- Updated SRCREV to latest.

  meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb | 14 ++
  1 file changed, 14 insertions(+)
  create mode 100644 meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb

diff --git a/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb 
b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
new file mode 100644
index 00..563debde3c
--- /dev/null
+++ b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
@@ -0,0 +1,14 @@
+DESCRIPTION = "Open source implementation of Audio Video Transport Protocol 
(AVTP) \
+   specified in IEEE 1722-2016 spec."
+HOMEPAGE = 
"https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Avnu_libavtp&d=DwIDAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=j5mDhOeNcVWNco5eYp6S60KnL4GmuLwFOeDnKizzUfY4ScAsBe2IQUQckKzHOrVn&s=CDG7OGmgTZNqph7uuR6Au6HBdZZmu_0lUYUC1dYWjsg&e=
 "
+LICENSE = "BSD-3-Clause"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=7fcb4331e23e45e171cd5693c1ff7d3e"
+
+SRC_URI = 
"git://github.com/Avnu/libavtp.git;branch=v${PV};protocol=https;nobranch=1"


We don't have a single recipe with nobranch set in poky, so I think we 
should keep it this way. I assume this was needed because, there's no 
${PV} branch available in the git repo (it's a tag).


Technically, ${PV} is a tag on github and not a branch. We don't have a 
single recipe with tag set in poky, so I think we also should keep it 
this way (tag= requires network to check that the tag hasn't moved 
between builds).


What I've seen some recipes do instead is to use github archives. See:
https://git.yoctoproject.org/poky/tree/meta/recipes-support/re2c/re2c_3.0.bb

Re: alsa-plugins which may require it in a PACKAGECONFIG option, it's 
not really a reason for inclusion if not enabled by default. Otherwise 
we would have one big layer only with all possible optional dependencies 
and their possible optional dependencies, etc...


Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166363): 
https://lists.openembedded.org/g/openembedded-core/message/166363
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

As long as the dependency is optional and controlled via PACKAGECONFIG
and off by default, the recipe does not have to be in core, and we
have plenty of examples of similar arrangements.

Alex

On Wed, 1 Jun 2022 at 10:05, Marcel Ziswiler  wrote:
>
> On Wed, 2022-06-01 at 09:30 +0200, Alexander Kanavin wrote:
> > This should go to meta-oe I think. Does it have to be in core, and if so 
> > why?
>
> Good question. However, alsa-plugins (and gstreamer1.0-plugins-bad for that 
> matter) also live there and may
> depend on it.
>
> > Alex
>
> Cheers
>
> Marcel
>
> > On Tue, 31 May 2022 at 23:32, Marcel Ziswiler  wrote:
> > >
> > > From: Peter Bergin 
> > >
> > > In order to enable configuration option aaf (AVTP Audio Format)
> > > used for AVB the library libavtp is a dependency but no recipe for
> > > this library was present. aaf support for alsa-plugins was
> > > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > >
> > > Signed-off-by: Peter Bergin 
> > > Signed-off-by: Marcel Ziswiler 
> > >
> > > ---
> > > Resurrect from mailing list [1] as this is still not upstream.
> > > End-to-end tested on Verdin iMX8M Plus.
> > > Will talk about it at the Embedded World Conference in the TSN & Linux
> > > track next month [2].
> > >
> > > [1] 
> > > https://lore.kernel.org/all/20210604090216.553285-1-pe...@berginkonsult.se/
> > > [2] https://events.weka-fachmedien.de/embedded-world-conference/program/
> > >
> > > Changes in v3:
> > > - Rename recipe to officially released PV of 0.2.0.
> > > - Drop PROVIDES of avtp which just works around alsa-plugins refering to
> > >   it as such instead of libavtp. Will update PACKAGECONFIG in
> > >   alsa-plugins instead.
> > >
> > > Changes in v2:
> > > - Updated SRC_URI specifying mandatory protocol as https.
> > > - Updated SRCREV to latest.
> > >
> > >  meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb | 14 ++
> > >  1 file changed, 14 insertions(+)
> > >  create mode 100644 meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > >
> > > diff --git a/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb 
> > > b/meta/recipes-
> > > multimedia/libavtp/libavtp_0.2.0.bb
> > > new file mode 100644
> > > index 00..563debde3c
> > > --- /dev/null
> > > +++ b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > > @@ -0,0 +1,14 @@
> > > +DESCRIPTION = "Open source implementation of Audio Video Transport 
> > > Protocol (AVTP) \
> > > +   specified in IEEE 1722-2016 spec."
> > > +HOMEPAGE = "https://github.com/Avnu/libavtp";
> > > +LICENSE = "BSD-3-Clause"
> > > +LIC_FILES_CHKSUM = "file://LICENSE;md5=7fcb4331e23e45e171cd5693c1ff7d3e"
> > > +
> > > +SRC_URI = 
> > > "git://github.com/Avnu/libavtp.git;branch=v${PV};protocol=https;nobranch=1"
> > > +SRCREV = "3599a5bf2d18fc3ae89b64f208d8380e6ee3a866"
> > > +
> > > +S = "${WORKDIR}/git"
> > > +
> > > +inherit meson pkgconfig
> > > +
> > > +EXTRA_OEMESON = "-Dtests=disabled"
> > > --
> > > 2.36.1
> > >
> > >
> > > 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166364): 
https://lists.openembedded.org/g/openembedded-core/message/166364
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

Hi Quentin

On Wed, 2022-06-01 at 10:13 +0200, Quentin Schulz wrote:
> Marcel, Peter,
> 
> On 5/31/22 23:32, Marcel Ziswiler wrote:
> > From: Peter Bergin 
> > 

[snip]

> > +
> > +SRC_URI = 
> > "git://github.com/Avnu/libavtp.git;branch=v${PV};protocol=https;nobranch=1"
> 
> We don't have a single recipe with nobranch set in poky, so I think we 
> should keep it this way. I assume this was needed because, there's no 
> ${PV} branch available in the git repo (it's a tag).
> 
> Technically, ${PV} is a tag on github and not a branch. We don't have a 
> single recipe with tag set in poky, so I think we also should keep it 
> this way (tag= requires network to check that the tag hasn't moved 
> between builds).

Well, remember. It wasn't me suggesting the use of PV. However, at least at 
first it really sounded like a
sensible goal.

> What I've seen some recipes do instead is to use github archives. See:
> https://git.yoctoproject.org/poky/tree/meta/recipes-support/re2c/re2c_3.0.bb

I have been there before, but, unfortunately, Avnu's libavtp on github only 
uses their archive [1] and not some
other download facility whose use is also discouraged as per [2].

I mean I guess I could just rename the recipe and otherwise keep relying on git 
with a hash but that also does
not seem like a really good option (e.g. keeping PV and hash in sync and/or 
even checking on this would be a
completely manual task). Not sure. I hope somebody more experienced might 
present the golden trick to this
dilemma. Thanks!

[1] https://github.com/Avnu/libavtp/archive/refs/tags/v0.2.0.tar.gz
[2] https://git.yoctoproject.org/poky/tree/scripts/lib/recipetool/create.py#n430

> Re: alsa-plugins which may require it in a PACKAGECONFIG option, it's 
> not really a reason for inclusion if not enabled by default. Otherwise 
> we would have one big layer only with all possible optional dependencies 
> and their possible optional dependencies, etc...
> 
> Cheers,
> Quentin

Cheers

Marcel

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166365): 
https://lists.openembedded.org/g/openembedded-core/message/166365
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

On Wed, 2022-06-01 at 10:22 +0200, Alexander Kanavin wrote:
> As long as the dependency is optional and controlled via PACKAGECONFIG
> and off by default, the recipe does not have to be in core, and we
> have plenty of examples of similar arrangements.

Understood and agreed. Let me move it.

Still waiting on the resolution of the git hash tag vs. PV download dilemma 
though...

Thanks!

> Alex

Cheers

Marcel

> On Wed, 1 Jun 2022 at 10:05, Marcel Ziswiler  wrote:
> > 
> > On Wed, 2022-06-01 at 09:30 +0200, Alexander Kanavin wrote:
> > > This should go to meta-oe I think. Does it have to be in core, and if so 
> > > why?
> > 
> > Good question. However, alsa-plugins (and gstreamer1.0-plugins-bad for that 
> > matter) also live there and may
> > depend on it.
> > 
> > > Alex
> > 
> > Cheers
> > 
> > Marcel
> > 
> > > On Tue, 31 May 2022 at 23:32, Marcel Ziswiler  wrote:
> > > > 
> > > > From: Peter Bergin 
> > > > 
> > > > In order to enable configuration option aaf (AVTP Audio Format)
> > > > used for AVB the library libavtp is a dependency but no recipe for
> > > > this library was present. aaf support for alsa-plugins was
> > > > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > > > 
> > > > Signed-off-by: Peter Bergin 
> > > > Signed-off-by: Marcel Ziswiler 
> > > > 
> > > > ---
> > > > Resurrect from mailing list [1] as this is still not upstream.
> > > > End-to-end tested on Verdin iMX8M Plus.
> > > > Will talk about it at the Embedded World Conference in the TSN & Linux
> > > > track next month [2].
> > > > 
> > > > [1] 
> > > > https://lore.kernel.org/all/20210604090216.553285-1-pe...@berginkonsult.se/
> > > > [2] https://events.weka-fachmedien.de/embedded-world-conference/program/
> > > > 
> > > > Changes in v3:
> > > > - Rename recipe to officially released PV of 0.2.0.
> > > > - Drop PROVIDES of avtp which just works around alsa-plugins refering to
> > > >   it as such instead of libavtp. Will update PACKAGECONFIG in
> > > >   alsa-plugins instead.
> > > > 
> > > > Changes in v2:
> > > > - Updated SRC_URI specifying mandatory protocol as https.
> > > > - Updated SRCREV to latest.
> > > > 
> > > >  meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb | 14 ++
> > > >  1 file changed, 14 insertions(+)
> > > >  create mode 100644 meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > > > 
> > > > diff --git a/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb 
> > > > b/meta/recipes-
> > > > multimedia/libavtp/libavtp_0.2.0.bb
> > > > new file mode 100644
> > > > index 00..563debde3c
> > > > --- /dev/null
> > > > +++ b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > > > @@ -0,0 +1,14 @@
> > > > +DESCRIPTION = "Open source implementation of Audio Video Transport 
> > > > Protocol (AVTP) \
> > > > +   specified in IEEE 1722-2016 spec."
> > > > +HOMEPAGE = "https://github.com/Avnu/libavtp";
> > > > +LICENSE = "BSD-3-Clause"
> > > > +LIC_FILES_CHKSUM = 
> > > > "file://LICENSE;md5=7fcb4331e23e45e171cd5693c1ff7d3e"
> > > > +
> > > > +SRC_URI = 
> > > > "git://github.com/Avnu/libavtp.git;branch=v${PV};protocol=https;nobranch=1"
> > > > +SRCREV = "3599a5bf2d18fc3ae89b64f208d8380e6ee3a866"
> > > > +
> > > > +S = "${WORKDIR}/git"
> > > > +
> > > > +inherit meson pkgconfig
> > > > +
> > > > +EXTRA_OEMESON = "-Dtests=disabled"
> > > > --
> > > > 2.36.1
> > > > 
> > > > 
> > > > 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166366): 
https://lists.openembedded.org/g/openembedded-core/message/166366
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell][PATCH v2] curl: Add fix for CVE-2022-27781 CVE-2022-27782

2022-06-01 Thread Riyaz Ahmed Khan

From: Riyaz Khan 

Add patches for CVE issues: CVE-2022-27781 CVE-2022-27782

CVE-2022-27781
Link: 
[https://github.com/curl/curl/commit/5c7da89d404bf59c8dd82a001119a16d18365917]

CVE-2022-27782
Link: 
[https://github.com/curl/curl/commit/1645e9b44505abd5cbaf65da5282c3f33b5924a5]

Change-Id: I6ebe14ff8caf809f8332bb785b159090f5046896
Signed-off-by: Riyaz Khan 
---
 .../curl/curl/CVE-2022-27781.patch| 50 +
 .../curl/curl/CVE-2022-27782.patch| 75 +++
 meta/recipes-support/curl/curl_7.69.1.bb  |  2 +
 3 files changed, 127 insertions(+)
 create mode 100644 meta/recipes-support/curl/curl/CVE-2022-27781.patch
 create mode 100644 meta/recipes-support/curl/curl/CVE-2022-27782.patch

diff --git a/meta/recipes-support/curl/curl/CVE-2022-27781.patch 
b/meta/recipes-support/curl/curl/CVE-2022-27781.patch
new file mode 100644
index 00..83cdd1290f
--- /dev/null
+++ b/meta/recipes-support/curl/curl/CVE-2022-27781.patch
@@ -0,0 +1,50 @@
+From 5c7da89d404bf59c8dd82a001119a16d18365917 Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg 
+Date: Mon, 9 May 2022 10:07:15 +0200
+Subject: [PATCH] nss: return error if seemingly stuck in a cert loop
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+CVE-2022-27781
+
+Reported-by: Florian Kohnhäuser
+Bug: https://curl.se/docs/CVE-2022-27781.html
+Closes #8822
+
+CVE: CVE-2022-27781
+
+Upstream-Status: Backport 
[https://github.com/curl/curl/commit/5c7da89d404bf59c8dd82a001119a16d18365917]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ lib/vtls/nss.c | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/lib/vtls/nss.c b/lib/vtls/nss.c
+index 5b7de9f81895..569c0628feb5 100644
+--- a/lib/vtls/nss.c
 b/lib/vtls/nss.c
+@@ -983,6 +983,9 @@ static void display_cert_info(struct Curl_easy *data,
+   PR_Free(common_name);
+ }
+ 
++/* A number of certs that will never occur in a real server handshake */
++#define TOO_MANY_CERTS 300
++
+ static CURLcode display_conn_info(struct Curl_easy *data, PRFileDesc *sock)
+ {
+   CURLcode result = CURLE_OK;
+@@ -1018,6 +1021,11 @@ static CURLcode display_conn_info(struct Curl_easy 
*data, PRFileDesc *sock)
+ cert2 = CERT_FindCertIssuer(cert, now, certUsageSSLCA);
+ while(cert2) {
+   i++;
++  if(i >= TOO_MANY_CERTS) {
++CERT_DestroyCertificate(cert2);
++failf(data, "certificate loop");
++return CURLE_SSL_CERTPROBLEM;
++  }
+   if(cert2->isRoot) {
+ CERT_DestroyCertificate(cert2);
+ break;
diff --git a/meta/recipes-support/curl/curl/CVE-2022-27782.patch 
b/meta/recipes-support/curl/curl/CVE-2022-27782.patch
new file mode 100644
index 00..a88aabe517
--- /dev/null
+++ b/meta/recipes-support/curl/curl/CVE-2022-27782.patch
@@ -0,0 +1,75 @@
+From 1645e9b44505abd5cbaf65da5282c3f33b5924a5 Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg 
+Date: Mon, 9 May 2022 23:13:53 +0200
+Subject: [PATCH] url: check SSH config match on connection reuse
+
+CVE-2022-27782
+
+Reported-by: Harry Sintonen
+Bug: https://curl.se/docs/CVE-2022-27782.html
+Closes #8825
+
+CVE: CVE-2022-27782
+
+Upstream-Status: Backport 
[https://github.com/curl/curl/commit/1645e9b44505abd5cbaf65da5282c3f33b5924a5]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ lib/url.c  | 11 +++
+ lib/vssh/ssh.h |  6 +++---
+ 2 files changed, 14 insertions(+), 3 deletions(-)
+
+diff --git a/lib/url.c b/lib/url.c
+index cf14a333ac69..6b31d4b1315d 100644
+--- a/lib/url.c
 b/lib/url.c
+@@ -1100,6 +1100,12 @@ static void prune_dead_connections(struct Curl_easy 
*data)
+   }
+ }
+ 
++static bool ssh_config_matches(struct connectdata *one,
++   struct connectdata *two)
++{
++  return (Curl_safecmp(one->proto.sshc.rsa, two->proto.sshc.rsa) &&
++  Curl_safecmp(one->proto.sshc.rsa_pub, two->proto.sshc.rsa_pub));
++}
+ /*
+  * Given one filled in connection struct (named needle), this function should
+  * detect if there already is one that has all the significant details
+@@ -1356,6 +1362,11 @@ ConnectionExists(struct Curl_easy *data,
+  (data->state.httpwant < CURL_HTTP_VERSION_2_0))
+ continue;
+ 
++  if(get_protocol_family(needle->handler) == PROTO_FAMILY_SSH) {
++if(!ssh_config_matches(needle, check))
++  continue;
++  }
++
+   if((needle->handler->flags&PROTOPT_SSL)
+ #ifndef CURL_DISABLE_PROXY
+  || !needle->bits.httpproxy || needle->bits.tunnel_proxy
+diff --git a/lib/vssh/ssh.h b/lib/vssh/ssh.h
+index 7972081ec610..30d82e57648e 100644
+--- a/lib/vssh/ssh.h
 b/lib/vssh/ssh.h
+@@ -7,7 +7,7 @@
+  *| (__| |_| |  _ <| |___
+  * \___|\___/|_| \_\_|
+  *
+- * Copyright (C) 1998 - 2021, Daniel Stenberg, , et al.
++ * Copyright (C) 1998 - 2022, Daniel Stenberg, , et al.
+  *
+  * This software is licensed as described in the file COPYI

[OE-core][dunfell][PATCH v2] curl: Add fix for CVE-2022-27781 CVE-2022-27782

2022-06-01 Thread Riyaz Ahmed Khan

From: Riyaz Khan 

Add patches for CVE issues: CVE-2022-27781 CVE-2022-27782

CVE-2022-27781
Link: 
[https://github.com/curl/curl/commit/5c7da89d404bf59c8dd82a001119a16d18365917]

CVE-2022-27782
Link: 
[https://github.com/curl/curl/commit/1645e9b44505abd5cbaf65da5282c3f33b5924a5]

Signed-off-by: Riyaz Khan 
---
 .../curl/curl/CVE-2022-27781.patch| 50 +
 .../curl/curl/CVE-2022-27782.patch| 75 +++
 meta/recipes-support/curl/curl_7.69.1.bb  |  2 +
 3 files changed, 127 insertions(+)
 create mode 100644 meta/recipes-support/curl/curl/CVE-2022-27781.patch
 create mode 100644 meta/recipes-support/curl/curl/CVE-2022-27782.patch

diff --git a/meta/recipes-support/curl/curl/CVE-2022-27781.patch 
b/meta/recipes-support/curl/curl/CVE-2022-27781.patch
new file mode 100644
index 00..83cdd1290f
--- /dev/null
+++ b/meta/recipes-support/curl/curl/CVE-2022-27781.patch
@@ -0,0 +1,50 @@
+From 5c7da89d404bf59c8dd82a001119a16d18365917 Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg 
+Date: Mon, 9 May 2022 10:07:15 +0200
+Subject: [PATCH] nss: return error if seemingly stuck in a cert loop
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+CVE-2022-27781
+
+Reported-by: Florian Kohnhäuser
+Bug: https://curl.se/docs/CVE-2022-27781.html
+Closes #8822
+
+CVE: CVE-2022-27781
+
+Upstream-Status: Backport 
[https://github.com/curl/curl/commit/5c7da89d404bf59c8dd82a001119a16d18365917]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ lib/vtls/nss.c | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/lib/vtls/nss.c b/lib/vtls/nss.c
+index 5b7de9f81895..569c0628feb5 100644
+--- a/lib/vtls/nss.c
 b/lib/vtls/nss.c
+@@ -983,6 +983,9 @@ static void display_cert_info(struct Curl_easy *data,
+   PR_Free(common_name);
+ }
+ 
++/* A number of certs that will never occur in a real server handshake */
++#define TOO_MANY_CERTS 300
++
+ static CURLcode display_conn_info(struct Curl_easy *data, PRFileDesc *sock)
+ {
+   CURLcode result = CURLE_OK;
+@@ -1018,6 +1021,11 @@ static CURLcode display_conn_info(struct Curl_easy 
*data, PRFileDesc *sock)
+ cert2 = CERT_FindCertIssuer(cert, now, certUsageSSLCA);
+ while(cert2) {
+   i++;
++  if(i >= TOO_MANY_CERTS) {
++CERT_DestroyCertificate(cert2);
++failf(data, "certificate loop");
++return CURLE_SSL_CERTPROBLEM;
++  }
+   if(cert2->isRoot) {
+ CERT_DestroyCertificate(cert2);
+ break;
diff --git a/meta/recipes-support/curl/curl/CVE-2022-27782.patch 
b/meta/recipes-support/curl/curl/CVE-2022-27782.patch
new file mode 100644
index 00..a88aabe517
--- /dev/null
+++ b/meta/recipes-support/curl/curl/CVE-2022-27782.patch
@@ -0,0 +1,75 @@
+From 1645e9b44505abd5cbaf65da5282c3f33b5924a5 Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg 
+Date: Mon, 9 May 2022 23:13:53 +0200
+Subject: [PATCH] url: check SSH config match on connection reuse
+
+CVE-2022-27782
+
+Reported-by: Harry Sintonen
+Bug: https://curl.se/docs/CVE-2022-27782.html
+Closes #8825
+
+CVE: CVE-2022-27782
+
+Upstream-Status: Backport 
[https://github.com/curl/curl/commit/1645e9b44505abd5cbaf65da5282c3f33b5924a5]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ lib/url.c  | 11 +++
+ lib/vssh/ssh.h |  6 +++---
+ 2 files changed, 14 insertions(+), 3 deletions(-)
+
+diff --git a/lib/url.c b/lib/url.c
+index cf14a333ac69..6b31d4b1315d 100644
+--- a/lib/url.c
 b/lib/url.c
+@@ -1100,6 +1100,12 @@ static void prune_dead_connections(struct Curl_easy 
*data)
+   }
+ }
+ 
++static bool ssh_config_matches(struct connectdata *one,
++   struct connectdata *two)
++{
++  return (Curl_safecmp(one->proto.sshc.rsa, two->proto.sshc.rsa) &&
++  Curl_safecmp(one->proto.sshc.rsa_pub, two->proto.sshc.rsa_pub));
++}
+ /*
+  * Given one filled in connection struct (named needle), this function should
+  * detect if there already is one that has all the significant details
+@@ -1356,6 +1362,11 @@ ConnectionExists(struct Curl_easy *data,
+  (data->state.httpwant < CURL_HTTP_VERSION_2_0))
+ continue;
+ 
++  if(get_protocol_family(needle->handler) == PROTO_FAMILY_SSH) {
++if(!ssh_config_matches(needle, check))
++  continue;
++  }
++
+   if((needle->handler->flags&PROTOPT_SSL)
+ #ifndef CURL_DISABLE_PROXY
+  || !needle->bits.httpproxy || needle->bits.tunnel_proxy
+diff --git a/lib/vssh/ssh.h b/lib/vssh/ssh.h
+index 7972081ec610..30d82e57648e 100644
+--- a/lib/vssh/ssh.h
 b/lib/vssh/ssh.h
+@@ -7,7 +7,7 @@
+  *| (__| |_| |  _ <| |___
+  * \___|\___/|_| \_\_|
+  *
+- * Copyright (C) 1998 - 2021, Daniel Stenberg, , et al.
++ * Copyright (C) 1998 - 2022, Daniel Stenberg, , et al.
+  *
+  * This software is licensed as described in the file COPYING, which
+  * you should have received as part of th

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

I'm not sure what the dilemma is, inspecting the repo shows that
there's a standard 0.2.0 tag pointing to a commit in the master
branch. You can look at pretty much any other recipe fetching from
git.
https://github.com/Avnu/libavtp/tags

Alex

On Wed, 1 Jun 2022 at 10:34, Marcel Ziswiler  wrote:
>
> On Wed, 2022-06-01 at 10:22 +0200, Alexander Kanavin wrote:
> > As long as the dependency is optional and controlled via PACKAGECONFIG
> > and off by default, the recipe does not have to be in core, and we
> > have plenty of examples of similar arrangements.
>
> Understood and agreed. Let me move it.
>
> Still waiting on the resolution of the git hash tag vs. PV download dilemma 
> though...
>
> Thanks!
>
> > Alex
>
> Cheers
>
> Marcel
>
> > On Wed, 1 Jun 2022 at 10:05, Marcel Ziswiler  wrote:
> > >
> > > On Wed, 2022-06-01 at 09:30 +0200, Alexander Kanavin wrote:
> > > > This should go to meta-oe I think. Does it have to be in core, and if 
> > > > so why?
> > >
> > > Good question. However, alsa-plugins (and gstreamer1.0-plugins-bad for 
> > > that matter) also live there and may
> > > depend on it.
> > >
> > > > Alex
> > >
> > > Cheers
> > >
> > > Marcel
> > >
> > > > On Tue, 31 May 2022 at 23:32, Marcel Ziswiler  
> > > > wrote:
> > > > >
> > > > > From: Peter Bergin 
> > > > >
> > > > > In order to enable configuration option aaf (AVTP Audio Format)
> > > > > used for AVB the library libavtp is a dependency but no recipe for
> > > > > this library was present. aaf support for alsa-plugins was
> > > > > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > > > >
> > > > > Signed-off-by: Peter Bergin 
> > > > > Signed-off-by: Marcel Ziswiler 
> > > > >
> > > > > ---
> > > > > Resurrect from mailing list [1] as this is still not upstream.
> > > > > End-to-end tested on Verdin iMX8M Plus.
> > > > > Will talk about it at the Embedded World Conference in the TSN & Linux
> > > > > track next month [2].
> > > > >
> > > > > [1] 
> > > > > https://lore.kernel.org/all/20210604090216.553285-1-pe...@berginkonsult.se/
> > > > > [2] 
> > > > > https://events.weka-fachmedien.de/embedded-world-conference/program/
> > > > >
> > > > > Changes in v3:
> > > > > - Rename recipe to officially released PV of 0.2.0.
> > > > > - Drop PROVIDES of avtp which just works around alsa-plugins refering 
> > > > > to
> > > > >   it as such instead of libavtp. Will update PACKAGECONFIG in
> > > > >   alsa-plugins instead.
> > > > >
> > > > > Changes in v2:
> > > > > - Updated SRC_URI specifying mandatory protocol as https.
> > > > > - Updated SRCREV to latest.
> > > > >
> > > > >  meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb | 14 ++
> > > > >  1 file changed, 14 insertions(+)
> > > > >  create mode 100644 meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > > > >
> > > > > diff --git a/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb 
> > > > > b/meta/recipes-
> > > > > multimedia/libavtp/libavtp_0.2.0.bb
> > > > > new file mode 100644
> > > > > index 00..563debde3c
> > > > > --- /dev/null
> > > > > +++ b/meta/recipes-multimedia/libavtp/libavtp_0.2.0.bb
> > > > > @@ -0,0 +1,14 @@
> > > > > +DESCRIPTION = "Open source implementation of Audio Video Transport 
> > > > > Protocol (AVTP) \
> > > > > +   specified in IEEE 1722-2016 spec."
> > > > > +HOMEPAGE = "https://github.com/Avnu/libavtp";
> > > > > +LICENSE = "BSD-3-Clause"
> > > > > +LIC_FILES_CHKSUM = 
> > > > > "file://LICENSE;md5=7fcb4331e23e45e171cd5693c1ff7d3e"
> > > > > +
> > > > > +SRC_URI = 
> > > > > "git://github.com/Avnu/libavtp.git;branch=v${PV};protocol=https;nobranch=1"
> > > > > +SRCREV = "3599a5bf2d18fc3ae89b64f208d8380e6ee3a866"
> > > > > +
> > > > > +S = "${WORKDIR}/git"
> > > > > +
> > > > > +inherit meson pkgconfig
> > > > > +
> > > > > +EXTRA_OEMESON = "-Dtests=disabled"
> > > > > --
> > > > > 2.36.1
> > > > >
> > > > >
> > > > > 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166369): 
https://lists.openembedded.org/g/openembedded-core/message/166369
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

2022-06-01 Thread Peter Bergin


On 2022-06-01 11:43, Alexander Kanavin wrote:

I'm not sure what the dilemma is, inspecting the repo shows that
there's a standard 0.2.0 tag pointing to a commit in the master
branch. You can look at pretty much any other recipe fetching from
git.
https://github.com/Avnu/libavtp/tags


Agree.

My suggestion for solution is 'SRC_URI=-...;branch=master...' + 
'SRCREV=' and rename recipe to libavtp_0.2.0.bb. I 
don't know if that is against any style guide or rules?


And also fine with a move to meta-openembedded.

/Peter



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166371): 
https://lists.openembedded.org/g/openembedded-core/message/166371
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell][PATCH 1/2] libxslt: update to v1.1.35

2022-06-01 Thread omkar

From: Markus Volk 

Security

[CVE-2021-30560] Fix use-after-free in xsltApplyTemplates
Fix memory leak in xsltDocumentElem (David King)
Fix memory leak in xsltCompileIdKeyPattern (David King)
Fix double-free with stylesheets containing entity nodes

Fixed regressions

Fix performance regression with predicates in patterns
Fix regression in xsltComputeSortResult

Bug fixes

Fix conflict resolution for templates with same priority
Fix xsl:number generating invalid UTF-8
Support attribute value templates in xsl:sort lang attributes
Don't pass first xsl:sort in xsl:apply-templates twice
Fix quadratic runtime with text and xsl:message

Don't allow empty EXSLT durations

Improvements

Add xsltproc --huge Argument via libxml XML_PARSE_HUGE (William N. Braswell, 
Jr.)

Tests, code quality, fuzzing

Remove .travis.yml
Fix some misleading indentation (David King)
Use actual types for templates in struct _xsltStylesheet
Add CI for CMake on MSVC (Markus Rickert)
Check for null pointer before calling freelocale
Add CI test for Python 3
Don't set maxDepth in XPath contexts
Transfer XPath limits to XPtr context
Stop using maxParserDepth XPath limit
Make long-to-double cast explicit in date.c
Disable LeakSanitizer
Run clang CI tests with -Wimplicit-int-conversion
Fix implicit-int-conversion warning in exslt/crypto.c
Fix clang -Wimplicit-int-conversion warning (David Kilzer)
Fix clang -Wconditional-uninitialized warning in libxslt/numbers.c (David 
Kilzer)
Fix -Wshadow warnings in libexslt/dynamic.c (David Kilzer)
Also search parent dir for source XML when fuzzing

Build system, portability

Add CMake build files (Markus Rickert)
Initial support for Python 3 (Suleyman Poyraz)
Call ANSI versions of WinAPI functions explicitly
Remove redundant flags from pkg-config files
Suppress automake warning in tests/XSLTMark
Fix linking libexslt dynamic library when using MinGW (Vadim Zeitlin)
Added platform specific path separators (Dmitriy Korovkin)
win32: allow passing *FLAGS on command line
Fix export of xsltExtMarker on Windows (David Kilzer)
Fix redundant includes already in libexslt.h (David Kilzer)
Minor fixes to configure.js
Fix variable syntax in Python configuration
Add new EXSLT string tests to EXTRA_DIST
Fix xml2-config check in configure script
win32: Add configuration for profiler (Chun-wei Fan)
Check whether 'xml2-config --dynamic' is supported

Documentation

Add Makefile rule to regenerate xsltproc.html
Update links
Remove MAINTAINERS
Upload documentation to GitLab Pages
Add documentation in devhelp format
Add --enable-rebuild-docs configure option
Fix libexslt header summaries
Fix validity of tutorial XML (David King)
Use DocBook URL for tutorial DTD (David King)
Update libxslt.doap
Add missing options to xsltproc man page

(From OE-Core rev: 6b5b1486bbd381b2b657645e91a1712332ddcb94)

Signed-off-by: Markus Volk 
Signed-off-by: Richard Purdie 
(cherry picked from commit daa312851681c55d81391b37a30a518f3e74e540)

Signed-off-by: Omkar Patil 
---
 .../libxslt/{libxslt_1.1.34.bb => libxslt_1.1.35.bb}| 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)
 rename meta/recipes-support/libxslt/{libxslt_1.1.34.bb => libxslt_1.1.35.bb} 
(89%)

diff --git a/meta/recipes-support/libxslt/libxslt_1.1.34.bb 
b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
similarity index 89%
rename from meta/recipes-support/libxslt/libxslt_1.1.34.bb
rename to meta/recipes-support/libxslt/libxslt_1.1.35.bb
index 63cce6fe06..0f25043743 100644
--- a/meta/recipes-support/libxslt/libxslt_1.1.34.bb
+++ b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
@@ -13,11 +13,9 @@ LIC_FILES_CHKSUM = 
"file://Copyright;md5=0cd9a07afbeb24026c9b03aecfeba458"
 SECTION = "libs"
 DEPENDS = "libxml2"
 
-SRC_URI = "http://xmlsoft.org/sources/libxslt-${PV}.tar.gz \
-  "
+SRC_URI = "https://download.gnome.org/sources/libxslt/1.1/libxslt-${PV}.tar.xz";
 
-SRC_URI[md5sum] = "db8765c8d076f1b6caafd9f2542a304a"
-SRC_URI[sha256sum] = 
"98b1bd46d6792925ad2dfe9a87452ea2adebf69dcb9919ffd55bf926a7f93f7f"
+SRC_URI[sha256sum] = 
"8247f33e9a872c6ac859aa45018bc4c4d00b97e2feac9eebc10c93ce1f34dd79"
 
 UPSTREAM_CHECK_REGEX = "libxslt-(?P\d+(\.\d+)+)\.tar"
 
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166372): 
https://lists.openembedded.org/g/openembedded-core/message/166372
Mute This Topic: https://lists.openembedded.org/mt/91472461/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell][PATCH 2/2] libxslt: Mark CVE-2022-29824 as not applying

2022-06-01 Thread omkar

From: Richard Purdie 

We have libxml2 2.9.14 and we don't link statically against libxml2 anyway
so the CVE doesn't apply to libxslt.

(From OE-Core rev: c6315d8a2a1429a0fb7563b1d6352ceee7bc222c)

Signed-off-by: Richard Purdie 
(cherry picked from commit ad63694e6df4f284879f7220962a821f97928eb0)
Signed-off-by: Omkar Patil 
---
 meta/recipes-support/libxslt/libxslt_1.1.35.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-support/libxslt/libxslt_1.1.35.bb 
b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
index 0f25043743..47a38deb13 100644
--- a/meta/recipes-support/libxslt/libxslt_1.1.35.bb
+++ b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
@@ -19,6 +19,10 @@ SRC_URI[sha256sum] = 
"8247f33e9a872c6ac859aa45018bc4c4d00b97e2feac9eebc10c93ce1f
 
 UPSTREAM_CHECK_REGEX = "libxslt-(?P\d+(\.\d+)+)\.tar"
 
+# We have libxml2 2.9.14 and we don't link statically with it anyway
+# so this isn't an issue.
+CVE_CHECK_WHITELIST += "CVE-2022-29824"
+
 S = "${WORKDIR}/libxslt-${PV}"
 
 BINCONFIG = "${bindir}/xslt-config"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166373): 
https://lists.openembedded.org/g/openembedded-core/message/166373
Mute This Topic: https://lists.openembedded.org/mt/91472462/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] linux-firmware: add support for building snapshots

2022-06-01 Thread Dmitry Baryshkov

In some cases it is useful to be able to test the snapshot of
linux-firmware (e.g. to test if the updated firmware works on the
particular hardware). Allow building the linux-firmware snapshots.

To switch to the most recent branch, add the following lines to the
local.conf file:

PREFERRED_VERSION_linux-firmware = "1:20220509+git%"
SRCREV:class-devupstream = "${AUTOREV}"
WHENCE_CHKSUM:class-devupstream:pn-linux-firmware = 
"4288aad55d189fa225d492526b8406d5"

Signed-off-by: Dmitry Baryshkov 
---
 .../linux-firmware/linux-firmware_20220509.bb | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20220509.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_20220509.bb
index 6e328e57260a..10a7036a1938 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20220509.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20220509.bb
@@ -69,6 +69,7 @@ LICENSE = "\
 & WHENCE \
 "
 
+WHENCE_CHKSUM = "d3eb82686904888f8bbbe8d865371404"
 LIC_FILES_CHKSUM = "file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc 
\
 
file://LICENCE.adsp_sst;md5=615c45b91a5a4a9fe046d6ab9a2df728 \
 file://LICENCE.agere;md5=af0133de6b4a9b2522defd5f188afd31 \
@@ -132,7 +133,7 @@ LIC_FILES_CHKSUM = 
"file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc \
 file://LICENCE.xc4000;md5=0ff51d2dc49fce04814c9155081092f0 
\
 file://LICENCE.xc5000;md5=1e170c13175323c32c7f4d0998d53f66 
\
 
file://LICENCE.xc5000c;md5=12b02efa3049db65d524aeb418dd87ca \
-file://WHENCE;md5=d3eb82686904888f8bbbe8d865371404 \
+file://WHENCE;md5=${WHENCE_CHKSUM} \
 "
 
 # These are not common licenses, set NO_GENERIC_LICENSE for them
@@ -208,6 +209,11 @@ SRC_URI = "\
   file://0001-Makefile-replace-mkdir-by-install.patch \
 "
 
+BBCLASSEXTEND = "devupstream:target"
+SRC_URI:class-devupstream = 
"git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git;protocol=https;branch=main"
+# Pin this to the 20220509 release, override this in local.conf
+SRCREV:class-devupstream ?= "b19cbdca78ab2adfd210c91be15a22568e8b8cae"
+
 SRC_URI[sha256sum] = 
"376e0b3d7b4f8aaa2abf7f5ab74803dcf14b06b94e3d841b1467cd9a2848255e"
 
 inherit allarch
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166374): 
https://lists.openembedded.org/g/openembedded-core/message/166374
Mute This Topic: https://lists.openembedded.org/mt/91472634/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

2022-06-01 Thread Luca Ceresoli via lists.openembedded.org

On Wed, 2022-06-01 at 12:52 +0200, Peter Bergin wrote:
> On 2022-06-01 11:43, Alexander Kanavin wrote:
> > I'm not sure what the dilemma is, inspecting the repo shows that
> > there's a standard 0.2.0 tag pointing to a commit in the master
> > branch. You can look at pretty much any other recipe fetching from
> > git.
> > https://github.com/Avnu/libavtp/tags
> > 
> Agree.

I also fully agree. Sorry for my confusion in this regard.

> My suggestion for solution is 'SRC_URI=-...;branch=master...' + 
> 'SRCREV=' and rename recipe to libavtp_0.2.0.bb. I 
> don't know if that is against any style guide or rules?
> 
> And also fine with a move to meta-openembedded.

Sure, let me do that. Thanks!

> /Peter

Cheers

Marcel

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166375): 
https://lists.openembedded.org/g/openembedded-core/message/166375
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell][PATCH v1] libxml2: Fix CVE-2022-29824 for libxml2

2022-06-01 Thread Riyaz Ahmed Khan

From: Riyaz 

Add patch for CVE issue: CVE-2022-29824

CVE-2022-29824
Link: 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/2554a2408e09f13652049e5ffb0d26196b02ebab]
Dependent patch: 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/b07251215ef48c70c6e56f7351406c47cfca4d5b]

Signed-off-by: Riyaz 
---
 .../libxml2/CVE-2022-29824-dependent.patch|  53 +++
 .../libxml/libxml2/CVE-2022-29824.patch   | 348 ++
 meta/recipes-core/libxml/libxml2_2.9.10.bb|   2 +
 3 files changed, 403 insertions(+)
 create mode 100644 
meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch
 create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch

diff --git a/meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch 
b/meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch
new file mode 100644
index 00..63d613cc21
--- /dev/null
+++ b/meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch
@@ -0,0 +1,53 @@
+From b07251215ef48c70c6e56f7351406c47cfca4d5b Mon Sep 17 00:00:00 2001
+From: Nick Wellnhofer 
+Date: Fri, 10 Jan 2020 15:55:07 +0100
+Subject: [PATCH] Fix integer overflow in xmlBufferResize
+
+Found by OSS-Fuzz.
+
+CVE: CVE-2022-29824
+
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/b07251215ef48c70c6e56f7351406c47cfca4d5b]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ tree.c | 9 +++--
+ 1 file changed, 7 insertions(+), 2 deletions(-)
+
+diff --git a/tree.c b/tree.c
+index 0d7fc98c..f43f6de1 100644
+--- a/tree.c
 b/tree.c
+@@ -7424,12 +7424,17 @@ xmlBufferResize(xmlBufferPtr buf, unsigned int size)
+ if (size < buf->size)
+ return 1;
+ 
++if (size > UINT_MAX - 10) {
++xmlTreeErrMemory("growing buffer");
++return 0;
++}
++
+ /* figure out new size */
+ switch (buf->alloc){
+   case XML_BUFFER_ALLOC_IO:
+   case XML_BUFFER_ALLOC_DOUBLEIT:
+   /*take care of empty case*/
+-  newSize = (buf->size ? buf->size*2 : size + 10);
++  newSize = (buf->size ? buf->size : size + 10);
+   while (size > newSize) {
+   if (newSize > UINT_MAX / 2) {
+   xmlTreeErrMemory("growing buffer");
+@@ -7445,7 +7450,7 @@ xmlBufferResize(xmlBufferPtr buf, unsigned int size)
+ if (buf->use < BASE_BUFFER_SIZE)
+ newSize = size;
+ else {
+-newSize = buf->size * 2;
++newSize = buf->size;
+ while (size > newSize) {
+ if (newSize > UINT_MAX / 2) {
+ xmlTreeErrMemory("growing buffer");
+-- 
+GitLab
+
+
diff --git a/meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch 
b/meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch
new file mode 100644
index 00..ad7b87dbc6
--- /dev/null
+++ b/meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch
@@ -0,0 +1,348 @@
+From 2554a2408e09f13652049e5ffb0d26196b02ebab Mon Sep 17 00:00:00 2001
+From: Nick Wellnhofer 
+Date: Tue, 8 Mar 2022 20:10:02 +0100
+Subject: [PATCH] [CVE-2022-29824] Fix integer overflows in xmlBuf and
+ xmlBuffer
+
+In several places, the code handling string buffers didn't check for
+integer overflow or used wrong types for buffer sizes. This could
+result in out-of-bounds writes or other memory errors when working on
+large, multi-gigabyte buffers.
+
+Thanks to Felix Wilhelm for the report.
+
+CVE: CVE-2022-29824
+
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/2554a2408e09f13652049e5ffb0d26196b02ebab]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ buf.c  | 86 +++---
+ tree.c | 72 ++--
+ 2 files changed, 61 insertions(+), 97 deletions(-)
+
+diff --git a/buf.c b/buf.c
+index 24368d37..40a5ee06 100644
+--- a/buf.c
 b/buf.c
+@@ -30,6 +30,10 @@
+ #include  /* for XML_MAX_TEXT_LENGTH */
+ #include "buf.h"
+ 
++#ifndef SIZE_MAX
++#define SIZE_MAX ((size_t) -1)
++#endif
++
+ #define WITH_BUFFER_COMPAT
+ 
+ /**
+@@ -156,6 +160,8 @@ xmlBufPtr
+ xmlBufCreateSize(size_t size) {
+ xmlBufPtr ret;
+ 
++if (size == SIZE_MAX)
++return(NULL);
+ ret = (xmlBufPtr) xmlMalloc(sizeof(xmlBuf));
+ if (ret == NULL) {
+   xmlBufMemoryError(NULL, "creating buffer");
+@@ -166,8 +172,8 @@ xmlBufCreateSize(size_t size) {
+ ret->error = 0;
+ ret->buffer = NULL;
+ ret->alloc = xmlBufferAllocScheme;
+-ret->size = (size ? size+2 : 0); /* +1 for ending null */
+-ret->compat_size = (int) ret->size;
++ret->size = (size ? size + 1 : 0); /* +1 for ending null */
++ret->compat_size = (ret->size > INT_MAX ? INT_MAX : ret->size);
+ if (ret->size){
+ ret->content = (xmlChar *) xmlMallocAtomic(ret->size * 
sizeof(xmlChar));
+ if (ret->content == NULL) {
+@@ -442,23 +448,17 @@ xmlBufGrowInternal(xmlBufPtr buf, size_t len) {
+ CHECK_COMPAT(buf)
+ 
+ if (buf->a

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

Hi Marcel,

On Tue, 31 May 2022 23:32:06 +0200
"Marcel Ziswiler"  wrote:

> From: Peter Bergin 
> 
> In order to enable configuration option aaf (AVTP Audio Format)
> used for AVB the library libavtp is a dependency but no recipe for
> this library was present. aaf support for alsa-plugins was
> introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> 
> Signed-off-by: Peter Bergin 
> Signed-off-by: Marcel Ziswiler 

This patch is failing on musl builds:

https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5308/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5294/steps/12/logs/stdio

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166377): 
https://lists.openembedded.org/g/openembedded-core/message/166377
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [dunfell][PATCH] e2fsprogs: CVE-2022-1304 out-of-bounds read/write via crafted filesystem

On Tue, May 31, 2022 at 7:34 PM Hitendra Prajapati
 wrote:
>
> Source: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
> MR: 117430
> Type: Security Fix
> Disposition: Backport from 
> https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?h=maint&id=ab51d587bb9b229b1fade1afd02e1574c1ba5c76
> ChangeID: e6db00c6e8375a2e869fd2e4ead61ca9149eb8fa
> Description:
>   CVE-2022-1304 e2fsprogs: out-of-bounds read/write via crafted 
> filesystem.
>
> Signed-off-by: Hitendra Prajapati 
> ---
>  .../e2fsprogs/e2fsprogs/CVE-2022-1304.patch   | 60 +++
>  .../e2fsprogs/e2fsprogs_1.45.7.bb |  1 +
>  2 files changed, 61 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/e2fsprogs/e2fsprogs/CVE-2022-1304.patch
>
> diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs/CVE-2022-1304.patch 
> b/meta/recipes-devtools/e2fsprogs/e2fsprogs/CVE-2022-1304.patch
> new file mode 100644
> index 00..74737abda7
> --- /dev/null
> +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs/CVE-2022-1304.patch
> @@ -0,0 +1,60 @@
> +From a66071ed6a0d1fa666d22dcb78fa6fcb3bf22df3 Mon Sep 17 00:00:00 2001
> +From: Hitendra Prajapati 
> +Date: Fri, 27 May 2022 14:01:50 +0530
> +Subject: [PATCH] CVE-2022-1304
> +
> +Upstream-Status: Backport from 
> https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?h=maint&id=ab51d587bb9b229b1fade1afd02e1574c1ba5c76

The standard format for upstream status would be:

Upstream-Status: Backport
[https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?h=maint&id=ab51d587bb9b229b1fade1afd02e1574c1ba5c76]

Also needs to have the CVE: and Signed-off-by: added, e.g.

CVE: CVE-2022-1304
Signed-off-by: Hitendra Prajapati 

Thanks so much for helping with CVEs!

Steve

> +
> +libext2fs: add sanity check to extent manipulation
> +It is possible to have a corrupted extent tree in such a way that a leaf
> +node contains zero extents in it. Currently if that happens and we try
> +to traverse the tree we can end up accessing wrong data, or possibly
> +even uninitialized memory. Make sure we don't do that.
> +
> +Additionally make sure that we have a sane number of bytes passed to
> +memmove() in ext2fs_extent_delete().
> +
> +Note that e2fsck is currently unable to spot and fix such corruption in
> +pass1.
> +
> +Signed-off-by: Lukas Czerner 
> +Reported-by: Nils Bars 
> +Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=2068113
> +Addresses: CVE-2022-1304
> +Addresses-Debian-Bug: #1010263
> +Signed-off-by: Theodore Ts'o 
> +
> +Signed-off-by: Hitendra Prajapati 
> +---
> + lib/ext2fs/extent.c | 8 
> + 1 file changed, 8 insertions(+)
> +
> +diff --git a/lib/ext2fs/extent.c b/lib/ext2fs/extent.c
> +index ac3dbfec9..a1b1905cd 100644
> +--- a/lib/ext2fs/extent.c
>  b/lib/ext2fs/extent.c
> +@@ -495,6 +495,10 @@ retry:
> +   ext2fs_le16_to_cpu(eh->eh_entries);
> +   newpath->max_entries = ext2fs_le16_to_cpu(eh->eh_max);
> +
> ++  /* Make sure there is at least one extent present */
> ++  if (newpath->left <= 0)
> ++  return EXT2_ET_EXTENT_NO_DOWN;
> ++
> +   if (path->left > 0) {
> +   ix++;
> +   newpath->end_blk = ext2fs_le32_to_cpu(ix->ei_block);
> +@@ -1630,6 +1634,10 @@ errcode_t ext2fs_extent_delete(ext2_extent_handle_t 
> handle, int flags)
> +
> +   cp = path->curr;
> +
> ++  /* Sanity check before memmove() */
> ++  if (path->left < 0)
> ++  return EXT2_ET_EXTENT_LEAF_BAD;
> ++
> +   if (path->left) {
> +   memmove(cp, cp + sizeof(struct ext3_extent_idx),
> +   path->left * sizeof(struct ext3_extent_idx));
> +--
> +2.25.1
> +
> diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.45.7.bb 
> b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.45.7.bb
> index 3bc530e02b..3e6faf4cb8 100644
> --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.45.7.bb
> +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.45.7.bb
> @@ -6,6 +6,7 @@ SRC_URI += "file://remove.ldconfig.call.patch \
> file://mkdir_p.patch \
> file://0001-configure.ac-correct-AM_GNU_GETTEXT.patch \
> 
> file://0001-intl-do-not-try-to-use-gettext-defines-that-no-longe.patch \
> +   file://CVE-2022-1304.patch \
> "
>
>  SRC_URI_append_class-native = " 
> file://e2fsprogs-fix-missing-check-for-permission-denied.patch \
> --
> 2.25.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166378): 
https://lists.openembedded.org/g/openembedded-core/message/166378
Mute This Topic: https://lists.openembedded.org/mt/91469563/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [dunfell][PATCH] pcre2: CVE-2022-1587 Out-of-bounds read

2022-06-01 Thread Luca Ceresoli via lists.openembedded.org

On Tue, May 31, 2022 at 7:54 PM Hitendra Prajapati
 wrote:
>
> Source:  https://github.com/PCRE2Project/pcre2
> MR: 118031
> Type: Security Fix
> Disposition: Backport from 
> https://github.com/PCRE2Project/pcre2/commit/03654e751e7f0700693526b67dfcadda6b42c9d0
> ChangeID: 8d5e1357918894374e3379daf1d1a6873c7b9bf3
> Description:
>
> CVE-2022-1587  pcre2: Out-of-bounds read in get_recurse_data_length in 
> pcre2_jit_compile.c.
>
> Signed-off-by: Hitendra Prajapati 
> ---
>  .../libpcre/libpcre2/CVE-2022-1587.patch  | 659 ++
>  .../recipes-support/libpcre/libpcre2_10.34.bb |   1 +
>  2 files changed, 660 insertions(+)
>  create mode 100644 meta/recipes-support/libpcre/libpcre2/CVE-2022-1587.patch
>
> diff --git a/meta/recipes-support/libpcre/libpcre2/CVE-2022-1587.patch 
> b/meta/recipes-support/libpcre/libpcre2/CVE-2022-1587.patch
> new file mode 100644
> index 00..1c3f5f1d3d
> --- /dev/null
> +++ b/meta/recipes-support/libpcre/libpcre2/CVE-2022-1587.patch
> @@ -0,0 +1,659 @@
> +From aa5aac0d209e3debf80fc2db924d9401fc50454b Mon Sep 17 00:00:00 2001
> +From: Hitendra Prajapati 
> +Date: Mon, 23 May 2022 14:11:11 +0530
> +Subject: [PATCH] CVE-2022-1587
> +
> +Upstream-Status: Backport from 
> https://github.com/PCRE2Project/pcre2/commit/03654e751e7f0700693526b67dfcadda6b42c9d0

Same comments as your e2fsprogs patch - Upstream-Status format,
missing CVE: and Signed-off-by: tags.

And once again thanks so much for helping with CVE fixes!

Steve

> +
> +Signed-off-by: Hitendra Prajapati 
> +---
> + ChangeLog   |   3 +
> + src/pcre2_jit_compile.c | 290 ++--
> + src/pcre2_jit_test.c|   1 +
> + 3 files changed, 194 insertions(+), 100 deletions(-)
> +
> +diff --git a/ChangeLog b/ChangeLog
> +index b5d72dc..de82de9 100644
> +--- a/ChangeLog
>  b/ChangeLog
> +@@ -4,6 +4,9 @@ Change Log for PCRE2
> + 23. Fixed a unicode properrty matching issue in JIT. The character was not
> + fully read in caseless matching.
> +
> ++24. Fixed an issue affecting recursions in JIT caused by duplicated data
> ++transfers.
> ++
> +
> + Version 10.34 21-November-2019
> + --
> +diff --git a/src/pcre2_jit_compile.c b/src/pcre2_jit_compile.c
> +index 5d43865..493c96d 100644
> +--- a/src/pcre2_jit_compile.c
>  b/src/pcre2_jit_compile.c
> +@@ -407,6 +407,9 @@ typedef struct compiler_common {
> +   /* Locals used by fast fail optimization. */
> +   sljit_s32 fast_fail_start_ptr;
> +   sljit_s32 fast_fail_end_ptr;
> ++  /* Variables used by recursive call generator. */
> ++  sljit_s32 recurse_bitset_size;
> ++  uint8_t *recurse_bitset;
> +
> +   /* Flipped and lower case tables. */
> +   const sljit_u8 *fcc;
> +@@ -2109,19 +2112,39 @@ for (i = 0; i < RECURSE_TMP_REG_COUNT; i++)
> +
> + #undef RECURSE_TMP_REG_COUNT
> +
> ++static BOOL recurse_check_bit(compiler_common *common, sljit_sw bit_index)
> ++{
> ++uint8_t *byte;
> ++uint8_t mask;
> ++
> ++SLJIT_ASSERT((bit_index & (sizeof(sljit_sw) - 1)) == 0);
> ++
> ++bit_index >>= SLJIT_WORD_SHIFT;
> ++
> ++mask = 1 << (bit_index & 0x7);
> ++byte = common->recurse_bitset + (bit_index >> 3);
> ++
> ++if (*byte & mask)
> ++  return FALSE;
> ++
> ++*byte |= mask;
> ++return TRUE;
> ++}
> ++
> + static int get_recurse_data_length(compiler_common *common, PCRE2_SPTR cc, 
> PCRE2_SPTR ccend,
> +   BOOL *needs_control_head, BOOL *has_quit, BOOL *has_accept)
> + {
> + int length = 1;
> +-int size;
> ++int size, offset;
> + PCRE2_SPTR alternative;
> + BOOL quit_found = FALSE;
> + BOOL accept_found = FALSE;
> + BOOL setsom_found = FALSE;
> + BOOL setmark_found = FALSE;
> +-BOOL capture_last_found = FALSE;
> + BOOL control_head_found = FALSE;
> +
> ++memset(common->recurse_bitset, 0, common->recurse_bitset_size);
> ++
> + #if defined DEBUG_FORCE_CONTROL_HEAD && DEBUG_FORCE_CONTROL_HEAD
> + SLJIT_ASSERT(common->control_head_ptr != 0);
> + control_head_found = TRUE;
> +@@ -2144,15 +2167,17 @@ while (cc < ccend)
> +   setsom_found = TRUE;
> + if (common->mark_ptr != 0)
> +   setmark_found = TRUE;
> +-if (common->capture_last_ptr != 0)
> +-  capture_last_found = TRUE;
> ++if (common->capture_last_ptr != 0 && recurse_check_bit(common, 
> common->capture_last_ptr))
> ++  length++;
> + cc += 1 + LINK_SIZE;
> + break;
> +
> + case OP_KET:
> +-if (PRIVATE_DATA(cc) != 0)
> ++offset = PRIVATE_DATA(cc);
> ++if (offset != 0)
> +   {
> +-  length++;
> ++  if (recurse_check_bit(common, offset))
> ++length++;
> +   SLJIT_ASSERT(PRIVATE_DATA(cc + 1) != 0);
> +   cc += PRIVATE_DATA(cc + 1);
> +   }
> +@@ -2169,39 +2194,55 @@ while (cc < ccend)
> + case OP_SBRA:
> + case OP_SBRAPOS:
> + case OP_SCOND:
> +-length++;
> + SLJIT_ASSERT(PRIVATE_DATA(cc) != 0);
> ++if (recurse_check_bit(common, PRIVATE_DATA(cc)))
> ++  length++;
> + cc += 1 + LINK_SIZE;
> + break;
> +
> + case OP_CBRA:
> + case OP_

Re: [oe-core][PATCH 1/4] xorg-lib-common: allow to build for wayland

Hi Markus,

On Tue, 31 May 2022 21:06:17 +0200
"Markus Volk"  wrote:

> Signed-off-by: Markus Volk 

I applied patches 1 to 3 of this series to my testing branch and got
these failures:

stdio: ERROR: Nothing PROVIDES 'font-util' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libfontenc_1.1.4.bb
 DEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont2' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont2_2.0.5.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont2-dev' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont2_2.0.5.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libfontenc' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libfontenc_1.1.4.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libfontenc-dev' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libfontenc_1.1.4.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont-dev' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont_1.5.4.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont_1.5.4.bb
 RDEPENDS on or otherwise requires it)

See the full logs:

https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/12/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/15/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/15/logs/stdio

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166380): 
https://lists.openembedded.org/g/openembedded-core/message/166380
Mute This Topic: https://lists.openembedded.org/mt/91458797/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core][dunfell][PATCH 1/2] libxslt: update to v1.1.35

2022-06-01 Thread Luca Ceresoli via lists.openembedded.org

On Wed, Jun 1, 2022 at 12:53 AM omkar  wrote:
>
> From: Markus Volk 
>
> Security
>
> [CVE-2021-30560] Fix use-after-free in xsltApplyTemplates
> Fix memory leak in xsltDocumentElem (David King)
> Fix memory leak in xsltCompileIdKeyPattern (David King)
> Fix double-free with stylesheets containing entity nodes
>
> Fixed regressions
>
> Fix performance regression with predicates in patterns
> Fix regression in xsltComputeSortResult
>
> Bug fixes
>
> Fix conflict resolution for templates with same priority
> Fix xsl:number generating invalid UTF-8
> Support attribute value templates in xsl:sort lang attributes
> Don't pass first xsl:sort in xsl:apply-templates twice
> Fix quadratic runtime with text and xsl:message
>
> Don't allow empty EXSLT durations
>
> Improvements
> Add xsltproc --huge Argument via libxml XML_PARSE_HUGE (William N. Braswell, 
> Jr.)
>
> Tests, code quality, fuzzing
>
> Remove .travis.yml
> Fix some misleading indentation (David King)
> Use actual types for templates in struct _xsltStylesheet
> Add CI for CMake on MSVC (Markus Rickert)
> Check for null pointer before calling freelocale
> Add CI test for Python 3
> Don't set maxDepth in XPath contexts
> Transfer XPath limits to XPtr context
> Stop using maxParserDepth XPath limit
> Make long-to-double cast explicit in date.c
> Disable LeakSanitizer
> Run clang CI tests with -Wimplicit-int-conversion
> Fix implicit-int-conversion warning in exslt/crypto.c
> Fix clang -Wimplicit-int-conversion warning (David Kilzer)
> Fix clang -Wconditional-uninitialized warning in libxslt/numbers.c (David 
> Kilzer)
> Fix -Wshadow warnings in libexslt/dynamic.c (David Kilzer)
> Also search parent dir for source XML when fuzzing
>
> Build system, portability
>
> Add CMake build files (Markus Rickert)
> Initial support for Python 3 (Suleyman Poyraz)
> Call ANSI versions of WinAPI functions explicitly
> Remove redundant flags from pkg-config files
> Suppress automake warning in tests/XSLTMark
> Fix linking libexslt dynamic library when using MinGW (Vadim Zeitlin)
> Added platform specific path separators (Dmitriy Korovkin)
> win32: allow passing *FLAGS on command line
> Fix export of xsltExtMarker on Windows (David Kilzer)
> Fix redundant includes already in libexslt.h (David Kilzer)
> Minor fixes to configure.js
> Fix variable syntax in Python configuration
> Add new EXSLT string tests to EXTRA_DIST
> Fix xml2-config check in configure script
> win32: Add configuration for profiler (Chun-wei Fan)
> Check whether 'xml2-config --dynamic' is supported
>
> Documentation
>
> Add Makefile rule to regenerate xsltproc.html
> Update links
> Remove MAINTAINERS
> Upload documentation to GitLab Pages
> Add documentation in devhelp format
> Add --enable-rebuild-docs configure option
> Fix libexslt header summaries
> Fix validity of tutorial XML (David King)
> Use DocBook URL for tutorial DTD (David King)
> Update libxslt.doap
> Add missing options to xsltproc man page

This seems to be much more than a bug fix/security release, so I'm not
sure it is suitable for an LTS branch.

If the intent was to fix CVE-2021-30560, I'd prefer to see a patch
adding the relevant commits for just that fix.

Thanks for helping out with CVEs, I appreciate it!

Steve

> (From OE-Core rev: 6b5b1486bbd381b2b657645e91a1712332ddcb94)
>
> Signed-off-by: Markus Volk 
> Signed-off-by: Richard Purdie 
> (cherry picked from commit daa312851681c55d81391b37a30a518f3e74e540)
>
> Signed-off-by: Omkar Patil 
> ---
>  .../libxslt/{libxslt_1.1.34.bb => libxslt_1.1.35.bb}| 6 ++
>  1 file changed, 2 insertions(+), 4 deletions(-)
>  rename meta/recipes-support/libxslt/{libxslt_1.1.34.bb => libxslt_1.1.35.bb} 
> (89%)
>
> diff --git a/meta/recipes-support/libxslt/libxslt_1.1.34.bb 
> b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> similarity index 89%
> rename from meta/recipes-support/libxslt/libxslt_1.1.34.bb
> rename to meta/recipes-support/libxslt/libxslt_1.1.35.bb
> index 63cce6fe06..0f25043743 100644
> --- a/meta/recipes-support/libxslt/libxslt_1.1.34.bb
> +++ b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> @@ -13,11 +13,9 @@ LIC_FILES_CHKSUM = 
> "file://Copyright;md5=0cd9a07afbeb24026c9b03aecfeba458"
>  SECTION = "libs"
>  DEPENDS = "libxml2"
>
> -SRC_URI = "http://xmlsoft.org/sources/libxslt-${PV}.tar.gz \
> -  "
> +SRC_URI = 
> "https://download.gnome.org/sources/libxslt/1.1/libxslt-${PV}.tar.xz";
>
> -SRC_URI[md5sum] = "db8765c8d076f1b6caafd9f2542a304a"
> -SRC_URI[sha256sum] = 
> "98b1bd46d6792925ad2dfe9a87452ea2adebf69dcb9919ffd55bf926a7f93f7f"
> +SRC_URI[sha256sum] = 
> "8247f33e9a872c6ac859aa45018bc4c4d00b97e2feac9eebc10c93ce1f34dd79"
>
>  UPSTREAM_CHECK_REGEX = "libxslt-(?P\d+(\.\d+)+)\.tar"
>
> --
> 2.17.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166381): 
https://lists.openembedded.org/g/openembedded-core/message/166381
Mute This Topic: https://lists.openembedded.org/mt/91472461/21656
Group Owner: opene

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

Hi Marcel,

On Wed, 1 Jun 2022 15:48:15 +0200
"Luca Ceresoli via lists.openembedded.org"
 wrote:

> Hi Marcel,
> 
> On Tue, 31 May 2022 23:32:06 +0200
> "Marcel Ziswiler"  wrote:
> 
> > From: Peter Bergin 
> > 
> > In order to enable configuration option aaf (AVTP Audio Format)
> > used for AVB the library libavtp is a dependency but no recipe for
> > this library was present. aaf support for alsa-plugins was
> > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > 
> > Signed-off-by: Peter Bergin 
> > Signed-off-by: Marcel Ziswiler   
> 
> This patch is failing on musl builds:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5308/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5294/steps/12/logs/stdio

This patch also triggers selftest errors because the new recipe has no
maintainer:

https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3657/steps/15/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/3661/steps/14/logs/stdio

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166382): 
https://lists.openembedded.org/g/openembedded-core/message/166382
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core][dunfell][PATCH 2/2] libxslt: Mark CVE-2022-29824 as not applying

On Wed, Jun 1, 2022 at 12:53 AM omkar  wrote:
>
> From: Richard Purdie 
>
> We have libxml2 2.9.14 and we don't link statically against libxml2 anyway
> so the CVE doesn't apply to libxslt.

dunfell libxml2 is version 2.9.10!

Steve

> (From OE-Core rev: c6315d8a2a1429a0fb7563b1d6352ceee7bc222c)
>
> Signed-off-by: Richard Purdie 
> (cherry picked from commit ad63694e6df4f284879f7220962a821f97928eb0)
> Signed-off-by: Omkar Patil 
> ---
>  meta/recipes-support/libxslt/libxslt_1.1.35.bb | 4 
>  1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-support/libxslt/libxslt_1.1.35.bb 
> b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> index 0f25043743..47a38deb13 100644
> --- a/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> +++ b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> @@ -19,6 +19,10 @@ SRC_URI[sha256sum] = 
> "8247f33e9a872c6ac859aa45018bc4c4d00b97e2feac9eebc10c93ce1f
>
>  UPSTREAM_CHECK_REGEX = "libxslt-(?P\d+(\.\d+)+)\.tar"
>
> +# We have libxml2 2.9.14 and we don't link statically with it anyway
> +# so this isn't an issue.
> +CVE_CHECK_WHITELIST += "CVE-2022-29824"
> +
>  S = "${WORKDIR}/libxslt-${PV}"
>
>  BINCONFIG = "${bindir}/xslt-config"
> --
> 2.17.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166383): 
https://lists.openembedded.org/g/openembedded-core/message/166383
Mute This Topic: https://lists.openembedded.org/mt/91472462/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[oe-core][PATCH] xorg-font-common.inc: allow to build for wayland

2022-06-01 Thread Markus Volk

---
 meta/recipes-graphics/xorg-font/xorg-font-common.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/xorg-font/xorg-font-common.inc 
b/meta/recipes-graphics/xorg-font/xorg-font-common.inc
index 2df23efed4..f552bb0076 100644
--- a/meta/recipes-graphics/xorg-font/xorg-font-common.inc
+++ b/meta/recipes-graphics/xorg-font/xorg-font-common.inc
@@ -15,7 +15,7 @@ S = "${WORKDIR}/${XORG_PN}-${PV}"
 inherit autotools pkgconfig features_check
 
 # The mkfontscale-native requires x11 in DISTRO_FEATURES
-REQUIRED_DISTRO_FEATURES = "x11"
+ANY_OF_DISTRO_FEATURES = "x11 wayland"
 
 EXTRA_OEMAKE += "FCCACHE=/bin/true 
UTIL_DIR=${STAGING_DIR_TARGET}\$\(MAPFILES_PATH\)"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166384): 
https://lists.openembedded.org/g/openembedded-core/message/166384
Mute This Topic: https://lists.openembedded.org/mt/91478419/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH 1/4] xorg-lib-common: allow to build for wayland

2022-06-01 Thread Markus Volk


Hi Luca,

i've sent a patch that should hopefully fix your issue

Am 01.06.22 um 17:00 schrieb Luca Ceresoli:

Hi Markus,

On Tue, 31 May 2022 21:06:17 +0200
"Markus Volk"  wrote:


Signed-off-by: Markus Volk 

I applied patches 1 to 3 of this series to my testing branch and got
these failures:

stdio: ERROR: Nothing PROVIDES 'font-util' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libfontenc_1.1.4.bb
 DEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont2' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont2_2.0.5.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont2-dev' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont2_2.0.5.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libfontenc' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libfontenc_1.1.4.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libfontenc-dev' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libfontenc_1.1.4.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont-dev' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont_1.5.4.bb
 RDEPENDS on or otherwise requires it)
stdio: ERROR: Nothing RPROVIDES 'libxfont' (but 
/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-graphics/xorg-lib/libxfont_1.5.4.bb
 RDEPENDS on or otherwise requires it)

See the full logs:

https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/12/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/15/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5304/steps/15/logs/stdio


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166385): 
https://lists.openembedded.org/g/openembedded-core/message/166385
Mute This Topic: https://lists.openembedded.org/mt/91458797/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

On Wed, 2022-06-01 at 15:48 +0200, Luca Ceresoli wrote:
> Hi Marcel,
> 
> On Tue, 31 May 2022 23:32:06 +0200
> "Marcel Ziswiler"  wrote:
> 
> > From: Peter Bergin 
> > 
> > In order to enable configuration option aaf (AVTP Audio Format)
> > used for AVB the library libavtp is a dependency but no recipe for
> > this library was present. aaf support for alsa-plugins was
> > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > 
> > Signed-off-by: Peter Bergin 
> > Signed-off-by: Marcel Ziswiler 
> 
> This patch is failing on musl builds:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5308/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5294/steps/12/logs/stdio

To be honest, I don't know nothing about musl and will need to get familiar 
with that topic first. If anybody
has some suggestions that would be highly appreciated. Thanks!

Cheers

Marcel

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166386): 
https://lists.openembedded.org/g/openembedded-core/message/166386
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core][dunfell][PATCH 2/2] libxslt: Mark CVE-2022-29824 as not applying

On Wed, Jun 1, 2022 at 5:09 AM Steve Sakoman via
lists.openembedded.org 
wrote:
>
> On Wed, Jun 1, 2022 at 12:53 AM omkar  wrote:
> >
> > From: Richard Purdie 
> >
> > We have libxml2 2.9.14 and we don't link statically against libxml2 anyway
> > so the CVE doesn't apply to libxslt.
>
> dunfell libxml2 is version 2.9.10!

I just noticed that we have a libxml2 patch submitted to fix CVE-2022-29824:

https://lists.openembedded.org/g/openembedded-core/message/166376

So you can adjust this patch to reflect this and resubmit it.

Steve

>
> Steve
>
> > (From OE-Core rev: c6315d8a2a1429a0fb7563b1d6352ceee7bc222c)
> >
> > Signed-off-by: Richard Purdie 
> > (cherry picked from commit ad63694e6df4f284879f7220962a821f97928eb0)
> > Signed-off-by: Omkar Patil 
> > ---
> >  meta/recipes-support/libxslt/libxslt_1.1.35.bb | 4 
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/meta/recipes-support/libxslt/libxslt_1.1.35.bb 
> > b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> > index 0f25043743..47a38deb13 100644
> > --- a/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> > +++ b/meta/recipes-support/libxslt/libxslt_1.1.35.bb
> > @@ -19,6 +19,10 @@ SRC_URI[sha256sum] = 
> > "8247f33e9a872c6ac859aa45018bc4c4d00b97e2feac9eebc10c93ce1f
> >
> >  UPSTREAM_CHECK_REGEX = "libxslt-(?P\d+(\.\d+)+)\.tar"
> >
> > +# We have libxml2 2.9.14 and we don't link statically with it anyway
> > +# so this isn't an issue.
> > +CVE_CHECK_WHITELIST += "CVE-2022-29824"
> > +
> >  S = "${WORKDIR}/libxslt-${PV}"
> >
> >  BINCONFIG = "${bindir}/xslt-config"
> > --
> > 2.17.1
> >
> >
> >
> >
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166387): 
https://lists.openembedded.org/g/openembedded-core/message/166387
Mute This Topic: https://lists.openembedded.org/mt/91472462/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

On Wed, 2022-06-01 at 17:05 +0200, Luca Ceresoli wrote:
> Hi Marcel,
> 
> On Wed, 1 Jun 2022 15:48:15 +0200
> "Luca Ceresoli via lists.openembedded.org"
>  wrote:
> 
> > Hi Marcel,
> > 
> > On Tue, 31 May 2022 23:32:06 +0200
> > "Marcel Ziswiler"  wrote:
> > 
> > > From: Peter Bergin 
> > > 
> > > In order to enable configuration option aaf (AVTP Audio Format)
> > > used for AVB the library libavtp is a dependency but no recipe for
> > > this library was present. aaf support for alsa-plugins was
> > > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > > 
> > > Signed-off-by: Peter Bergin 
> > > Signed-off-by: Marcel Ziswiler   
> > 
> > This patch is failing on musl builds:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5308/steps/11/logs/stdio
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5294/steps/12/logs/stdio
> 
> This patch also triggers selftest errors because the new recipe has no
> maintainer:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3657/steps/15/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/3661/steps/14/logs/stdio

Okay, thanks. Sorry, I missed this being a mandatory requirement now. I guess I 
can add me and/or Peter as
maintainer. No biggy really.

Cheers

Marcel

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166388): 
https://lists.openembedded.org/g/openembedded-core/message/166388
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH 1/2] gcc: Upgrade to 11.3 release

On Wed, Jun 1, 2022 at 12:10 AM Martin Jansa  wrote:
>
> As discussed on IRC yesterday I've tried to reproduce this failure locally 
> and it works fine with poky master cee443ae75f (last commit in master before 
> the upgrade to 12.1)
> 2022-06-01 09:46:37,051 - oe-selftest - INFO - RESULTS - 
> reproducible.ReproducibleTests.test_reproducible_builds: PASSED (6429.19s)
> and now it passed with kirkstone as well:
>
> poky $ git cherry-pick 44a36caa7c2
> Auto-merging meta/conf/distro/include/maintainers.inc
> [jansa/kirkstone-gcc-11.3 5c6e280eed5] gcc: Upgrade to 11.3 release
> ...
> poky $ oe-selftest -r reproducible 2>&1 | tee 
> log.oe-selftest.reproducible.kirkstone
> 2022-06-01 09:51:31,653 - oe-selftest - INFO - Changing cwd to 
> /OE/build/poky/build
> 2022-06-01 09:51:31,653 - oe-selftest - INFO - Adding layer libraries:
> 2022-06-01 09:51:31,653 - oe-selftest - INFO -  /OE/build/poky/meta-poky/lib
> 2022-06-01 09:51:31,653 - oe-selftest - INFO -  /OE/build/poky/meta/lib
> 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> /OE/build/poky/meta-yocto-bsp/lib
> 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> /OE/build/poky/meta-selftest/lib
> 2022-06-01 09:51:31,655 - oe-selftest - INFO - Running bitbake -e to test the 
> configuration is valid/parsable
> hint: Using 'master' as the name for the initial branch. This default branch 
> name
> hint: is subject to change. To configure the initial branch name to use in all
> hint: of your new repositories, which will suppress this warning, call:
> hint:
> hint:   git config --global init.defaultBranch 
> hint:
> hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
> hint: 'development'. The just-created branch can be renamed via this command:
> hint:
> hint:   git branch -m 
> 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include selftest.inc" 
> in /OE/build/poky/build-st/conf/local.conf
> 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include bblayers.inc" 
> in bblayers.conf
> 2022-06-01 09:51:37,092 - oe-selftest - INFO - test_diffoscope 
> (reproducible.DiffoscopeTests)
> 2022-06-01 10:08:42,982 - oe-selftest - INFO -  ... ok
> 2022-06-01 10:08:42,983 - oe-selftest - INFO - test_reproducible_builds 
> (reproducible.ReproducibleTests)
> 2022-06-01 10:09:56,114 - oe-selftest - INFO - Building reproducibleA (sstate 
> allowed)...
> ^Ap2022-06-01 11:11:09,785 - oe-selftest - INFO - Building reproducibleB 
> (sstate NOT allowed)...
> 2022-06-01 11:55:00,507 - oe-selftest - INFO - Checking deb packages for 
> differences...
> 2022-06-01 11:55:00,946 - oe-selftest - INFO - Reproducibility summary for 
> deb: same=139 different=0 different_excluded=0 missing=0 total=139
> unused_exclusions=[]
> 2022-06-01 11:55:00,946 - oe-selftest - INFO - Checking ipk packages for 
> differences...
> 2022-06-01 11:55:01,330 - oe-selftest - INFO - Reproducibility summary for 
> ipk: same=139 different=0 different_excluded=0 missing=0 total=139
> unused_exclusions=[]
> 2022-06-01 11:55:01,331 - oe-selftest - INFO - Checking rpm packages for 
> differences...
> 2022-06-01 11:55:01,760 - oe-selftest - INFO - Reproducibility summary for 
> rpm: same=139 different=0 different_excluded=0 missing=0 total=139
> unused_exclusions=[]
> 2022-06-01 11:55:01,760 - oe-selftest - INFO -  ... ok
> 2022-06-01 11:56:29,573 - oe-selftest - INFO - 
> --
> 2022-06-01 11:56:29,573 - oe-selftest - INFO - Ran 2 tests in 7495.224s
> 2022-06-01 11:56:29,573 - oe-selftest - INFO - OK
> 2022-06-01 11:56:31,723 - oe-selftest - INFO - RESULTS:
> 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> reproducible.DiffoscopeTests.test_diffoscope: PASSED (1025.89s)
> 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> reproducible.ReproducibleTests.test_reproducible_builds: PASSED (6378.78s)
> 2022-06-01 11:56:31,881 - oe-selftest - INFO - SUMMARY:
> 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest () - Ran 2 tests 
> in 7495.225s
> 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest - OK - All 
> required tests passed (successes=2, skipped=0, failures=0, errors=0)
>
> Is it possible that the reproducibility failure was caused by something else 
> included in your run on autobuilder?

It is quite possible that it is host distro specific, I've seen that
quite often in the past.  Let me know which distro you used for your
test and I'll try the same on the autobuilder.

Steve

>
> Cheers,
>
> On Mon, May 30, 2022 at 1:42 AM Steve Sakoman  wrote:
>>
>> On Wed, May 25, 2022 at 8:49 AM Martin Jansa  wrote:
>> >
>> > From: Khem Raj 
>> >
>> > This is a bugfix release on gcc-11 series, fixes 189 bugs [1]
>> > Drop backported patches already included in 11.3 release
>>
>> This is causing a reproducibility error in my autobuilder testing for
>> webkit-gtk.  I've tried multiple builds with and without the patch and
>> the failure is repeatable.
>>
>> Sadly diffoscope blows up due to

Re: [OE-core][dunfell][PATCH v2] curl: Add fix for CVE-2022-27781 CVE-2022-27782

On Tue, May 31, 2022 at 11:01 PM Riyaz Ahmed Khan  wrote:
>
> From: Riyaz Khan 
>
> Add patches for CVE issues: CVE-2022-27781 CVE-2022-27782
>
> CVE-2022-27781
> Link: 
> [https://github.com/curl/curl/commit/5c7da89d404bf59c8dd82a001119a16d18365917]

Unfortunately, this is still failing:

ERROR: curl-7.69.1-r0 do_patch: Applying patch 'CVE-2022-27781.patch'
on target directory
'/home/steve/builds/poky-contrib/build/tmp/work/core2-64-poky-linux/curl/7.69.1-r0/curl-7.69.1'
Command Error: 'quilt --quiltrc
/home/steve/builds/poky-contrib/build/tmp/work/core2-64-poky-linux/curl/7.69.1-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch CVE-2022-27781.patch
patching file lib/vtls/nss.c
Hunk #1 FAILED at 983.
Hunk #2 succeeded at 986 (offset -32 lines).
1 out of 2 hunks FAILED -- rejects in file lib/vtls/nss.c
Patch CVE-2022-27781.patch does not apply (enforce with -f)
ERROR: Logfile of failure stored in:
/home/steve/builds/poky-contrib/build/tmp/work/core2-64-poky-linux/curl/7.69.1-r0/temp/log.do_patch.1303805
ERROR: Task 
(/home/steve/builds/poky-contrib/meta/recipes-support/curl/curl_7.69.1.bb:do_patch)
failed with exit code '1'

Steve

> CVE-2022-27782
> Link: 
> [https://github.com/curl/curl/commit/1645e9b44505abd5cbaf65da5282c3f33b5924a5]
>
> Signed-off-by: Riyaz Khan 
> ---
>  .../curl/curl/CVE-2022-27781.patch| 50 +
>  .../curl/curl/CVE-2022-27782.patch| 75 +++
>  meta/recipes-support/curl/curl_7.69.1.bb  |  2 +
>  3 files changed, 127 insertions(+)
>  create mode 100644 meta/recipes-support/curl/curl/CVE-2022-27781.patch
>  create mode 100644 meta/recipes-support/curl/curl/CVE-2022-27782.patch
>
> diff --git a/meta/recipes-support/curl/curl/CVE-2022-27781.patch 
> b/meta/recipes-support/curl/curl/CVE-2022-27781.patch
> new file mode 100644
> index 00..83cdd1290f
> --- /dev/null
> +++ b/meta/recipes-support/curl/curl/CVE-2022-27781.patch
> @@ -0,0 +1,50 @@
> +From 5c7da89d404bf59c8dd82a001119a16d18365917 Mon Sep 17 00:00:00 2001
> +From: Daniel Stenberg 
> +Date: Mon, 9 May 2022 10:07:15 +0200
> +Subject: [PATCH] nss: return error if seemingly stuck in a cert loop
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +CVE-2022-27781
> +
> +Reported-by: Florian Kohnhäuser
> +Bug: https://curl.se/docs/CVE-2022-27781.html
> +Closes #8822
> +
> +CVE: CVE-2022-27781
> +
> +Upstream-Status: Backport 
> [https://github.com/curl/curl/commit/5c7da89d404bf59c8dd82a001119a16d18365917]
> +
> +Signed-off-by: Riyaz Ahmed Khan 
> +
> +---
> + lib/vtls/nss.c | 8 
> + 1 file changed, 8 insertions(+)
> +
> +diff --git a/lib/vtls/nss.c b/lib/vtls/nss.c
> +index 5b7de9f81895..569c0628feb5 100644
> +--- a/lib/vtls/nss.c
>  b/lib/vtls/nss.c
> +@@ -983,6 +983,9 @@ static void display_cert_info(struct Curl_easy *data,
> +   PR_Free(common_name);
> + }
> +
> ++/* A number of certs that will never occur in a real server handshake */
> ++#define TOO_MANY_CERTS 300
> ++
> + static CURLcode display_conn_info(struct Curl_easy *data, PRFileDesc *sock)
> + {
> +   CURLcode result = CURLE_OK;
> +@@ -1018,6 +1021,11 @@ static CURLcode display_conn_info(struct Curl_easy 
> *data, PRFileDesc *sock)
> + cert2 = CERT_FindCertIssuer(cert, now, certUsageSSLCA);
> + while(cert2) {
> +   i++;
> ++  if(i >= TOO_MANY_CERTS) {
> ++CERT_DestroyCertificate(cert2);
> ++failf(data, "certificate loop");
> ++return CURLE_SSL_CERTPROBLEM;
> ++  }
> +   if(cert2->isRoot) {
> + CERT_DestroyCertificate(cert2);
> + break;
> diff --git a/meta/recipes-support/curl/curl/CVE-2022-27782.patch 
> b/meta/recipes-support/curl/curl/CVE-2022-27782.patch
> new file mode 100644
> index 00..a88aabe517
> --- /dev/null
> +++ b/meta/recipes-support/curl/curl/CVE-2022-27782.patch
> @@ -0,0 +1,75 @@
> +From 1645e9b44505abd5cbaf65da5282c3f33b5924a5 Mon Sep 17 00:00:00 2001
> +From: Daniel Stenberg 
> +Date: Mon, 9 May 2022 23:13:53 +0200
> +Subject: [PATCH] url: check SSH config match on connection reuse
> +
> +CVE-2022-27782
> +
> +Reported-by: Harry Sintonen
> +Bug: https://curl.se/docs/CVE-2022-27782.html
> +Closes #8825
> +
> +CVE: CVE-2022-27782
> +
> +Upstream-Status: Backport 
> [https://github.com/curl/curl/commit/1645e9b44505abd5cbaf65da5282c3f33b5924a5]
> +
> +Signed-off-by: Riyaz Ahmed Khan 
> +
> +---
> + lib/url.c  | 11 +++
> + lib/vssh/ssh.h |  6 +++---
> + 2 files changed, 14 insertions(+), 3 deletions(-)
> +
> +diff --git a/lib/url.c b/lib/url.c
> +index cf14a333ac69..6b31d4b1315d 100644
> +--- a/lib/url.c
>  b/lib/url.c
> +@@ -1100,6 +1100,12 @@ static void prune_dead_connections(struct Curl_easy 
> *data)
> +   }
> + }
> +
> ++static bool ssh_config_matches(struct connectdata *one,
> ++   struct connectdata *two)
> ++{
> ++  return (Curl_safecmp(one-

Re: [OE-core] [kirkstone][PATCH 1/2] gcc: Upgrade to 11.3 release

On Wed, 2022-06-01 at 05:29 -1000, Steve Sakoman wrote:
> On Wed, Jun 1, 2022 at 12:10 AM Martin Jansa  wrote:
> > 
> > As discussed on IRC yesterday I've tried to reproduce this failure locally 
> > and it works fine with poky master cee443ae75f (last commit in master 
> > before the upgrade to 12.1)
> > 2022-06-01 09:46:37,051 - oe-selftest - INFO - RESULTS - 
> > reproducible.ReproducibleTests.test_reproducible_builds: PASSED (6429.19s)
> > and now it passed with kirkstone as well:
> > 
> > poky $ git cherry-pick 44a36caa7c2
> > Auto-merging meta/conf/distro/include/maintainers.inc
> > [jansa/kirkstone-gcc-11.3 5c6e280eed5] gcc: Upgrade to 11.3 release
> > ...
> > poky $ oe-selftest -r reproducible 2>&1 | tee 
> > log.oe-selftest.reproducible.kirkstone
> > 2022-06-01 09:51:31,653 - oe-selftest - INFO - Changing cwd to 
> > /OE/build/poky/build
> > 2022-06-01 09:51:31,653 - oe-selftest - INFO - Adding layer libraries:
> > 2022-06-01 09:51:31,653 - oe-selftest - INFO -  /OE/build/poky/meta-poky/lib
> > 2022-06-01 09:51:31,653 - oe-selftest - INFO -  /OE/build/poky/meta/lib
> > 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> > /OE/build/poky/meta-yocto-bsp/lib
> > 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> > /OE/build/poky/meta-selftest/lib
> > 2022-06-01 09:51:31,655 - oe-selftest - INFO - Running bitbake -e to test 
> > the configuration is valid/parsable
> > hint: Using 'master' as the name for the initial branch. This default 
> > branch name
> > hint: is subject to change. To configure the initial branch name to use in 
> > all
> > hint: of your new repositories, which will suppress this warning, call:
> > hint:
> > hint:   git config --global init.defaultBranch 
> > hint:
> > hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
> > hint: 'development'. The just-created branch can be renamed via this 
> > command:
> > hint:
> > hint:   git branch -m 
> > 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include 
> > selftest.inc" in /OE/build/poky/build-st/conf/local.conf
> > 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include 
> > bblayers.inc" in bblayers.conf
> > 2022-06-01 09:51:37,092 - oe-selftest - INFO - test_diffoscope 
> > (reproducible.DiffoscopeTests)
> > 2022-06-01 10:08:42,982 - oe-selftest - INFO -  ... ok
> > 2022-06-01 10:08:42,983 - oe-selftest - INFO - test_reproducible_builds 
> > (reproducible.ReproducibleTests)
> > 2022-06-01 10:09:56,114 - oe-selftest - INFO - Building reproducibleA 
> > (sstate allowed)...
> > ^Ap2022-06-01 11:11:09,785 - oe-selftest - INFO - Building reproducibleB 
> > (sstate NOT allowed)...
> > 2022-06-01 11:55:00,507 - oe-selftest - INFO - Checking deb packages for 
> > differences...
> > 2022-06-01 11:55:00,946 - oe-selftest - INFO - Reproducibility summary for 
> > deb: same=139 different=0 different_excluded=0 missing=0 total=139
> > unused_exclusions=[]
> > 2022-06-01 11:55:00,946 - oe-selftest - INFO - Checking ipk packages for 
> > differences...
> > 2022-06-01 11:55:01,330 - oe-selftest - INFO - Reproducibility summary for 
> > ipk: same=139 different=0 different_excluded=0 missing=0 total=139
> > unused_exclusions=[]
> > 2022-06-01 11:55:01,331 - oe-selftest - INFO - Checking rpm packages for 
> > differences...
> > 2022-06-01 11:55:01,760 - oe-selftest - INFO - Reproducibility summary for 
> > rpm: same=139 different=0 different_excluded=0 missing=0 total=139
> > unused_exclusions=[]
> > 2022-06-01 11:55:01,760 - oe-selftest - INFO -  ... ok
> > 2022-06-01 11:56:29,573 - oe-selftest - INFO - 
> > --
> > 2022-06-01 11:56:29,573 - oe-selftest - INFO - Ran 2 tests in 7495.224s
> > 2022-06-01 11:56:29,573 - oe-selftest - INFO - OK
> > 2022-06-01 11:56:31,723 - oe-selftest - INFO - RESULTS:
> > 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> > reproducible.DiffoscopeTests.test_diffoscope: PASSED (1025.89s)
> > 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> > reproducible.ReproducibleTests.test_reproducible_builds: PASSED (6378.78s)
> > 2022-06-01 11:56:31,881 - oe-selftest - INFO - SUMMARY:
> > 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest () - Ran 2 tests 
> > in 7495.225s
> > 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest - OK - All 
> > required tests passed (successes=2, skipped=0, failures=0, errors=0)
> > 
> > Is it possible that the reproducibility failure was caused by something 
> > else included in your run on autobuilder?
> 
> It is quite possible that it is host distro specific, I've seen that
> quite often in the past.  Let me know which distro you used for your
> test and I'll try the same on the autobuilder.

Keep in mind that the test uses sstate to compare against so even that
isn't a guarantee of identifying the issue.

Did you try the strings comparison I suggested? Do you have the file
section tables comparison (diff) I could look at?

Cheers,

Richard



-=-=-=-=-=-=-=-

[OE-core] [AUH] glib-2.0: upgrading to 2.72.2 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-2.0* to *2.72.2* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-glib-2.0-upgrade-2.72.1-2.72.2.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/glib-2.0/glib-2.0-bash-completion: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-bash-completion: PKGV changed 
from 2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-codegen: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-codegen: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-dbg: PV changed from "2.72.1" to 
"2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-dbg: FILELIST: removed 
"/usr/lib/.debug/libgthread-2.0.so.0.7200.1 
/usr/lib/.debug/libgio-2.0.so.0.7200.1 
/usr/lib/.debug/libgmodule-2.0.so.0.7200.1 
/usr/lib/.debug/libglib-2.0.so.0.7200.1 
/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.7200.1-gdb.py 
/usr/share/gdb/auto-load/usr/lib/libglib-2.0.so.0.7200.1-gdb.py 
/usr/lib/.debug/libgobject-2.0.so.0.7200.1", added 
"/usr/lib/.debug/libgthread-2.0.so.0.7200.2 
/usr/lib/.debug/libgmodule-2.0.so.0.7200.2 
/usr/lib/.debug/libglib-2.0.so.0.7200.2 /usr/lib/.debug/libgio-2.0.so.0.7200.2 
/usr/lib/.debug/libgobject-2.0.so.0.7200.2 
/usr/share/gdb/auto-load/usr/lib/libglib-2.0.so.0.7200.2-gdb.py 
/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.7200.2-gdb.py"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-dbg: PKGSIZE changed from 
21024068 to 21024536 (+0%)
packages/core2-32-poky-linux/glib-2.0/glib-2.0-dbg: PKGV changed from 2.72.1 
[default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-dev: PV changed from "2.72.1" to 
"2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-dev: PKGV changed from 2.72.1 
[default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-doc: PV changed from "2.72.1" to 
"2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-doc: PKGV changed from 2.72.1 
[default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-af: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-af: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-am: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-am: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-an: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-an: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-ar: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-ar: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-as: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-as: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-ast: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-ast: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-az: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-az: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-be+latin: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-be+latin: PKGV changed 
from 2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-be: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-be: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-bg: PV changed from 
"2.72.1" to "2.72.2"
packages/core2-32-poky-linux/glib-2.0/glib-2.0-locale-bg: PKGV changed from 
2.72.1 [default] to 2.72.2 [default]
packages/core2-32-poky

[OE-core] [AUH] ovmf: upgrading to edk2-stable202205 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202205* 
has Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 
0001-ovmf-upgrade-edk2-stable202202-edk2-stable202205.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-ovmf-upgrade-edk2-stable202202-edk2-stable202205.patch
Description: Binary data
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (882 cached, 1 parsed). 1642 targets, 36 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 2 recipes from the qemux86 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-e338cba712cfde5d8a175c69eb55e145343966df"
TUNE_FEATURES= "m32 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:e338cba712cfde5d8a175c69eb55e145343966df"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 26 Local 15 Mirrors 0 Missed 11 Current 235 (57% match, 
95% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 797 of 1128 
(virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_fetch)
NOTE: Running task 811 of 1128 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_fetch)
NOTE: recipe ovmf-edk2-stable202205-r0: task do_fetch: Started
NOTE: recipe ovmf-native-edk2-stable202205-r0: task do_fetch: Started
NOTE: recipe ovmf-edk2-stable202205-r0: task do_fetch: Succeeded
NOTE: Running task 1105 of 1128 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_unpack)
NOTE: recipe ovmf-edk2-stable202205-r0: task do_unpack: Started
NOTE: recipe ovmf-native-edk2-stable202205-r0: task do_fetch: Succeeded
NOTE: Running task 1106 of 1128 
(virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_unpack)
NOTE: Running task 1107 of 1128 
(virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe ovmf-native-edk2-stable202205-r0: task do_unpack: Started
NOTE: recipe ovmf-native-edk2-stable202205-r0: task do_prepare_recipe_sysroot: 
Started
NOTE: recipe ovmf-native-edk2-stable202205-r0: task do_prepare_recipe_sysroot: 
Succeeded
NOTE: recipe ovmf-edk2-stable202205-r0: task do_unpack: Succeeded
NOTE: Running task 1108 of 1128 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_patch)
NOTE: recipe ovmf-edk2-stable202205-r0: task do_patch: Started
NOTE: recipe ovmf-edk2-stable202205-r0: task do_patch: Failed
NOTE: recipe ovmf-native-edk2-stable202205-r0: task do_unpack: Succeeded
NOTE: Tasks Summary: Attempted 1108 tasks of which 1102 didn't need to be rerun 
and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds

Summary: 1 task failed:
  
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_patch
Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.
/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: ovmf-edk2-stable202205-r0 do_patch: Applying patch 
'0006-Committing-changes-from-do_patch.patch' on target directory 
'/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-32-poky-linux/ovmf/edk2-stable202205-r0/git'
CmdError('quilt --quiltrc 
/home/pokybuild/yocto-worker/

[OE-core] [AUH] seatd: upgrading to 0.7.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *seatd* to *0.7.0* has Failed 
(devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe seatd failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-780a5b66a51cab425a5cabb48f9d07672f1841bf"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:780a5b66a51cab425a5cabb48f9d07672f1841bf"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 20 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto a803ba0502cccf147eec7fbcacd11c5b8643c0e0
WARNING: Command 'git rebase a803ba0502cccf147eec7fbcacd11c5b8643c0e0' failed:
Auto-merging seatd-launch/seatd-launch.c
CONFLICT (content): Merge conflict in seatd-launch/seatd-launch.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/seatd
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/seatd/seatd_0.7.0.bb



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166394): 
https://lists.openembedded.org/g/openembedded-core/message/166394
Mute This Topic: https://lists.openembedded.org/mt/91480149/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] btrfs-tools: upgrading to 5.18 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *5.18* has 
Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe btrfs-tools failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-780a5b66a51cab425a5cabb48f9d07672f1841bf"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:780a5b66a51cab425a5cabb48f9d07672f1841bf"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 20 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto f9e303584272b81b05b926a0cc9010f43af12a03
WARNING: Command 'git rebase f9e303584272b81b05b926a0cc9010f43af12a03' failed:
Auto-merging configure.ac
CONFLICT (content): Merge conflict in configure.ac
Auto-merging cmds/restore.c
CONFLICT (content): Merge conflict in cmds/restore.c
Auto-merging Makefile

You will need to resolve conflicts in order to complete the upgrade.
INFO: Using source tree as build directory since recipe inherits 
autotools-brokensep
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/btrfs-tools
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/btrfs-tools/btrfs-tools_5.18.bb



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166395): 
https://lists.openembedded.org/g/openembedded-core/message/166395
Mute This Topic: https://lists.openembedded.org/mt/91480150/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] systemd-boot: upgrading to 251.1 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd-boot* to *251.1* has 
Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe systemd-boot failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-780a5b66a51cab425a5cabb48f9d07672f1841bf"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:780a5b66a51cab425a5cabb48f9d07672f1841bf"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 20 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto dcda9f3d078709b26a6612a9581795e64b27b509
WARNING: Command 'git rebase dcda9f3d078709b26a6612a9581795e64b27b509' failed:
Auto-merging src/boot/efi/boot.c
CONFLICT (content): Merge conflict in src/boot/efi/boot.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/systemd-boot
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/systemd-boot/systemd-boot_251.1.bb



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166396): 
https://lists.openembedded.org/g/openembedded-core/message/166396
Mute This Topic: https://lists.openembedded.org/mt/91480151/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] python3-dtschema: upgrading to 2022.5 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dtschema* to *2022.5* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-python3-dtschema-upgrade-2022.4-2022.5.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/python3-dtschema: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/d/dtschema/dtschema-2022.4.tar.gz";
 to 
"https://files.pythonhosted.org/packages/source/d/dtschema/dtschema-2022.5.tar.gz";
packages/core2-32-poky-linux/python3-dtschema: PV changed from "2022.4" to 
"2022.5"
packages/core2-32-poky-linux/python3-dtschema: PKGV changed from 2022.4 
[default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dbg: PV changed 
from "2022.4" to "2022.5"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dbg: PKGV 
changed from 2022.4 [default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dev: PV changed 
from "2022.4" to "2022.5"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dev: PKGV 
changed from 2022.4 [default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-doc: PV changed 
from "2022.4" to "2022.5"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-doc: PKGV 
changed from 2022.4 [default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-locale: PV 
changed from "2022.4" to "2022.5"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-locale: PKGV 
changed from 2022.4 [default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-src: PV changed 
from "2022.4" to "2022.5"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-src: PKGV 
changed from 2022.4 [default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-staticdev: PV 
changed from "2022.4" to "2022.5"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-staticdev: PKGV 
changed from 2022.4 [default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: PKGSIZE changed 
from 214407 to 218918 (+2%)
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: PV changed from 
"2022.4" to "2022.5"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: PKGV changed 
from 2022.4 [default] to 2022.5 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: FILELIST: 
directory renamed /usr/lib/python3.10/site-packages/dtschema-2022.4.dist-info 
-> /usr/lib/python3.10/site-packages/dtschema-2022.5.dist-info, added 
"/usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bus.yaml 
/usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bridge.yaml"
Changes to packages/core2-32-poky-linux/python3-dtschema (sysroot):
  /usr/lib/python3.10/site-packages/dtschema-2022.4.dist-info moved to 
/usr/lib/python3.10/site-packages/dtschema-2022.5.dist-info
  /usr/lib/python3.10/site-packages/dtschema/schemas/isa was added
  /usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bridge.yaml was 
added
  /usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bus.yaml was added
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: FILELIST: 
directory renamed /usr/lib/python3.10/site-packages/dtschema-2022.4.dist-info 
-> /usr/lib/python3.10/site-packages/dtschema-2022.5.dist-info, added 
"/usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bridge.yaml 
/usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bus.yaml"
Changes to packages/core2-32-poky-linux/python3-dtschema (sysroot):
  /usr/lib/python3.10/site-packages/dtschema-2022.4.dist-info moved to 
/usr/lib/python3.10/site-packages/dtschema-2022.5.dist-info
  /usr/lib/python3.10/site-packages/dtschema/schemas/isa was added
  /usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bridge.yaml was 
added
  /usr/lib/python3.10/site-packages/dtschema/schemas/isa/isa-bus.yaml was added


0001-python3-dtschema-upgrade-2022.4-2022.5.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166403): 
https://lists.openembedded.org/g/openembedded-core/message/166403
Mute This

[OE-core] [AUH] systemd: upgrading to 251.1 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd* to *251.1* has
Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe systemd failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.1+snapshot-780a5b66a51cab425a5cabb48f9d07672f1841bf"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:780a5b66a51cab425a5cabb48f9d07672f1841bf"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 20 (0% match, 100%
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
INFO: SRC_URI contains some conditional appends/prepends - will create branches
to represent these
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto dcda9f3d078709b26a6612a9581795e64b27b509
WARNING: Command 'git rebase dcda9f3d078709b26a6612a9581795e64b27b509' failed:
Auto-merging src/boot/efi/boot.c
CONFLICT (content): Merge conflict in src/boot/efi/boot.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Rebasing devtool-override-libc-musl onto
dcda9f3d078709b26a6612a9581795e64b27b509
WARNING: Command 'git rebase dcda9f3d078709b26a6612a9581795e64b27b509' failed:
Auto-merging src/boot/efi/boot.c
CONFLICT (content): Merge conflict in src/boot/efi/boot.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/systemd
INFO: New recipe is
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/systemd/systemd_251.1.bb

Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166397):
https://lists.openembedded.org/g/openembedded-core/message/166397
Mute This Topic: https://lists.openembedded.org/mt/91480152/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] python3-numpy: upgrading to 1.22.4 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-numpy* to *1.22.4* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-python3-numpy-upgrade-1.22.3-1.22.4.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/python3-numpy: PV changed from "1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy: SRC_URI changed from 
"https://github.com/numpy/numpy/releases/download/v1.22.3/numpy-1.22.3.tar.gz 
file://0001-Don-t-search-usr-and-so-on-for-libraries-by-default-.patch 
file://0001-numpy-core-Define-RISCV-32-support.patch file://run-ptest" to 
"https://github.com/numpy/numpy/releases/download/v1.22.4/numpy-1.22.4.tar.gz 
file://0001-Don-t-search-usr-and-so-on-for-libraries-by-default-.patch 
file://0001-numpy-core-Define-RISCV-32-support.patch file://run-ptest"
packages/core2-32-poky-linux/python3-numpy: PKGV changed from 1.22.3 [default] 
to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy-dbg: PKGSIZE changed 
from 30772680 to 30773484 (+0%)
packages/core2-32-poky-linux/python3-numpy/python3-numpy-dbg: PV changed from 
"1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy-dbg: PKGV changed from 
1.22.3 [default] to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy-dev: PV changed from 
"1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy-dev: PKGV changed from 
1.22.3 [default] to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy-doc: PV changed from 
"1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy-doc: PKGV changed from 
1.22.3 [default] to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy-locale: PV changed 
from "1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy-locale: PKGV changed 
from 1.22.3 [default] to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy-ptest: PV changed from 
"1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy-ptest: PKGV changed 
from 1.22.3 [default] to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy-src: PKGSIZE changed 
from 18538049 to 18539381 (+0%)
packages/core2-32-poky-linux/python3-numpy/python3-numpy-src: PV changed from 
"1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy-src: PKGV changed from 
1.22.3 [default] to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy-staticdev: PKGSIZE 
changed from 260590 to 260622 (+0%)
packages/core2-32-poky-linux/python3-numpy/python3-numpy-staticdev: PV changed 
from "1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy-staticdev: PKGV 
changed from 1.22.3 [default] to 1.22.4 [default]
packages/core2-32-poky-linux/python3-numpy/python3-numpy: PKGSIZE changed from 
33116355 to 33126764 (+0%)
packages/core2-32-poky-linux/python3-numpy/python3-numpy: PV changed from 
"1.22.3" to "1.22.4"
packages/core2-32-poky-linux/python3-numpy/python3-numpy: PKGV changed from 
1.22.3 [default] to 1.22.4 [default]
Changes to packages/core2-32-poky-linux/python3-numpy (sysroot):
  /usr/lib/python3.10/site-packages/numpy-1.22.3.dist-info moved to 
/usr/lib/python3.10/site-packages/numpy-1.22.4.dist-info
Changes to packages/core2-32-poky-linux/python3-numpy (sysroot):
  /usr/lib/python3.10/site-packages/numpy-1.22.3.dist-info moved to 
/usr/lib/python3.10/site-packages/numpy-1.22.4.dist-info


0001-python3-numpy-upgrade-1.22.3-1.22.4.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166401): 
https://lists.openembedded.org/g/openembedded-core/message/166401
Mute This Topic: https://lists.openembedded.org/mt/91480156/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] llvm: upgrading to 14.0.4 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *14.0.4* has Failed 
(devtool error).

Detailed error information:

The following devtool command failed:  finish -f llvm 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/llvm
NOTE: Starting bitbake server...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 884 .bb files complete (882 cached, 2 parsed). 1645 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.

Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 334, in 
ret = main()
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 321, in main
ret = args.func(args, config, basepath, workspace)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 2108, in finish
updated, appendfile, removed = _update_recipe(args.recipename, workspace, 
rd, args.mode, appendlayerdir, wildcard_version=True, no_remove=False, 
no_report_remove=removing_original, initial_rev=args.initial_rev, 
dry_run_outdir=dry_run_outdir, no_overrides=args.no_overrides, 
force_patch_refresh=args.force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1814, in _update_recipe
updated, appendf, removed = _update_recipe_patch(recipename, workspace, 
srctree, crd, appendlayerdir, wildcard_version, no_remove, no_report_remove, 
initial_rev, dry_run_outdir, force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1608, in _update_recipe_patch
initial_rev, update_rev, changed_revs, filter_patches = 
_get_patchset_revs(srctree, append, initial_rev, force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1213, in _get_patchset_revs
initial_rev, cwd=srctree)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/process.py", 
line 187, in run
raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
bb.process.ExecutionError: Execution of 'git rev-list --reverse 
29f1039a7285a5c3a9c353d054140bf2556d4c4d..HEAD' failed with exit code 128:
fatal: Invalid revision range 29f1039a7285a5c3a9c353d054140bf2556d4c4d..HEAD



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166398): 
https://lists.openembedded.org/g/openembedded-core/message/166398
Mute This Topic: https://lists.openembedded.org/mt/91480153/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] gnu-config: upgrading to 02ba26b218d3d3db6c56e014655faf463cefa983 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to 
*02ba26b218d3d3db6c56e014655faf463cefa983* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade gnu-config -S 
02ba26b218d3d3db6c56e014655faf463cefa983
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-693b7126fbef93868d315ed8a4aaa4f4f192378e"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:693b7126fbef93868d315ed8a4aaa4f4f192378e"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 8 Local 0 Mirrors 0 Missed 8 Current 12 (0% match, 60% 
complete)
Removing 6 stale sstate objects for arch x86_64...done.
NOTE: Executing Tasks
WARNING: Failed to find a git repository in WORKDIR: 
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir
WARNING: gnu-config: the directory ${WORKDIR}/git 
(/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir/git)
 pointed to by the S variable doesn't exist - please set S within the recipe to 
point to where the source has been unpacked to
WARNING: No source unpacked to S - either the gnu-config recipe doesn't use any 
source or the correct source directory could not be determined
NOTE: Tasks Summary: Attempted 56 tasks of which 51 didn't need to be rerun and 
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
ERROR: Bitbake Fetcher Error: FetchError('Fetch command export 
PSEUDO_DISABLED=1; export ftp_proxy="http://proxy.yocto.io:5187/";; export 
FTP_PROXY="http://proxy.yocto.io:5187/";; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/native-intercept:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir/recipe-sysroot-native/usr/bin/x86_64-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir/recipe-sysroot-native/usr/sbin:/home/pokybuild/
 
yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/workdir/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; git -c core.fsyncobjectfiles=0 -c 
gc.autoDetach=false -c core.pager=cat clone -n -s 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git2/git.savannah.gnu.org.git.config.git/
 
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0
 /devtooltmp-wwp2vgcj/workdir/git/ failed with exit code 128, output:\nfatal: 
destination path 
\'/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20220516+gitAUTOINC+f56a714038-r0/devtooltmp-wwp2vgcj/work

[OE-core] [AUH] cmake: upgrading to 3.23.2 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cmake* to *3.23.2* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.23.1-3.23.2.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-cmake-upgrade-3.23.1-3.23.2.patch
Description: Binary data
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...WARNING: 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/cmake/cmake-native_3.23.1.bb:
 Unable to get checksum for cmake-native SRC_URI entry OEToolchainConfig.cmake: 
file could not be found
done.
Parsing of 883 .bb files complete (881 cached, 2 parsed). 1642 targets, 36 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 1 recipes from the qemux86 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-780a5b66a51cab425a5cabb48f9d07672f1841bf"
TUNE_FEATURES= "m32 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:780a5b66a51cab425a5cabb48f9d07672f1841bf"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 46 Local 34 Mirrors 0 Missed 12 Current 181 (73% match, 
94% complete)
Removing 1 stale sstate objects for arch core2-32...done.
Removing 2 stale sstate objects for arch x86_64...done.
Removing 1 stale sstate objects for arch qemux86...done.
NOTE: Executing Tasks
NOTE: Running setscene task 199 of 227 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/expat/expat_2.4.8.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running task 668 of 881 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/cmake/cmake-native_3.23.1.bb:do_fetch)
NOTE: Running task 752 of 881 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/cmake/cmake_3.23.2.bb:do_fetch)
NOTE: recipe cmake-native-3.23.1-r0: task do_fetch: Started
WARNING: cmake-native-3.23.1-r0 do_fetch: Checksum mismatch for local file 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/cmake-3.23.1.tar.gz
Cleaning and trying again.
WARNING: cmake-native-3.23.1-r0 do_fetch: Renaming 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/cmake-3.23.1.tar.gz
 to 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/cmake-3.23.1.tar.gz_bad-checksum_33fd10a8ec687a4d0d5b42473f10459bb92b3ae7def2b745dc10b192760869f3
NOTE: recipe cmake-3.23.2-r0: task do_fetch: Started
NOTE: recipe expat-2.4.8-r0: task do_deploy_source_date_epoch_setscene: Started
NOTE: recipe cmake-3.23.2-r0: task do_fetch: Succeeded
NOTE: Running task 844 of 881 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/cmake/cmake_3.23.2.bb:do_unpack)
NOTE: recipe expat-2.4.8-r0: task do_deploy_source_date_epoch_setscene: 
Succeeded
NOTE: Setscene tasks completed
NOTE: Running task 845 of 881 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/expat/expat_2.4.8.bb:do_fetch)
NOTE: recipe cmake-3.23.2-r0: task do_unpack: Started
NOTE: recipe expat-2.4.8-r0: task do_fetch: Started
NOTE: recipe expat-2.4.8-r0: task do_fetch: Succeeded
NOTE: Running task 846 of 881 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/expat/expat_2.4.8.bb:do_unpack)
NOTE: recipe expat-2.4.8-r0: task do_unpack: Started
NOTE: recipe expat-2.4.8-r0: task do_unpack: Succeeded
NOTE: Running task 847 of 881 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/expat/expat_2.4.8.bb:do_patch)
NOTE: recipe expat-2.4.8-r0: task do_patch: Started
NOTE: recipe expat-2.4.8-r0: task do_patch: Succeeded
NOTE: Running task 848 of 881 
(/home/pokybuild/yocto

[OE-core] [AUH] vulkan-samples: upgrading to fa909d508e8b5ef817b0c68b91034c13a6b4bc15 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to 
*fa909d508e8b5ef817b0c68b91034c13a6b4bc15* has Failed(other errors).

Detailed error information:

'MACHINE=qemux86 bitbake vulkan-samples' failed
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (0 cached, 883 parsed). 1642 targets, 36 
skipped, 0 masked, 0 errors.
Removing 70 recipes from the core2-32 sysroot...done.
Removing 83 recipes from the qemux86 sysroot...done.

Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.

/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: Nothing PROVIDES 'vulkan-samples'
vulkan-samples was skipped: incompatible with host i686-poky-linux (not in 
COMPATIBLE_HOST)


Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166413): 
https://lists.openembedded.org/g/openembedded-core/message/166413
Mute This Topic: https://lists.openembedded.org/mt/91480168/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] rust-llvm: upgrading to 1.61.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust-llvm* to *1.61.0* has 
Failed (devtool error).

Detailed error information:

The following devtool command failed:  finish -f rust-llvm 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust
NOTE: Starting bitbake server...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1643 entries from dependency cache.
Parsing recipes...done.
Parsing of 884 .bb files complete (883 cached, 1 parsed). 1644 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.

ERROR: Traceback (most recent call last):
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 162, in wrapped
return func(fn, *args)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 187, in parse_config_file
return bb.parse.handle(fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 107, in handle
return h['handle'](fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py",
 line 118, in handle
abs_fn = resolve_file(fn, data)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 133, in resolve_file
raise IOError(errno.ENOENT, "file %s not found" % fn)
FileNotFoundError: [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf
 not found

ERROR: Unable to parse 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf:
 [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf
 not found
Traceback (most recent call last):
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 162, in wrapped
return func(fn, *args)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 187, in parse_config_file
return bb.parse.handle(fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 107, in handle
return h['handle'](fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py",
 line 118, in handle
abs_fn = resolve_file(fn, data)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 133, in resolve_file
raise IOError(errno.ENOENT, "file %s not found" % fn)
FileNotFoundError: [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf
 not found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 334, in 
ret = main()
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 321, in main
ret = args.func(args, config, basepath, workspace)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 2108, in finish
updated, appendfile, removed = _update_recipe(args.recipename, workspace, 
rd, args.mode, appendlayerdir, wildcard_version=True, no_remove=False, 
no_report_remove=removing_original, initial_rev=args.initial_rev, 
dry_run_outdir=dry_run_outdir, no_overrides=args.no_overrides, 
force_patch_refresh=args.force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1814, in _update_recipe
updated, appendf, removed = _update_recipe_patch(recipename, workspace, 
srctree, crd, appendlayerdir, wildcard_version, no_remove, no_report_remove, 
initial_rev, dry_run_outdir, force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1671, in _update_recipe_patch
redirect_output=dry_run_outdir)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", 
line 705, in bbappend_recipe
appendpath, pathok = get_bbappend_path(rd, destlayerdir, wildcardver)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", 
line 632, in get_bbappend_path
confdata = bb.cookerdata.parse_config_file(destlayerconf, confdata)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 167, in wrapped
raise bb.BBHandledException()
bb.BBHandledException


Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://

[OE-core] [AUH] python3-sphinx: upgrading to 5.0.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-sphinx* to *5.0.0* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-python3-sphinx-upgrade-4.5.0-5.0.0.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-python3-sphinx-upgrade-4.5.0-5.0.0.patch
Description: Binary data
packages/core2-32-poky-linux/python3-sphinx: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/S/Sphinx/Sphinx-4.5.0.tar.gz"; 
to "https://files.pythonhosted.org/packages/source/S/Sphinx/Sphinx-5.0.0.tar.gz";
packages/core2-32-poky-linux/python3-sphinx: PKGV changed from 4.5.0 [default] 
to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx: PV changed from "4.5.0" to "5.0.0"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-dbg: PKGV changed 
from 4.5.0 [default] to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-dbg: PV changed from 
"4.5.0" to "5.0.0"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-dev: PKGV changed 
from 4.5.0 [default] to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-dev: PV changed from 
"4.5.0" to "5.0.0"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-doc: PKGV changed 
from 4.5.0 [default] to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-doc: PV changed from 
"4.5.0" to "5.0.0"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-locale: PKGV changed 
from 4.5.0 [default] to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-locale: PV changed 
from "4.5.0" to "5.0.0"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-src: PKGV changed 
from 4.5.0 [default] to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-src: PV changed from 
"4.5.0" to "5.0.0"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-staticdev: PKGV 
changed from 4.5.0 [default] to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx-staticdev: PV 
changed from "4.5.0" to "5.0.0"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx: PKGSIZE changed 
from 13751917 to 13816540 (+0%)
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx: FILELIST: directory 
renamed /usr/lib/python3.10/site-packages/Sphinx-4.5.0.dist-info -> 
/usr/lib/python3.10/site-packages/Sphinx-5.0.0.dist-info, removed 
"/usr/lib/python3.10/site-packages/sphinx/search/jssplitter.py 
/usr/lib/python3.10/site-packages/sphinx/ext/autodoc/__pycache__/deprecated.cpython-310.pyc
 
/usr/lib/python3.10/site-packages/sphinx/search/__pycache__/jssplitter.cpython-310.pyc
 /usr/lib/python3.10/site-packages/sphinx/themes/basic/static/jquery-3.5.1.js 
/usr/lib/python3.10/site-packages/sphinx/ext/autodoc/deprecated.py", added 
"/usr/lib/python3.10/site-packages/sphinx/themes/basic/static/_sphinx_javascript_frameworks_compat.js
 /usr/lib/python3.10/site-packages/sphinx/locale/ru_RU/LC_MESSAGES/sphinx.po 
/usr/lib/python3.10/site-packages/sphinx/themes/basic/static/jquery-3.6.0.js 
/usr/lib/python3.10/site-packages/sphinx/locale/ru_RU/LC_MESSAGES/sphinx.mo 
/usr/lib/python3.10/site-packages/sphinx/locale/ru_RU/LC_ME
 SSAGES/sphinx.js"
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx: PKGV changed from 
4.5.0 [default] to 5.0.0 [default]
packages/core2-32-poky-linux/python3-sphinx/python3-sphinx: PV changed from 
"4.5.0" to "5.0.0"
Changes to packages/core2-32-poky-linux/python3-sphinx (sysroot):
  /usr/lib/python3.10/site-packages/Sphinx-4.5.0.dist-info moved to 
/usr/lib/python3.10/site-packages/Sphinx-5.0.0.dist-info
  /usr/lib/python3.10/site-packages/sphinx/themes/basic/static/jquery-3.5.1.js 
moved to 
/usr/lib/python3.10/site-packages/sphinx/themes/basic/static/jquery-3.6.0.js
  /usr/lib/python3.10/site-packages/sphinx/locale/ru_RU was added
  /usr/lib/python3.10/site-packages/sphinx/locale/ru_RU/LC_MESSAGES was added
  /usr/lib/python3.10/site-packages/sphinx/locale/ru_RU/LC_MESSAGES/sphinx.js 
was added
  /usr/lib/python3.10/site-packages/sphinx/locale/ru_RU/LC_MESSAGES/sphinx.mo 
was added
  /usr/lib/python3.10/site-packages/sphinx/locale/ru_RU/LC_MESSAGES/sphinx.po 
was added
  
/usr/lib/python3.10/site-packages/sphinx/themes/basic/static/_sphinx_javascript_frameworks_c

[OE-core] [AUH] python3-psutil: upgrading to 5.9.1 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-psutil* to *5.9.1* 
has Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe python3-psutil failed.
NOTE: Starting bitbake server...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-f802d945780891fc87a84de0e705db6ab11076bb"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:f802d945780891fc87a84de0e705db6ab11076bb"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% match, 
100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 884 .bb files complete (882 cached, 2 parsed). 1643 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-f802d945780891fc87a84de0e705db6ab11076bb"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:f802d945780891fc87a84de0e705db6ab11076bb"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files: 100% || Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://files.pythonhosted.org/packages/source/p/psutil/psutil-5.9.1.tar.gz...
INFO: Rebasing devtool onto 4c5fbc5809392ac1bc2b1c46ffcb9bd85d786d2d
WARNING: Command 'git rebase 4c5fbc5809392ac1bc2b1c46ffcb9bd85d786d2d' failed:
Auto-merging psutil/tests/test_unicode.py
Auto-merging psutil/tests/test_system.py
Auto-merging psutil/tests/test_process.py
Auto-merging psutil/tests/test_misc.py
CONFLICT (content): Merge conflict in psutil/tests/test_misc.py
Auto-merging psutil/tests/test_linux.py
Auto-merging psutil/tests/test_contracts.py

You will need to resolve conflicts in order to complete the upgrade.
INFO: Using source tree as build directory since that would be the default for 
this recipe
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/python3-psutil
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/python3-psutil/python3-psutil_5.9.1.bb



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166405): 
https://lists.openembedded.org/g/openembedded-core/message/166405
Mute This Topic: https://lists.openembedded.org/mt/91480160/21656
Group Owner: openembedded-core

[OE-core] [AUH] libstd-rs: upgrading to 1.61.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libstd-rs* to *1.61.0* has 
Failed (devtool error).

Detailed error information:

The following devtool command failed:  finish -f libstd-rs 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust
NOTE: Starting bitbake server...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 884 .bb files complete (883 cached, 1 parsed). 1644 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.

ERROR: Traceback (most recent call last):
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 162, in wrapped
return func(fn, *args)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 187, in parse_config_file
return bb.parse.handle(fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 107, in handle
return h['handle'](fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py",
 line 118, in handle
abs_fn = resolve_file(fn, data)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 133, in resolve_file
raise IOError(errno.ENOENT, "file %s not found" % fn)
FileNotFoundError: [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf
 not found

ERROR: Unable to parse 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf:
 [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf
 not found
Traceback (most recent call last):
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 162, in wrapped
return func(fn, *args)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 187, in parse_config_file
return bb.parse.handle(fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 107, in handle
return h['handle'](fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py",
 line 118, in handle
abs_fn = resolve_file(fn, data)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 133, in resolve_file
raise IOError(errno.ENOENT, "file %s not found" % fn)
FileNotFoundError: [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf
 not found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 334, in 
ret = main()
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 321, in main
ret = args.func(args, config, basepath, workspace)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 2108, in finish
updated, appendfile, removed = _update_recipe(args.recipename, workspace, 
rd, args.mode, appendlayerdir, wildcard_version=True, no_remove=False, 
no_report_remove=removing_original, initial_rev=args.initial_rev, 
dry_run_outdir=dry_run_outdir, no_overrides=args.no_overrides, 
force_patch_refresh=args.force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1814, in _update_recipe
updated, appendf, removed = _update_recipe_patch(recipename, workspace, 
srctree, crd, appendlayerdir, wildcard_version, no_remove, no_report_remove, 
initial_rev, dry_run_outdir, force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1671, in _update_recipe_patch
redirect_output=dry_run_outdir)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", 
line 705, in bbappend_recipe
appendpath, pathok = get_bbappend_path(rd, destlayerdir, wildcardver)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", 
line 632, in get_bbappend_path
confdata = bb.cookerdata.parse_config_file(destlayerconf, confdata)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 167, in wrapped
raise bb.BBHandledException()
bb.BBHandledException


Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://

[OE-core] [AUH] python3-pip: upgrading to 22.1.2 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pip* to *22.1.2* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-python3-pip-upgrade-22.1.1-22.1.2.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/python3-pip: PKGV changed from 22.1.1 [default] to 
22.1.2 [default]
packages/core2-32-poky-linux/python3-pip: PV changed from "22.1.1" to "22.1.2"
packages/core2-32-poky-linux/python3-pip: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/p/pip/pip-22.1.1.tar.gz 
file://0001-change-shebang-to-python3.patch file://no_shebang_mangling.patch 
file://reproducible.patch" to 
"https://files.pythonhosted.org/packages/source/p/pip/pip-22.1.2.tar.gz 
file://0001-change-shebang-to-python3.patch file://no_shebang_mangling.patch 
file://reproducible.patch"
packages/core2-32-poky-linux/python3-pip/python3-pip-dbg: PKGV changed from 
22.1.1 [default] to 22.1.2 [default]
packages/core2-32-poky-linux/python3-pip/python3-pip-dbg: PV changed from 
"22.1.1" to "22.1.2"
packages/core2-32-poky-linux/python3-pip/python3-pip-dev: PKGV changed from 
22.1.1 [default] to 22.1.2 [default]
packages/core2-32-poky-linux/python3-pip/python3-pip-dev: PV changed from 
"22.1.1" to "22.1.2"
packages/core2-32-poky-linux/python3-pip/python3-pip-doc: PKGV changed from 
22.1.1 [default] to 22.1.2 [default]
packages/core2-32-poky-linux/python3-pip/python3-pip-doc: PV changed from 
"22.1.1" to "22.1.2"
packages/core2-32-poky-linux/python3-pip/python3-pip-locale: PKGV changed from 
22.1.1 [default] to 22.1.2 [default]
packages/core2-32-poky-linux/python3-pip/python3-pip-locale: PV changed from 
"22.1.1" to "22.1.2"
packages/core2-32-poky-linux/python3-pip/python3-pip-src: PKGV changed from 
22.1.1 [default] to 22.1.2 [default]
packages/core2-32-poky-linux/python3-pip/python3-pip-src: PV changed from 
"22.1.1" to "22.1.2"
packages/core2-32-poky-linux/python3-pip/python3-pip-staticdev: PKGV changed 
from 22.1.1 [default] to 22.1.2 [default]
packages/core2-32-poky-linux/python3-pip/python3-pip-staticdev: PV changed from 
"22.1.1" to "22.1.2"
packages/core2-32-poky-linux/python3-pip/python3-pip: PKGSIZE changed from 
12541127 to 12541218 (+0%)
packages/core2-32-poky-linux/python3-pip/python3-pip: PKGV changed from 22.1.1 
[default] to 22.1.2 [default]
packages/core2-32-poky-linux/python3-pip/python3-pip: PV changed from "22.1.1" 
to "22.1.2"
Changes to packages/core2-32-poky-linux/python3-pip (sysroot):
  /usr/lib/python3.10/site-packages/pip-22.1.1.dist-info moved to 
/usr/lib/python3.10/site-packages/pip-22.1.2.dist-info
Changes to packages/core2-32-poky-linux/python3-pip (sysroot):
  /usr/lib/python3.10/site-packages/pip-22.1.1.dist-info moved to 
/usr/lib/python3.10/site-packages/pip-22.1.2.dist-info


0001-python3-pip-upgrade-22.1.1-22.1.2.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166407): 
https://lists.openembedded.org/g/openembedded-core/message/166407
Mute This Topic: https://lists.openembedded.org/mt/91480162/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] procps: upgrading to 4.0.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *procps* to *4.0.0* has Failed 
(devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe procps failed.
NOTE: Starting bitbake server...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-39eeed6b02bdeee5095ff92e916f9e3fe8642be6"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:39eeed6b02bdeee5095ff92e916f9e3fe8642be6"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% match, 
100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Extracting current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto 61825a5cc56b40c4afffd8c880b641210b05b3b7
WARNING: Command 'git rebase 61825a5cc56b40c4afffd8c880b641210b05b3b7' failed:
Auto-merging ps/output.c
CONFLICT (content): Merge conflict in ps/output.c
Auto-merging NEWS
CONFLICT (content): Merge conflict in NEWS

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/procps
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/procps/procps_4.0.0.bb



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166414): 
https://lists.openembedded.org/g/openembedded-core/message/166414
Mute This Topic: https://lists.openembedded.org/mt/91480169/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] libxkbcommon: upgrading to 1.4.1 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxkbcommon* to *1.4.1* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-libxkbcommon-upgrade-1.4.0-1.4.1.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/libxkbcommon: PKGV changed from 1.4.0 [default] to 
1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon: SRC_URI changed from 
"http://xkbcommon.org/download/libxkbcommon-1.4.0.tar.xz"; to 
"http://xkbcommon.org/download/libxkbcommon-1.4.1.tar.xz";
packages/core2-32-poky-linux/libxkbcommon: PV changed from "1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dbg: PKGV changed from 
1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dbg: PV changed from 
"1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dbg: PKGSIZE changed 
from 919148 to 919228 (+0%)
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dev: PKGV changed from 
1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dev: PV changed from 
"1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dev: PKGSIZE changed 
from 354865 to 354882 (+0%)
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-doc: PKGV changed from 
1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-doc: PV changed from 
"1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-locale: PKGV changed 
from 1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-locale: PV changed from 
"1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-src: PKGV changed from 
1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-src: PV changed from 
"1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-src: PKGSIZE changed 
from 1475990 to 1476588 (+0%)
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-staticdev: PKGV changed 
from 1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-staticdev: PV changed 
from "1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-x11: PKGV changed from 
1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-x11: PV changed from 
"1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon: PKGV changed from 1.4.0 
[default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon: PV changed from "1.4.0" 
to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/libxkbregistry: PKGV changed from 
1.4.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbregistry: PV changed from 
"1.4.0" to "1.4.1"
packages/core2-32-poky-linux/libxkbcommon/xkbcli: PKGV changed from 1.4.0 
[default] to 1.4.1 [default]
packages/core2-32-poky-linux/libxkbcommon/xkbcli: PV changed from "1.4.0" to 
"1.4.1"


0001-libxkbcommon-upgrade-1.4.0-1.4.1.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166412): 
https://lists.openembedded.org/g/openembedded-core/message/166412
Mute This Topic: https://lists.openembedded.org/mt/91480167/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] alsa-lib: upgrading to 1.2.7 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *alsa-lib* to *1.2.7* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-alsa-lib-upgrade-1.2.6.1-1.2.7.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-alsa-lib-upgrade-1.2.6.1-1.2.7.patch
Description: Binary data
packages/core2-32-poky-linux/alsa-lib/alsa-conf: PV changed from "1.2.6.1" to 
"1.2.7"
packages/core2-32-poky-linux/alsa-lib/alsa-conf: PKGV changed from 1.2.6.1 
[default] to 1.2.7 [default]
packages/core2-32-poky-linux/alsa-lib/alsa-conf: PKGSIZE changed from 154743 to 
155351 (+0%)
packages/core2-32-poky-linux/alsa-lib/alsa-lib-dbg: PV changed from "1.2.6.1" 
to "1.2.7"
packages/core2-32-poky-linux/alsa-lib/alsa-lib-dbg: PKGV changed from 1.2.6.1 
[default] to 1.2.7 [default]
packages/core2-32-poky-linux/alsa-lib/alsa-lib-dbg: PKGSIZE changed from 
2945196 to 2974008 (+1%)
packages/core2-32-poky-linux/alsa-lib/alsa-lib-dev: PV changed from "1.2.6.1" 
to "1.2.7"
packages/core2-32-poky-linux/alsa-lib/alsa-lib-dev: PKGV changed from 1.2.6.1 
[default] to 1.2.7 [default]
packages/core2-32-poky-linux/alsa-lib/alsa-lib-dev: PKGSIZE changed from 440502 
to 441381 (+0%)
packages/core2-32-poky-linux/alsa-lib/alsa-lib-doc: PV changed from "1.2.6.1" 
to "1.2.7"
packages/core2-32-poky-linux/alsa-lib/alsa-lib-doc: PKGV changed from 1.2.6.1 
[default] to 1.2.7 [default]
packages/core2-32-poky-linux/alsa-lib/alsa-lib-locale: PV changed from 
"1.2.6.1" to "1.2.7"
packages/core2-32-poky-linux/alsa-lib/alsa-lib-locale: PKGV changed from 
1.2.6.1 [default] to 1.2.7 [default]
packages/core2-32-poky-linux/alsa-lib/alsa-lib-src: FILELIST: directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/aserver -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/aserver, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/pcm -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src/pcm, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/seq -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src/seq, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/rawmidi -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src/rawmidi, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/mixer -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src/mixer, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/hwdep -> 
/usr/src/debug/alsa-l
 ib/1.2.7-r0/alsa-lib-1.2.7/src/hwdep, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/build/include/alsa/sound/uapi -> 
/usr/src/debug/alsa-lib/1.2.7-r0/build/include/alsa/sound/uapi, directory 
renamed /usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/topology -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src/topology, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/timer -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src/timer, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/ucm -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/src/ucm, directory renamed 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/include -> 
/usr/src/debug/alsa-lib/1.2.7-r0/alsa-lib-1.2.7/include, removed 
"/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/control_remap.c
 /usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/setup.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/ctlparse.c 
/usr/sr
 c/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/control_hw.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/control.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/hcontrol.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/tlv.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/namehint.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/cards.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/control_empty.c 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/src/control/control_local.h 
/usr/src/debug/alsa-lib/1.2.6.1-r0/alsa-lib-1.2.6.1/

[OE-core] [AUH] perl: upgrading to 5.36.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *perl* to *5.36.0* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-perl-upgrade-5.34.1-5.36.0.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-perl-upgrade-5.34.1-5.36.0.patch
Description: Binary data
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...WARNING: 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/perl/perl_5.36.0.bb:
 Unable to get checksum for perl SRC_URI entry encodefix.patch: file could not 
be found
done.
Parsing of 883 .bb files complete (882 cached, 1 parsed). 1642 targets, 36 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 1 recipes from the qemux86 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-693b7126fbef93868d315ed8a4aaa4f4f192378e"
TUNE_FEATURES= "m32 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:693b7126fbef93868d315ed8a4aaa4f4f192378e"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 76 Local 22 Mirrors 0 Missed 54 Current 129 (28% match, 
73% complete)
Removing 5 stale sstate objects for arch core2-32...done.
Removing 16 stale sstate objects for arch qemux86...done.
Removing 10 stale sstate objects for arch x86_64...done.
NOTE: Executing Tasks
NOTE: Running setscene task 139 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/glibc/glibc-locale_2.35.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 142 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/make/make_4.3.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 147 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/libxcrypt/libxcrypt_4.4.28.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 150 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/zlib/zlib_1.2.12.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 156 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/readline/readline_8.1.2.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 157 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-extended/gawk/gawk_5.1.1.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 162 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-support/gdbm/gdbm_1.23.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 171 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.5.0.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 172 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-extended/psmisc/psmisc_23.5.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 177 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 182 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/glibc/glibc_2.35.bb:do_stash_locale_setscene)
NOTE: Running setscene task 183 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/gcc/libgcc_12.1.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 186 of 205 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.16.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene tas

[OE-core] [AUH] sysklogd: upgrading to 2.4.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sysklogd* to *2.4.0* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-sysklogd-upgrade-2.3.0-2.4.0.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/sysklogd: PKGV changed from 2.3.0 [default] to 
2.4.0 [default]
packages/core2-32-poky-linux/sysklogd: PV changed from "2.3.0" to "2.4.0"
packages/core2-32-poky-linux/sysklogd/sysklogd-dbg: PKGSIZE changed from 140460 
to 145164 (+3%)
packages/core2-32-poky-linux/sysklogd/sysklogd-dbg: PKGV changed from 2.3.0 
[default] to 2.4.0 [default]
packages/core2-32-poky-linux/sysklogd/sysklogd-dbg: PV changed from "2.3.0" to 
"2.4.0"
packages/core2-32-poky-linux/sysklogd/sysklogd-dev: PKGV changed from 2.3.0 
[default] to 2.4.0 [default]
packages/core2-32-poky-linux/sysklogd/sysklogd-dev: PV changed from "2.3.0" to 
"2.4.0"
packages/core2-32-poky-linux/sysklogd/sysklogd-doc: PKGSIZE changed from 82417 
to 86560 (+5%)
packages/core2-32-poky-linux/sysklogd/sysklogd-doc: PKGV changed from 2.3.0 
[default] to 2.4.0 [default]
packages/core2-32-poky-linux/sysklogd/sysklogd-doc: PV changed from "2.3.0" to 
"2.4.0"
packages/core2-32-poky-linux/sysklogd/sysklogd-locale: PKGV changed from 2.3.0 
[default] to 2.4.0 [default]
packages/core2-32-poky-linux/sysklogd/sysklogd-locale: PV changed from "2.3.0" 
to "2.4.0"
packages/core2-32-poky-linux/sysklogd/sysklogd-src: PKGSIZE changed from 136715 
to 143372 (+5%)
packages/core2-32-poky-linux/sysklogd/sysklogd-src: PKGV changed from 2.3.0 
[default] to 2.4.0 [default]
packages/core2-32-poky-linux/sysklogd/sysklogd-src: PV changed from "2.3.0" to 
"2.4.0"
packages/core2-32-poky-linux/sysklogd/sysklogd-staticdev: PKGV changed from 
2.3.0 [default] to 2.4.0 [default]
packages/core2-32-poky-linux/sysklogd/sysklogd-staticdev: PV changed from 
"2.3.0" to "2.4.0"
packages/core2-32-poky-linux/sysklogd/sysklogd: PKGSIZE changed from 87356 to 
87805 (+1%)
packages/core2-32-poky-linux/sysklogd/sysklogd: PKGV changed from 2.3.0 
[default] to 2.4.0 [default]
packages/core2-32-poky-linux/sysklogd/sysklogd: PV changed from "2.3.0" to 
"2.4.0"


0001-sysklogd-upgrade-2.3.0-2.4.0.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166410): 
https://lists.openembedded.org/g/openembedded-core/message/166410
Mute This Topic: https://lists.openembedded.org/mt/91480165/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] xwayland: upgrading to 22.1.2 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xwayland* to *22.1.2* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-xwayland-upgrade-22.1.1-22.1.2.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-xwayland-upgrade-22.1.1-22.1.2.patch
Description: Binary data
packages/core2-32-poky-linux/xwayland: SRC_URI changed from 
"https://www.x.org/archive/individual/xserver/xwayland-22.1.1.tar.xz"; to 
"https://www.x.org/archive/individual/xserver/xwayland-22.1.2.tar.xz";
packages/core2-32-poky-linux/xwayland: PV changed from "22.1.1" to "22.1.2"
packages/core2-32-poky-linux/xwayland: PKGV changed from 22.1.1 [default] to 
22.1.2 [default]
packages/core2-32-poky-linux/xwayland/xwayland-dbg: PV changed from "22.1.1" to 
"22.1.2"
packages/core2-32-poky-linux/xwayland/xwayland-dbg: PKGV changed from 22.1.1 
[default] to 22.1.2 [default]
packages/core2-32-poky-linux/xwayland/xwayland-dbg: PKGSIZE changed from 
10261796 to 10262620 (+0%)
packages/core2-32-poky-linux/xwayland/xwayland-dev: PV changed from "22.1.1" to 
"22.1.2"
packages/core2-32-poky-linux/xwayland/xwayland-dev: PKGV changed from 22.1.1 
[default] to 22.1.2 [default]
packages/core2-32-poky-linux/xwayland/xwayland-doc: PV changed from "22.1.1" to 
"22.1.2"
packages/core2-32-poky-linux/xwayland/xwayland-doc: PKGV changed from 22.1.1 
[default] to 22.1.2 [default]
packages/core2-32-poky-linux/xwayland/xwayland-locale: PV changed from "22.1.1" 
to "22.1.2"
packages/core2-32-poky-linux/xwayland/xwayland-locale: PKGV changed from 22.1.1 
[default] to 22.1.2 [default]
packages/core2-32-poky-linux/xwayland/xwayland-src: PV changed from "22.1.1" to 
"22.1.2"
packages/core2-32-poky-linux/xwayland/xwayland-src: PKGV changed from 22.1.1 
[default] to 22.1.2 [default]
packages/core2-32-poky-linux/xwayland/xwayland-src: PKGSIZE changed from 
8589131 to 8590421 (+0%)
packages/core2-32-poky-linux/xwayland/xwayland-staticdev: PV changed from 
"22.1.1" to "22.1.2"
packages/core2-32-poky-linux/xwayland/xwayland-staticdev: PKGV changed from 
22.1.1 [default] to 22.1.2 [default]
packages/core2-32-poky-linux/xwayland/xwayland: PV changed from "22.1.1" to 
"22.1.2"
packages/core2-32-poky-linux/xwayland/xwayland: PKGV changed from 22.1.1 
[default] to 22.1.2 [default]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166420): 
https://lists.openembedded.org/g/openembedded-core/message/166420
Mute This Topic: https://lists.openembedded.org/mt/91480176/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] diffoscope: upgrading to 214 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffoscope* to *214* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-212-214.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-diffoscope-upgrade-212-214.patch
Description: Binary data
packages/core2-32-poky-linux/diffoscope/diffoscope-dbg: PV changed from "212" 
to "214"
packages/core2-32-poky-linux/diffoscope/diffoscope-dbg: PKGV changed from 212 
[default] to 214 [default]
packages/core2-32-poky-linux/diffoscope/diffoscope-dev: PV changed from "212" 
to "214"
packages/core2-32-poky-linux/diffoscope/diffoscope-dev: PKGV changed from 212 
[default] to 214 [default]
packages/core2-32-poky-linux/diffoscope/diffoscope-doc: PV changed from "212" 
to "214"
packages/core2-32-poky-linux/diffoscope/diffoscope-doc: PKGV changed from 212 
[default] to 214 [default]
packages/core2-32-poky-linux/diffoscope/diffoscope-locale: PV changed from 
"212" to "214"
packages/core2-32-poky-linux/diffoscope/diffoscope-locale: PKGV changed from 
212 [default] to 214 [default]
packages/core2-32-poky-linux/diffoscope/diffoscope-src: PV changed from "212" 
to "214"
packages/core2-32-poky-linux/diffoscope/diffoscope-src: PKGV changed from 212 
[default] to 214 [default]
packages/core2-32-poky-linux/diffoscope/diffoscope-staticdev: PV changed from 
"212" to "214"
packages/core2-32-poky-linux/diffoscope/diffoscope-staticdev: PKGV changed from 
212 [default] to 214 [default]
packages/core2-32-poky-linux/diffoscope/diffoscope: PKGSIZE changed from 
1054847 to 1055982 (+0%)
packages/core2-32-poky-linux/diffoscope/diffoscope: PV changed from "212" to 
"214"
packages/core2-32-poky-linux/diffoscope/diffoscope: PKGV changed from 212 
[default] to 214 [default]
packages/core2-32-poky-linux/diffoscope: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/d/diffoscope/diffoscope-212.tar.gz";
 to 
"https://files.pythonhosted.org/packages/source/d/diffoscope/diffoscope-214.tar.gz";
packages/core2-32-poky-linux/diffoscope: PV changed from "212" to "214"
packages/core2-32-poky-linux/diffoscope: PKGV changed from 212 [default] to 214 
[default]
Changes to packages/core2-32-poky-linux/diffoscope (sysroot):
  /usr/lib/python3.10/site-packages/diffoscope-212.dist-info moved to 
/usr/lib/python3.10/site-packages/diffoscope-214.dist-info
Changes to packages/core2-32-poky-linux/diffoscope (sysroot):
  /usr/lib/python3.10/site-packages/diffoscope-212.dist-info moved to 
/usr/lib/python3.10/site-packages/diffoscope-214.dist-info
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (0 cached, 883 parsed). 1643 targets, 49 
skipped, 0 masked, 0 errors.
Removing 100 recipes from the core2-32 sysroot...done.
Removing 120 recipes from the qemux86 sysroot...done.

Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.
/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: Nothing PROVIDES 'diffoscope'
diffoscope was skipped: incompatible with host i686-poky-linux-musl (not in 
COMPATIBLE_HOST)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166426): 
https://lists.openembedded.org/g/openembedded-core/message/166426
Mute This Topic: https://lists.openembedded.org/mt/91480182/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] wayland: upgrading to 1.20.91 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wayland* to *1.20.91* has 
Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade wayland -V 1.20.91
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-3e89c670531fda61c286f0b29d32af99bf47858c"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:3e89c670531fda61c286f0b29d32af99bf47858c"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 21 (100% match, 
100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun 
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 884 .bb files complete (882 cached, 2 parsed). 1643 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-3e89c670531fda61c286f0b29d32af99bf47858c"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:3e89c670531fda61c286f0b29d32af99bf47858c"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 17 (100% match, 
100% complete)
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://wayland.freedesktop.org/releases/wayland-1.20.91.tar.xz, attempting 
MIRRORS if available
NOTE: Tasks Summary: Attempted 82 tasks of which 81 didn't need to be rerun and 
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://wayland.freedesktop.org/releases/wayland-1.20.91.tar.xz...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/";; export 
FTP_PROXY="http://proxy.yocto.io:5187/";; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-bhtqkk5n/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-bhtqkk5n/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-bhtqkk5n/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-bhtqkk5n/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-bhtqkk5n/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-bhtq
 
kk5n/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -P 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads 
'https://wayland.freedesktop.org/releases/wayland-1.20.91.tar.xz' 
--progress=d

[OE-core] [AUH] Upgrade status: 2022-06-01

Recipe upgrade statistics:

* Succeeded: 20
glib-2.0, 2.72.2, Anuj Mittal 
dnf, 4.13.0, Alexander Kanavin 
python3-dtschema, 2022.5, Bruce Ashfield 
python3-numpy, 1.22.4, Oleksandr Kravchuk 

python3-pip, 22.1.2, Zang Ruochen 
python3-sphinx, 5.0.0, Tim Orling 
sysklogd, 2.4.0, Chen Qi 
sysstat, 12.6.0, Chen Qi 
adwaita-icon-theme, 42.0, Ross Burton 
gtk+3, 3.24.34, Ross Burton 
harfbuzz, 4.3.0, Anuj Mittal 
mesa, 22.1.0, Otavio Salvador 
piglit, 1.0-new-commits-available, Ross Burton 
libxkbcommon, 1.4.1, Unassigned 
xwayland, 22.1.2, Unassigned 
alsa-lib, 1.2.7, Michael Opdenacker 
alsa-ucm-conf, 1.2.7, Michael Opdenacker 

webkitgtk, 2.36.3, Alexander Kanavin 
diffoscope, 214, Joshua Watt 
gnutls, 3.7.6, Unassigned 
* Failed(do_compile): 5
ovmf, edk2-stable202205, Ricardo Neri 

cmake, 3.23.2, Pascal Bach 
perl, 5.36.0, Alexander Kanavin 
ltp, 20220527, Yi Zhao 
alsa-utils, 1.2.7, Michael Opdenacker 
* Failed (devtool error): 13
seatd, 0.7.0, Alexander Kanavin 
systemd-boot, 251.1, Chen Qi 
systemd, 251.1, Chen Qi 
btrfs-tools, 5.18, Wang Mingyu 
gnu-config, 20220516-new-commits-available, Robert Yang 

llvm, 14.0.4, Khem Raj 
python3-psutil, 5.9.1, Tim Orling 
libstd-rs, 1.61.0, Randy MacLeod 
rust-llvm, 1.61.0, Randy MacLeod 
procps, 4.0.0, Alexander Kanavin 
wayland, 1.20.91, Denys Dmytriyenko 
tiff, 4.4.0, Alexander Kanavin 
pulseaudio, 16.0, Unassigned 
* Failed(other errors): 2
cargo, 1.61.0, Randy MacLeod 
vulkan-samples, git-new-commits-available, Ross Burton 


TOTAL: attempted=40 succeeded=20(50.00%) failed=20(50.00%)

Recipe upgrade statistics per Maintainer:

Michael Opdenacker 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166423): 
https://lists.openembedded.org/g/openembedded-core/message/166423
Mute This Topic: https://lists.openembedded.org/mt/91480179/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] tiff: upgrading to 4.4.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *tiff* to *4.4.0* has Failed 
(devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe tiff failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-42cb37a941790a20c198fc2d9ca1561deb9a37f7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:42cb37a941790a20c198fc2d9ca1561deb9a37f7"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% match, 
100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 884 .bb files complete (882 cached, 2 parsed). 1643 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-42cb37a941790a20c198fc2d9ca1561deb9a37f7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:42cb37a941790a20c198fc2d9ca1561deb9a37f7"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:  95% |##  | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching http://download.osgeo.org/libtiff/tiff-4.4.0.tar.gz...
INFO: Rebasing devtool onto c5144393c4a6dca08231b705c9d90c9a276e488e
WARNING: Command 'git rebase c5144393c4a6dca08231b705c9d90c9a276e488e' failed:
Auto-merging tools/tiffcrop.c
CONFLICT (content): Merge conflict in tools/tiffcrop.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/tiff
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/tiff/tiff_4.4.0.bb



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166430): 
https://lists.openembedded.org/g/openembedded-core/message/166430
Mute This Topic: https://lists.openembedded.org/mt/91480187/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] sysstat: upgrading to 12.6.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sysstat* to *12.6.0* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-sysstat-upgrade-12.4.5-12.6.0.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/sysstat: SRC_URI changed from 
"http://pagesperso-orange.fr/sebastien.godard/sysstat-12.4.5.tar.xz 
file://99_sysstat file://sysstat.service 
file://0001-configure.in-remove-check-for-chkconfig.patch" to 
"http://pagesperso-orange.fr/sebastien.godard/sysstat-12.6.0.tar.xz 
file://99_sysstat file://sysstat.service 
file://0001-configure.in-remove-check-for-chkconfig.patch"
packages/core2-32-poky-linux/sysstat: PV changed from "12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat: PKGV changed from 12.4.5 [default] to 
12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-dbg: PKGV changed from 12.4.5 
[default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-dbg: PKGSIZE changed from 1822688 
to 1832604 (+1%)
packages/core2-32-poky-linux/sysstat/sysstat-dbg: PV changed from "12.4.5" to 
"12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-dev: PKGV changed from 12.4.5 
[default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-dev: PV changed from "12.4.5" to 
"12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-doc: PKGV changed from 12.4.5 
[default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-doc: PKGSIZE changed from 248562 
to 255443 (+3%)
packages/core2-32-poky-linux/sysstat/sysstat-doc: PV changed from "12.4.5" to 
"12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-doc: FILELIST: removed 
"/usr/share/doc/sysstat/sysstat-12.4.5.lsm", added 
"/usr/share/doc/sysstat/sysstat-12.6.0.lsm"
packages/core2-32-poky-linux/sysstat/sysstat-locale-af: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-af: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-cs: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-cs: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-da: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-da: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-de: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-de: PKGSIZE changed from 
14987 to 15444 (+3%)
packages/core2-32-poky-linux/sysstat/sysstat-locale-de: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-eo: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-eo: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-es: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-es: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-eu: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-eu: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-fi: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-fi: PKGSIZE changed from 
14354 to 15138 (+5%)
packages/core2-32-poky-linux/sysstat/sysstat-locale-fi: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-fr: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-fr: PKGSIZE changed from 
15488 to 16020 (+3%)
packages/core2-32-poky-linux/sysstat/sysstat-locale-fr: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-fur: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-locale-fur: PV changed from 
"12.4.5" to "12.6.0"
packages/core2-32-poky-linux/sysstat/sysstat-locale-gl: PKGV changed from 
12.4.5 [default] to 12.6.0 [default]
packages/core2-32-poky-linux/sysstat/sysstat-local

[OE-core] [AUH] gnutls: upgrading to 3.7.6 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnutls* to *3.7.6* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-gnutls-upgrade-3.7.5-3.7.6.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/gnutls/gnutls-bin: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-bin: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-dbg: PKGSIZE changed from 7541748 to 
7541608 (-0%)
packages/core2-32-poky-linux/gnutls/gnutls-dbg: FILELIST: removed 
"/usr/lib/.debug/libgnutls.so.30.33.0", added 
"/usr/lib/.debug/libgnutls.so.30.33.1"
packages/core2-32-poky-linux/gnutls/gnutls-dbg: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-dbg: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-dev: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-dev: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-doc: PKGSIZE changed from 4381794 to 
4410932 (+1%)
packages/core2-32-poky-linux/gnutls/gnutls-doc: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-doc: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-fips: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-fips: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-cs: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-cs: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-de: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-de: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-eo: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-eo: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-es: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-es: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-fi: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-fi: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-fr: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-fr: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-it: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-it: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-ms: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-ms: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-nl: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-nl: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-pl: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-pl: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-pt-br: PV changed from 
"3.7.5" to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-pt-br: PKGV changed from 
3.7.5 [default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-sr: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-sr: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-sv: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-sv: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-uk: PV changed from "3.7.5" 
to "3.7.6"
packages/core2-32-poky-linux/gnutls/gnutls-locale-uk: PKGV changed from 3.7.5 
[default] to 3

[OE-core] [AUH] alsa-ucm-conf: upgrading to 1.2.7 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *alsa-ucm-conf* to *1.2.7* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-alsa-ucm-conf-upgrade-1.2.6.3-1.2.7.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf-src: PKGV changed from 
1.2.6.3 [default] to 1.2.7 [default]
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf-src: PV changed from 
"1.2.6.3" to "1.2.7"
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: FILELIST: added 
"/usr/share/alsa/ucm2/conf.d/sof-essx8336/sof-essx8336.conf 
/usr/share/alsa/ucm2/USB-Audio/Arturia/Minifuse-2-HiFi.conf 
/usr/share/alsa/ucm2/conf.d/acp6x/acp6x.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4.conf 
/usr/share/alsa/ucm2/USB-Audio/Steinberg/UR44.conf 
/usr/share/alsa/ucm2/common/ctl/remap.conf 
/usr/share/alsa/ucm2/USB-Audio/Steinberg/UR44-HiFi.conf 
/usr/share/alsa/ucm2/USB-Audio/Behringer/UMC204HD.conf 
/usr/share/alsa/ucm2/common/pcm/split.conf 
/usr/share/alsa/ucm2/Intel/sof-essx8336/sof-essx8336.conf 
/usr/share/alsa/ucm2/USB-Audio/Behringer/UMC204HD-HiFi.conf 
/usr/share/alsa/ucm2/USB-Audio/Realtek/ALC4080.conf 
/usr/share/alsa/ucm2/Intel/sof-essx8336/HiFi.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi.conf 
/usr/share/alsa/ucm2/Intel/sof-essx8336/Hdmi.conf 
/usr/share/alsa/ucm2/common/direct.conf 
/usr/share/alsa/ucm2/conf.d/simple-card/rockchip,es8316-codec.conf 
/usr/share/alsa/ucm2/U
 SB-Audio/Arturia/Minifuse-2.conf /usr/share/alsa/ucm2/common/direct-verb.conf 
/usr/share/alsa/ucm2/USB-Audio/Realtek/ALC4080-HiFi.conf"
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: PKGV changed from 1.2.6.3 
[default] to 1.2.7 [default]
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: PKGSIZE changed from 
210719 to 237379 (+13%)
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: PV changed from "1.2.6.3" 
to "1.2.7"
packages/all-poky-linux/alsa-ucm-conf: PKGV changed from 1.2.6.3 [default] to 
1.2.7 [default]
packages/all-poky-linux/alsa-ucm-conf: SRC_URI changed from 
"https://www.alsa-project.org/files/pub/lib/alsa-ucm-conf-1.2.6.3.tar.bz2"; to 
"https://www.alsa-project.org/files/pub/lib/alsa-ucm-conf-1.2.7.tar.bz2";
packages/all-poky-linux/alsa-ucm-conf: PV changed from "1.2.6.3" to "1.2.7"
Changes to packages/all-poky-linux/alsa-ucm-conf (sysroot):
  /usr/share/alsa/ucm2/common/ctl was added
  /usr/share/alsa/ucm2/common/ctl/remap.conf was added
  /usr/share/alsa/ucm2/common/direct.conf was added
  /usr/share/alsa/ucm2/common/direct-verb.conf was added
  /usr/share/alsa/ucm2/common/pcm was added
  /usr/share/alsa/ucm2/common/pcm/split.conf was added
  /usr/share/alsa/ucm2/conf.d/acp6x was added
  /usr/share/alsa/ucm2/conf.d/acp6x/acp6x.conf was added
  /usr/share/alsa/ucm2/conf.d/simple-card/rockchip,es8316-codec.conf was added
  /usr/share/alsa/ucm2/conf.d/sof-essx8336 was added
  /usr/share/alsa/ucm2/conf.d/sof-essx8336/sof-essx8336.conf was added
  /usr/share/alsa/ucm2/Intel/sof-essx8336 was added
  /usr/share/alsa/ucm2/Intel/sof-essx8336/Hdmi.conf was added
  /usr/share/alsa/ucm2/Intel/sof-essx8336/HiFi.conf was added
  /usr/share/alsa/ucm2/Intel/sof-essx8336/sof-essx8336.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Arturia was added
  /usr/share/alsa/ucm2/USB-Audio/Arturia/Minifuse-2.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Arturia/Minifuse-2-HiFi.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Behringer was added
  /usr/share/alsa/ucm2/USB-Audio/Behringer/UMC204HD.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Behringer/UMC204HD-HiFi.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Realtek/ALC4080.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Realtek/ALC4080-HiFi.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Steinberg was added
  /usr/share/alsa/ucm2/USB-Audio/Steinberg/UR44.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Steinberg/UR44-HiFi.conf was added
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: PKGSIZE changed from 
210719 to 237379 (+13%)
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: FILELIST: ad

[OE-core] [AUH] pulseaudio: upgrading to 16.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *pulseaudio* to *16.0* has 
Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe pulseaudio failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-42cb37a941790a20c198fc2d9ca1561deb9a37f7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:42cb37a941790a20c198fc2d9ca1561deb9a37f7"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 21 (100% match, 
100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun 
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 884 .bb files complete (882 cached, 2 parsed). 1643 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-42cb37a941790a20c198fc2d9ca1561deb9a37f7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:42cb37a941790a20c198fc2d9ca1561deb9a37f7"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 17 (100% match, 
100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 83 tasks of which 81 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:  53% |### | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:00
INFO: Extracting current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching 
http://freedesktop.org/software/pulseaudio/releases/pulseaudio-16.0.tar.xz...
INFO: Rebasing devtool onto f8cc45f5977d951bd45fa62accd282f4ed1175ae
WARNING: Command 'git rebase f8cc45f5977d951bd45fa62accd282f4ed1175ae' failed:
Auto-merging meson.build
CONFLICT (content): Merge conflict in meson.build

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/pulseaudio
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/pulseaudio/pulseaudio_16.0.bb



Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166428): 
https://lists.openembedded.org/g/openembedded-core/message/166428
Mute This Topic: https://lists.openembedded.org/mt/91480185/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] alsa-utils: upgrading to 1.2.7 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *alsa-utils* to *1.2.7* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-alsa-utils-upgrade-1.2.6-1.2.7.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-alsa-utils-upgrade-1.2.6-1.2.7.patch
Description: Binary data
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1642 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (881 cached, 2 parsed). 1642 targets, 36 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 1 recipes from the qemux86 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-b3f6b1acb302d2ad3b22bbb70b9ceeb5c49a1a9a"
TUNE_FEATURES= "m32 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:b3f6b1acb302d2ad3b22bbb70b9ceeb5c49a1a9a"
workspace= "master:95066dde6861ee08fdb505ab3e0422156cc24fae"

Initialising tasks...done.
Sstate summary: Wanted 115 Local 107 Mirrors 0 Missed 8 Current 302 (93% match, 
98% complete)
Removing 1 stale sstate objects for arch core2-32...done.
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 1293 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_fetch)
NOTE: recipe alsa-utils-1.2.7-r0: task do_fetch: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_fetch: Succeeded
NOTE: Running task 1493 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_unpack)
NOTE: Running task 1494 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_prepare_recipe_sysroot)
NOTE: recipe alsa-utils-1.2.7-r0: task do_unpack: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_unpack: Succeeded
NOTE: Running task 1495 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_patch)
NOTE: recipe alsa-utils-1.2.7-r0: task do_patch: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_patch: Succeeded
NOTE: Running task 1496 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_deploy_source_date_epoch)
NOTE: Running task 1497 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_populate_lic)
NOTE: recipe alsa-utils-1.2.7-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: recipe alsa-utils-1.2.7-r0: task do_deploy_source_date_epoch: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_populate_lic: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_populate_lic: Succeeded
NOTE: recipe alsa-utils-1.2.7-r0: task do_deploy_source_date_epoch: Succeeded
NOTE: Running task 1498 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_configure)
NOTE: recipe alsa-utils-1.2.7-r0: task do_configure: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_configure: Succeeded
NOTE: Running task 1499 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_compile)
NOTE: recipe alsa-utils-1.2.7-r0: task do_compile: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_compile: Succeeded
NOTE: Running task 1500 of 1507 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-multimedia/alsa/alsa-utils_1.2.7.bb:do_install)
NOTE: recipe alsa-utils-1.2.7-r0: task do_install: Started
NOTE: recipe alsa-utils-1.2.7-r0: task do_install: Succeeded
NOTE: Running task 1501 of 1507 
(/home/pokybuild

Re: [OE-core] [kirkstone][PATCH 1/2] gcc: Upgrade to 11.3 release

On Wed, Jun 1, 2022 at 6:10 AM Richard Purdie
 wrote:
>
> On Wed, 2022-06-01 at 05:29 -1000, Steve Sakoman wrote:
> > On Wed, Jun 1, 2022 at 12:10 AM Martin Jansa  wrote:
> > >
> > > As discussed on IRC yesterday I've tried to reproduce this failure 
> > > locally and it works fine with poky master cee443ae75f (last commit in 
> > > master before the upgrade to 12.1)
> > > 2022-06-01 09:46:37,051 - oe-selftest - INFO - RESULTS - 
> > > reproducible.ReproducibleTests.test_reproducible_builds: PASSED (6429.19s)
> > > and now it passed with kirkstone as well:
> > >
> > > poky $ git cherry-pick 44a36caa7c2
> > > Auto-merging meta/conf/distro/include/maintainers.inc
> > > [jansa/kirkstone-gcc-11.3 5c6e280eed5] gcc: Upgrade to 11.3 release
> > > ...
> > > poky $ oe-selftest -r reproducible 2>&1 | tee 
> > > log.oe-selftest.reproducible.kirkstone
> > > 2022-06-01 09:51:31,653 - oe-selftest - INFO - Changing cwd to 
> > > /OE/build/poky/build
> > > 2022-06-01 09:51:31,653 - oe-selftest - INFO - Adding layer libraries:
> > > 2022-06-01 09:51:31,653 - oe-selftest - INFO -  
> > > /OE/build/poky/meta-poky/lib
> > > 2022-06-01 09:51:31,653 - oe-selftest - INFO -  /OE/build/poky/meta/lib
> > > 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> > > /OE/build/poky/meta-yocto-bsp/lib
> > > 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> > > /OE/build/poky/meta-selftest/lib
> > > 2022-06-01 09:51:31,655 - oe-selftest - INFO - Running bitbake -e to test 
> > > the configuration is valid/parsable
> > > hint: Using 'master' as the name for the initial branch. This default 
> > > branch name
> > > hint: is subject to change. To configure the initial branch name to use 
> > > in all
> > > hint: of your new repositories, which will suppress this warning, call:
> > > hint:
> > > hint:   git config --global init.defaultBranch 
> > > hint:
> > > hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
> > > hint: 'development'. The just-created branch can be renamed via this 
> > > command:
> > > hint:
> > > hint:   git branch -m 
> > > 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include 
> > > selftest.inc" in /OE/build/poky/build-st/conf/local.conf
> > > 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include 
> > > bblayers.inc" in bblayers.conf
> > > 2022-06-01 09:51:37,092 - oe-selftest - INFO - test_diffoscope 
> > > (reproducible.DiffoscopeTests)
> > > 2022-06-01 10:08:42,982 - oe-selftest - INFO -  ... ok
> > > 2022-06-01 10:08:42,983 - oe-selftest - INFO - test_reproducible_builds 
> > > (reproducible.ReproducibleTests)
> > > 2022-06-01 10:09:56,114 - oe-selftest - INFO - Building reproducibleA 
> > > (sstate allowed)...
> > > ^Ap2022-06-01 11:11:09,785 - oe-selftest - INFO - Building reproducibleB 
> > > (sstate NOT allowed)...
> > > 2022-06-01 11:55:00,507 - oe-selftest - INFO - Checking deb packages for 
> > > differences...
> > > 2022-06-01 11:55:00,946 - oe-selftest - INFO - Reproducibility summary 
> > > for deb: same=139 different=0 different_excluded=0 missing=0 total=139
> > > unused_exclusions=[]
> > > 2022-06-01 11:55:00,946 - oe-selftest - INFO - Checking ipk packages for 
> > > differences...
> > > 2022-06-01 11:55:01,330 - oe-selftest - INFO - Reproducibility summary 
> > > for ipk: same=139 different=0 different_excluded=0 missing=0 total=139
> > > unused_exclusions=[]
> > > 2022-06-01 11:55:01,331 - oe-selftest - INFO - Checking rpm packages for 
> > > differences...
> > > 2022-06-01 11:55:01,760 - oe-selftest - INFO - Reproducibility summary 
> > > for rpm: same=139 different=0 different_excluded=0 missing=0 total=139
> > > unused_exclusions=[]
> > > 2022-06-01 11:55:01,760 - oe-selftest - INFO -  ... ok
> > > 2022-06-01 11:56:29,573 - oe-selftest - INFO - 
> > > --
> > > 2022-06-01 11:56:29,573 - oe-selftest - INFO - Ran 2 tests in 7495.224s
> > > 2022-06-01 11:56:29,573 - oe-selftest - INFO - OK
> > > 2022-06-01 11:56:31,723 - oe-selftest - INFO - RESULTS:
> > > 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> > > reproducible.DiffoscopeTests.test_diffoscope: PASSED (1025.89s)
> > > 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> > > reproducible.ReproducibleTests.test_reproducible_builds: PASSED (6378.78s)
> > > 2022-06-01 11:56:31,881 - oe-selftest - INFO - SUMMARY:
> > > 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest () - Ran 2 
> > > tests in 7495.225s
> > > 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest - OK - All 
> > > required tests passed (successes=2, skipped=0, failures=0, errors=0)
> > >
> > > Is it possible that the reproducibility failure was caused by something 
> > > else included in your run on autobuilder?
> >
> > It is quite possible that it is host distro specific, I've seen that
> > quite often in the past.  Let me know which distro you used for your
> > test and I'll try the same on the autobuilder.
>
> Keep in mind that the test us

Re: [OE-core] [kirkstone][PATCH 1/2] gcc: Upgrade to 11.3 release

2022-06-01 Thread Khem Raj

does it use objdump from host ?

On Wed, Jun 1, 2022 at 9:21 AM Steve Sakoman  wrote:
>
> On Wed, Jun 1, 2022 at 6:10 AM Richard Purdie
>  wrote:
> >
> > On Wed, 2022-06-01 at 05:29 -1000, Steve Sakoman wrote:
> > > On Wed, Jun 1, 2022 at 12:10 AM Martin Jansa  
> > > wrote:
> > > >
> > > > As discussed on IRC yesterday I've tried to reproduce this failure 
> > > > locally and it works fine with poky master cee443ae75f (last commit in 
> > > > master before the upgrade to 12.1)
> > > > 2022-06-01 09:46:37,051 - oe-selftest - INFO - RESULTS - 
> > > > reproducible.ReproducibleTests.test_reproducible_builds: PASSED 
> > > > (6429.19s)
> > > > and now it passed with kirkstone as well:
> > > >
> > > > poky $ git cherry-pick 44a36caa7c2
> > > > Auto-merging meta/conf/distro/include/maintainers.inc
> > > > [jansa/kirkstone-gcc-11.3 5c6e280eed5] gcc: Upgrade to 11.3 release
> > > > ...
> > > > poky $ oe-selftest -r reproducible 2>&1 | tee 
> > > > log.oe-selftest.reproducible.kirkstone
> > > > 2022-06-01 09:51:31,653 - oe-selftest - INFO - Changing cwd to 
> > > > /OE/build/poky/build
> > > > 2022-06-01 09:51:31,653 - oe-selftest - INFO - Adding layer libraries:
> > > > 2022-06-01 09:51:31,653 - oe-selftest - INFO -  
> > > > /OE/build/poky/meta-poky/lib
> > > > 2022-06-01 09:51:31,653 - oe-selftest - INFO -  /OE/build/poky/meta/lib
> > > > 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> > > > /OE/build/poky/meta-yocto-bsp/lib
> > > > 2022-06-01 09:51:31,654 - oe-selftest - INFO -  
> > > > /OE/build/poky/meta-selftest/lib
> > > > 2022-06-01 09:51:31,655 - oe-selftest - INFO - Running bitbake -e to 
> > > > test the configuration is valid/parsable
> > > > hint: Using 'master' as the name for the initial branch. This default 
> > > > branch name
> > > > hint: is subject to change. To configure the initial branch name to use 
> > > > in all
> > > > hint: of your new repositories, which will suppress this warning, call:
> > > > hint:
> > > > hint:   git config --global init.defaultBranch 
> > > > hint:
> > > > hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
> > > > hint: 'development'. The just-created branch can be renamed via this 
> > > > command:
> > > > hint:
> > > > hint:   git branch -m 
> > > > 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include 
> > > > selftest.inc" in /OE/build/poky/build-st/conf/local.conf
> > > > 2022-06-01 09:51:37,091 - oe-selftest - INFO - Adding: "include 
> > > > bblayers.inc" in bblayers.conf
> > > > 2022-06-01 09:51:37,092 - oe-selftest - INFO - test_diffoscope 
> > > > (reproducible.DiffoscopeTests)
> > > > 2022-06-01 10:08:42,982 - oe-selftest - INFO -  ... ok
> > > > 2022-06-01 10:08:42,983 - oe-selftest - INFO - test_reproducible_builds 
> > > > (reproducible.ReproducibleTests)
> > > > 2022-06-01 10:09:56,114 - oe-selftest - INFO - Building reproducibleA 
> > > > (sstate allowed)...
> > > > ^Ap2022-06-01 11:11:09,785 - oe-selftest - INFO - Building 
> > > > reproducibleB (sstate NOT allowed)...
> > > > 2022-06-01 11:55:00,507 - oe-selftest - INFO - Checking deb packages 
> > > > for differences...
> > > > 2022-06-01 11:55:00,946 - oe-selftest - INFO - Reproducibility summary 
> > > > for deb: same=139 different=0 different_excluded=0 missing=0 total=139
> > > > unused_exclusions=[]
> > > > 2022-06-01 11:55:00,946 - oe-selftest - INFO - Checking ipk packages 
> > > > for differences...
> > > > 2022-06-01 11:55:01,330 - oe-selftest - INFO - Reproducibility summary 
> > > > for ipk: same=139 different=0 different_excluded=0 missing=0 total=139
> > > > unused_exclusions=[]
> > > > 2022-06-01 11:55:01,331 - oe-selftest - INFO - Checking rpm packages 
> > > > for differences...
> > > > 2022-06-01 11:55:01,760 - oe-selftest - INFO - Reproducibility summary 
> > > > for rpm: same=139 different=0 different_excluded=0 missing=0 total=139
> > > > unused_exclusions=[]
> > > > 2022-06-01 11:55:01,760 - oe-selftest - INFO -  ... ok
> > > > 2022-06-01 11:56:29,573 - oe-selftest - INFO - 
> > > > --
> > > > 2022-06-01 11:56:29,573 - oe-selftest - INFO - Ran 2 tests in 7495.224s
> > > > 2022-06-01 11:56:29,573 - oe-selftest - INFO - OK
> > > > 2022-06-01 11:56:31,723 - oe-selftest - INFO - RESULTS:
> > > > 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> > > > reproducible.DiffoscopeTests.test_diffoscope: PASSED (1025.89s)
> > > > 2022-06-01 11:56:31,724 - oe-selftest - INFO - RESULTS - 
> > > > reproducible.ReproducibleTests.test_reproducible_builds: PASSED 
> > > > (6378.78s)
> > > > 2022-06-01 11:56:31,881 - oe-selftest - INFO - SUMMARY:
> > > > 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest () - Ran 2 
> > > > tests in 7495.225s
> > > > 2022-06-01 11:56:31,881 - oe-selftest - INFO - oe-selftest - OK - All 
> > > > required tests passed (successes=2, skipped=0, failures=0, errors=0)
> > > >
> > > > Is it possible that the reproducibility failure was caused by so

Re: [OE-core] [kirkstone][PATCH 1/2] gcc: Upgrade to 11.3 release

On Wed, 2022-06-01 at 06:21 -1000, Steve Sakoman wrote:
> On Wed, Jun 1, 2022 at 6:10 AM Richard Purdie
>  wrote:
> > 
> > On Wed, 2022-06-01 at 05:29 -1000, Steve Sakoman wrote:
> > 
> > 
> > Keep in mind that the test uses sstate to compare against so even that
> > isn't a guarantee of identifying the issue.
> > 
> > Did you try the strings comparison I suggested? Do you have the file
> > section tables comparison (diff) I could look at?
> 
> Are you referring to the section header info from objdump -h ?
> 
> If so I've attached the a/b info, they are quite compact.

Yes, I couldn't remember the option to objdump offhand. The diff looks
like:

--- /tmp/headersa.txt   2022-06-01 17:22:57.272277627 +0100
+++ /tmp/headersb.txt   2022-06-01 17:22:43.972218408 +0100
@@ -1,5 +1,5 @@
 
-a/usr/lib/libwebkit2gtk-4.0.so.37.56.5: file format elf64-x86-64
+b/usr/lib/libwebkit2gtk-4.0.so.37.56.5: file format elf64-x86-64
 
 Sections:
 Idx Name  Size  VMA   LMA   File off  Algn
@@ -63,15 +63,15 @@
   CONTENTS, READONLY, DEBUGGING, OCTETS
  29 .debug_abbrev 00c6ce64      921c9968  2**0
   CONTENTS, READONLY, DEBUGGING, OCTETS
- 30 .debug_line   09025ee1      92e367cc  2**0
+ 30 .debug_line   09025ede      92e367cc  2**0
   CONTENTS, READONLY, DEBUGGING, OCTETS
- 31 .debug_str1820ba50      9be5c6ad  2**0
+ 31 .debug_str1820ba50      9be5c6aa  2**0
   CONTENTS, READONLY, DEBUGGING, OCTETS
- 32 .debug_line_str 0005d9f4      b40680fd  
2**0
+ 32 .debug_line_str 0005d9f4      b40680fa  
2**0
   CONTENTS, READONLY, DEBUGGING, OCTETS
- 33 .debug_loclists 13d74aa2      b40c5af1  
2**0
+ 33 .debug_loclists 13d74aa0      b40c5aee  
2**0
   CONTENTS, READONLY, DEBUGGING, OCTETS
- 34 .debug_rnglists 034c6c08      c7e3a593  
2**0
+ 34 .debug_rnglists 034c6bf6      c7e3a58e  
2**0
   CONTENTS, READONLY, DEBUGGING, OCTETS
- 35 .gnu_debuglink 0024      cb30119c  2**2
+ 35 .gnu_debuglink 0024      cb301184  2**2
   CONTENTS, READONLY

I'm a bit puzzled since usually the debug symbols are moved off to the
-dbg package and yet they seem combined here with the library. What the
above seems to say is that the debug_line, loclists and rnglists
sections changed size, the rest changed offset (and we ignore
gnu_debuglink since that is a checksum which would depend on the other
bits).

That would imply that some piece of code used to compile webkit has
different line numbering on one system compared to another but
generates identical code. You should be able to parse the debuginfo to
get a filename and linenumber out of it but I can't remember how, I
think I learnt to read dwarfish last time I did this :/.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166435): 
https://lists.openembedded.org/g/openembedded-core/message/166435
Mute This Topic: https://lists.openembedded.org/mt/91339755/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [oe-core][PATCH v3 2/2] libavtp: add recipe to be able to use aaf config for alsa-plugins

2022-06-01 Thread Max Krummenacher

On Wed, Jun 1, 2022 at 5:14 PM Marcel Ziswiler  wrote:
>
> On Wed, 2022-06-01 at 15:48 +0200, Luca Ceresoli wrote:
> > Hi Marcel,
> >
> > On Tue, 31 May 2022 23:32:06 +0200
> > "Marcel Ziswiler"  wrote:
> >
> > > From: Peter Bergin 
> > >
> > > In order to enable configuration option aaf (AVTP Audio Format)
> > > used for AVB the library libavtp is a dependency but no recipe for
> > > this library was present. aaf support for alsa-plugins was
> > > introduced in ddf5421331180bc45697511b44cdd4a4e6dda6ff.
> > >
> > > Signed-off-by: Peter Bergin 
> > > Signed-off-by: Marcel Ziswiler 
> >
> > This patch is failing on musl builds:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5308/steps/11/logs/stdio
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5294/steps/12/logs/stdio
>
> To be honest, I don't know nothing about musl and will need to get familiar 
> with that topic first. If anybody
> has some suggestions that would be highly appreciated. Thanks!
>
> Cheers
>
> Marcel
>
I have the patch ready for Marcel. So with the move to
meta-openembedded the recipe will also build with musl.
Max

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166436): 
https://lists.openembedded.org/g/openembedded-core/message/166436
Mute This Topic: https://lists.openembedded.org/mt/91462033/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH 1/2] gcc: Upgrade to 11.3 release

On Wed, Jun 1, 2022 at 6:32 AM Richard Purdie
 wrote:
>
> On Wed, 2022-06-01 at 06:21 -1000, Steve Sakoman wrote:
> > On Wed, Jun 1, 2022 at 6:10 AM Richard Purdie
> >  wrote:
> > >
> > > On Wed, 2022-06-01 at 05:29 -1000, Steve Sakoman wrote:
> > >
> > >
> > > Keep in mind that the test uses sstate to compare against so even that
> > > isn't a guarantee of identifying the issue.
> > >
> > > Did you try the strings comparison I suggested? Do you have the file
> > > section tables comparison (diff) I could look at?
> >
> > Are you referring to the section header info from objdump -h ?
> >
> > If so I've attached the a/b info, they are quite compact.
>
> Yes, I couldn't remember the option to objdump offhand. The diff looks
> like:
>
> --- /tmp/headersa.txt   2022-06-01 17:22:57.272277627 +0100
> +++ /tmp/headersb.txt   2022-06-01 17:22:43.972218408 +0100
> @@ -1,5 +1,5 @@
>
> -a/usr/lib/libwebkit2gtk-4.0.so.37.56.5: file format elf64-x86-64
> +b/usr/lib/libwebkit2gtk-4.0.so.37.56.5: file format elf64-x86-64
>
>  Sections:
>  Idx Name  Size  VMA   LMA   File off  
> Algn
> @@ -63,15 +63,15 @@
>CONTENTS, READONLY, DEBUGGING, OCTETS
>   29 .debug_abbrev 00c6ce64      921c9968  
> 2**0
>CONTENTS, READONLY, DEBUGGING, OCTETS
> - 30 .debug_line   09025ee1      92e367cc  
> 2**0
> + 30 .debug_line   09025ede      92e367cc  
> 2**0
>CONTENTS, READONLY, DEBUGGING, OCTETS
> - 31 .debug_str1820ba50      9be5c6ad  
> 2**0
> + 31 .debug_str1820ba50      9be5c6aa  
> 2**0
>CONTENTS, READONLY, DEBUGGING, OCTETS
> - 32 .debug_line_str 0005d9f4      b40680fd  
> 2**0
> + 32 .debug_line_str 0005d9f4      b40680fa  
> 2**0
>CONTENTS, READONLY, DEBUGGING, OCTETS
> - 33 .debug_loclists 13d74aa2      b40c5af1  
> 2**0
> + 33 .debug_loclists 13d74aa0      b40c5aee  
> 2**0
>CONTENTS, READONLY, DEBUGGING, OCTETS
> - 34 .debug_rnglists 034c6c08      c7e3a593  
> 2**0
> + 34 .debug_rnglists 034c6bf6      c7e3a58e  
> 2**0
>CONTENTS, READONLY, DEBUGGING, OCTETS
> - 35 .gnu_debuglink 0024      cb30119c  
> 2**2
> + 35 .gnu_debuglink 0024      cb301184  
> 2**2
>CONTENTS, READONLY
>
> I'm a bit puzzled since usually the debug symbols are moved off to the
> -dbg package and yet they seem combined here with the library. What the
> above seems to say is that the debug_line, loclists and rnglists
> sections changed size, the rest changed offset (and we ignore
> gnu_debuglink since that is a checksum which would depend on the other
> bits).
>
> That would imply that some piece of code used to compile webkit has
> different line numbering on one system compared to another but
> generates identical code. You should be able to parse the debuginfo to
> get a filename and linenumber out of it but I can't remember how, I
> think I learnt to read dwarfish last time I did this :/.

I did a dump of the debug sections with objdump -g and got absolutely
huge output files that crashed all of the diff programs I tried.

I guess the next step is to split those files into smaller chunks and
diff those :-(

Have I mentioned how much I hate webkit-gtk?

Steve

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166437): 
https://lists.openembedded.org/g/openembedded-core/message/166437
Mute This Topic: https://lists.openembedded.org/mt/91339755/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] populate_sdk_ext: Fix race condition on bb_unihashes.dat

There is a race were the bb_unihashes.dat file may end up zero sized due to
concurrent builds. Use recently added API within bitbake to copy the file
safely. Also use the opportunity to remove hardcoded filepaths internal to
bitbake from OE-Core.

Bump the minimum bitbake version to match the API being used.

Signed-off-by: Richard Purdie 
---
 meta/classes/populate_sdk_ext.bbclass | 6 ++
 meta/conf/sanity.conf | 2 +-
 2 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/meta/classes/populate_sdk_ext.bbclass 
b/meta/classes/populate_sdk_ext.bbclass
index e2019f9bbf7..926587c3564 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -401,10 +401,8 @@ python copy_buildsystem () {
 if os.path.exists(builddir + dest_stub):
 shutil.copyfile(builddir + dest_stub, baseoutpath + dest_stub)
 
-if os.path.exists(builddir + '/cache/bb_unihashes.dat'):
-bb.parse.siggen.save_unitaskhashes()
-bb.utils.mkdirhier(os.path.join(baseoutpath, 'cache'))
-shutil.copyfile(builddir + '/cache/bb_unihashes.dat', baseoutpath + 
'/cache/bb_unihashes.dat')
+cachedir = os.path.join(baseoutpath, 'cache')
+bb.parse.siggen.copy_unitaskhashes(cachedir)
 
 # If PR Service is in use, we need to export this as well
 bb.note('Do we have a pr database?')
diff --git a/meta/conf/sanity.conf b/meta/conf/sanity.conf
index e6cb2b45fe2..fff1ad8246b 100644
--- a/meta/conf/sanity.conf
+++ b/meta/conf/sanity.conf
@@ -3,7 +3,7 @@
 # See sanity.bbclass
 #
 # Expert users can confirm their sanity with "touch conf/sanity.conf"
-BB_MIN_VERSION = "1.53.1"
+BB_MIN_VERSION = "2.0.1"
 
 SANITY_ABIFILE = "${TMPDIR}/abi_version"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166438): 
https://lists.openembedded.org/g/openembedded-core/message/166438
Mute This Topic: https://lists.openembedded.org/mt/91483007/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 1/2] files: rootfs-postcommands: move helper commands to script

2022-06-01 Thread Vyacheslav Yurkov

From: Vyacheslav Yurkov 

OverlayFS systemd helper unit might require more pre-processing
commands. It gets more complicated to embed them in a unit file, because
systemd shell subset is limited and might require additional escaping.
Move the command to a separate script, thus simplifying systemd unit.

Signed-off-by: Vyacheslav Yurkov 
---
 meta/classes/rootfs-postcommands.bbclass| 13 -
 meta/files/overlayfs-create-dirs.service.in |  3 +--
 meta/files/overlayfs-create-dirs.sh |  8 
 3 files changed, 21 insertions(+), 3 deletions(-)
 create mode 100644 meta/files/overlayfs-create-dirs.sh

diff --git a/meta/classes/rootfs-postcommands.bbclass 
b/meta/classes/rootfs-postcommands.bbclass
index d302c23cf4..3f9fdb602d 100644
--- a/meta/classes/rootfs-postcommands.bbclass
+++ b/meta/classes/rootfs-postcommands.bbclass
@@ -39,7 +39,7 @@ ROOTFS_POSTPROCESS_COMMAND += 
'${@bb.utils.contains("DISTRO_FEATURES", "systemd"
 
 ROOTFS_POSTPROCESS_COMMAND += 'empty_var_volatile;'
 
-ROOTFS_POSTPROCESS_COMMAND += '${@bb.utils.contains("DISTRO_FEATURES", 
"overlayfs", "overlayfs_qa_check;", "", d)}'
+ROOTFS_POSTPROCESS_COMMAND += '${@bb.utils.contains("DISTRO_FEATURES", 
"overlayfs", "overlayfs_qa_check; overlayfs_postprocess;", "", d)}'
 
 inherit image-artifact-names
 
@@ -422,3 +422,14 @@ python overlayfs_qa_check() {
 if not allUnitExist:
 bb.fatal('Not all mount paths and units are installed in the image')
 }
+
+python overlayfs_postprocess() {
+import shutil
+
+# install helper script
+helperScriptName = "overlayfs-create-dirs.sh"
+helperScriptSource = oe.path.join(d.getVar("COREBASE"), "meta/files", 
helperScriptName)
+helperScriptDest = oe.path.join(d.getVar("IMAGE_ROOTFS"), "/usr/sbin/", 
helperScriptName)
+shutil.copyfile(helperScriptSource, helperScriptDest)
+os.chmod(helperScriptDest, 0o755)
+}
diff --git a/meta/files/overlayfs-create-dirs.service.in 
b/meta/files/overlayfs-create-dirs.service.in
index 61b2b9321b..c949a6dc73 100644
--- a/meta/files/overlayfs-create-dirs.service.in
+++ b/meta/files/overlayfs-create-dirs.service.in
@@ -6,8 +6,7 @@ DefaultDependencies=no
 
 [Service]
 Type=oneshot
-ExecStart=mkdir -p {DATA_MOUNT_POINT}/upper{LOWERDIR}
-ExecStart=mkdir -p {DATA_MOUNT_POINT}/workdir{LOWERDIR}
+ExecStart=/usr/sbin/overlayfs-create-dirs.sh {LOWERDIR} {DATA_MOUNT_POINT}
 RemainAfterExit=true
 StandardOutput=journal
 
diff --git a/meta/files/overlayfs-create-dirs.sh 
b/meta/files/overlayfs-create-dirs.sh
new file mode 100644
index 00..06c7587a6b
--- /dev/null
+++ b/meta/files/overlayfs-create-dirs.sh
@@ -0,0 +1,8 @@
+#!/bin/sh
+# This script is intended to be used sorely by overlayfs-create-dirs.service
+# Usage: overlayfs-create-dirs.sh  
+
+lowerdir=$1
+datamountpoint=$2
+mkdir -p ${datamountpoint}/upper${lowerdir}
+mkdir -p ${datamountpoint}/workdir${lowerdir}
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166439): 
https://lists.openembedded.org/g/openembedded-core/message/166439
Mute This Topic: https://lists.openembedded.org/mt/91484585/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/2] files: respect overlayfs owner from lower layer

2022-06-01 Thread Vyacheslav Yurkov

From: Vyacheslav Yurkov 

Permission model of overlayfs uses permissions/ownership from the upper
layer after mounting. Fix up UID/GID of the upper layer, when lower
layer already uses something custom.

Signed-off-by: Vyacheslav Yurkov 
---
 meta/files/overlayfs-create-dirs.sh | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/files/overlayfs-create-dirs.sh 
b/meta/files/overlayfs-create-dirs.sh
index 06c7587a6b..9954c34352 100644
--- a/meta/files/overlayfs-create-dirs.sh
+++ b/meta/files/overlayfs-create-dirs.sh
@@ -6,3 +6,6 @@ lowerdir=$1
 datamountpoint=$2
 mkdir -p ${datamountpoint}/upper${lowerdir}
 mkdir -p ${datamountpoint}/workdir${lowerdir}
+if [ -d "$lowerdir" ]; then
+chown $(stat -c "%U:%G" ${lowerdir}) ${datamountpoint}/upper${lowerdir}
+fi
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166440): 
https://lists.openembedded.org/g/openembedded-core/message/166440
Mute This Topic: https://lists.openembedded.org/mt/91484586/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH 1/2] gcc: Upgrade to 11.3 release

On Wed, 2022-06-01 at 07:01 -1000, Steve Sakoman wrote:
> On Wed, Jun 1, 2022 at 6:32 AM Richard Purdie
>  wrote:
> > 
> > On Wed, 2022-06-01 at 06:21 -1000, Steve Sakoman wrote:
> > > On Wed, Jun 1, 2022 at 6:10 AM Richard Purdie
> > >  wrote:
> > > > 
> > > > On Wed, 2022-06-01 at 05:29 -1000, Steve Sakoman wrote:
> > > > 
> > > > 
> > > > Keep in mind that the test uses sstate to compare against so even that
> > > > isn't a guarantee of identifying the issue.
> > > > 
> > > > Did you try the strings comparison I suggested? Do you have the file
> > > > section tables comparison (diff) I could look at?
> > > 
> > > Are you referring to the section header info from objdump -h ?
> > > 
> > > If so I've attached the a/b info, they are quite compact.
> > 
> > Yes, I couldn't remember the option to objdump offhand. The diff looks
> > like:
> > 
> > --- /tmp/headersa.txt   2022-06-01 17:22:57.272277627 +0100
> > +++ /tmp/headersb.txt   2022-06-01 17:22:43.972218408 +0100
> > @@ -1,5 +1,5 @@
> > 
> > -a/usr/lib/libwebkit2gtk-4.0.so.37.56.5: file format elf64-x86-64
> > +b/usr/lib/libwebkit2gtk-4.0.so.37.56.5: file format elf64-x86-64
> > 
> >  Sections:
> >  Idx Name  Size  VMA   LMA   File off  
> > Algn
> > @@ -63,15 +63,15 @@
> >CONTENTS, READONLY, DEBUGGING, OCTETS
> >   29 .debug_abbrev 00c6ce64      921c9968  
> > 2**0
> >CONTENTS, READONLY, DEBUGGING, OCTETS
> > - 30 .debug_line   09025ee1      92e367cc  
> > 2**0
> > + 30 .debug_line   09025ede      92e367cc  
> > 2**0
> >CONTENTS, READONLY, DEBUGGING, OCTETS
> > - 31 .debug_str1820ba50      9be5c6ad  
> > 2**0
> > + 31 .debug_str1820ba50      9be5c6aa  
> > 2**0
> >CONTENTS, READONLY, DEBUGGING, OCTETS
> > - 32 .debug_line_str 0005d9f4      b40680fd 
> >  2**0
> > + 32 .debug_line_str 0005d9f4      b40680fa 
> >  2**0
> >CONTENTS, READONLY, DEBUGGING, OCTETS
> > - 33 .debug_loclists 13d74aa2      b40c5af1 
> >  2**0
> > + 33 .debug_loclists 13d74aa0      b40c5aee 
> >  2**0
> >CONTENTS, READONLY, DEBUGGING, OCTETS
> > - 34 .debug_rnglists 034c6c08      c7e3a593 
> >  2**0
> > + 34 .debug_rnglists 034c6bf6      c7e3a58e 
> >  2**0
> >CONTENTS, READONLY, DEBUGGING, OCTETS
> > - 35 .gnu_debuglink 0024      cb30119c  
> > 2**2
> > + 35 .gnu_debuglink 0024      cb301184  
> > 2**2
> >CONTENTS, READONLY
> > 
> > I'm a bit puzzled since usually the debug symbols are moved off to the
> > -dbg package and yet they seem combined here with the library. What the
> > above seems to say is that the debug_line, loclists and rnglists
> > sections changed size, the rest changed offset (and we ignore
> > gnu_debuglink since that is a checksum which would depend on the other
> > bits).
> > 
> > That would imply that some piece of code used to compile webkit has
> > different line numbering on one system compared to another but
> > generates identical code. You should be able to parse the debuginfo to
> > get a filename and linenumber out of it but I can't remember how, I
> > think I learnt to read dwarfish last time I did this :/.
> 
> I did a dump of the debug sections with objdump -g and got absolutely
> huge output files that crashed all of the diff programs I tried.
> 
> I guess the next step is to split those files into smaller chunks and
> diff those :-(
> 
> Have I mentioned how much I hate webkit-gtk?

Steve ran readelf against them and found there were some differences
with the _ZZN7WebCore11CSSProperty symbol. A grep on a build directory
shows:

tmp/work/core2-64-poky-linux/webkitgtk/2.36.1-r0$ grep WebCore11CSSProperty 
build webkitgtk-2.36.1 -R
grep: build/lib/libWebCoreGTK.a: binary file matches
grep: 
build/Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-2f84417a-14.cpp.o:
 binary file matches
grep: 
build/Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-2f84417a-17.cpp.o:
 binary file matches
grep: 
build/Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-84c9f43f-5.cpp.o:
 binary file matches
grep: 
build/Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-26ec8d00-4.cpp.o:
 binary file matches
grep: 
build/Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-2f84417a-7.cpp.o:
 binary file matches
grep:

[OE-core] [kirkstone][PATCH] gcc: depend on zstd-native

Sharing sstate cache binaries between two systems, one with libzstd installed
and the other without, leads to various gcc components being linked against
the system libzstd and failing to run on the system with out it installed.

Make zstd-native from our system available.

Signed-off-by: Jeremy A. Puhlman 
---
 meta/recipes-devtools/gcc/gcc-11.2.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc 
b/meta/recipes-devtools/gcc/gcc-11.2.inc
index 68e0d203fc..e2a28468f5 100644
--- a/meta/recipes-devtools/gcc/gcc-11.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
@@ -11,7 +11,7 @@ BINV = "11.2.0"
 FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
 
 DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
-NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native"
+NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native 
zstd-native"
 
 LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"
 
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166442): 
https://lists.openembedded.org/g/openembedded-core/message/166442
Mute This Topic: https://lists.openembedded.org/mt/91486528/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH] gcc: depend on zstd-native

On Wed, 2022-06-01 at 16:55 -0400, Jeremy Puhlman wrote:
> Sharing sstate cache binaries between two systems, one with libzstd installed
> and the other without, leads to various gcc components being linked against
> the system libzstd and failing to run on the system with out it installed.
> 
> Make zstd-native from our system available.
> 
> Signed-off-by: Jeremy A. Puhlman 
> ---
>  meta/recipes-devtools/gcc/gcc-11.2.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc 
> b/meta/recipes-devtools/gcc/gcc-11.2.inc
> index 68e0d203fc..e2a28468f5 100644
> --- a/meta/recipes-devtools/gcc/gcc-11.2.inc
> +++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
> @@ -11,7 +11,7 @@ BINV = "11.2.0"
>  FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
>  
>  DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
> -NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native"
> +NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native 
> zstd-native"
>  
>  LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"

Does master have that issue?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166443): 
https://lists.openembedded.org/g/openembedded-core/message/166443
Mute This Topic: https://lists.openembedded.org/mt/91486528/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH] gcc: depend on zstd-native




On 6/1/2022 3:15 PM, Richard Purdie wrote:

On Wed, 2022-06-01 at 16:55 -0400, Jeremy Puhlman wrote:

Sharing sstate cache binaries between two systems, one with libzstd installed
and the other without, leads to various gcc components being linked against
the system libzstd and failing to run on the system with out it installed.

Make zstd-native from our system available.

Signed-off-by: Jeremy A. Puhlman 
---
  meta/recipes-devtools/gcc/gcc-11.2.inc | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc 
b/meta/recipes-devtools/gcc/gcc-11.2.inc
index 68e0d203fc..e2a28468f5 100644
--- a/meta/recipes-devtools/gcc/gcc-11.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
@@ -11,7 +11,7 @@ BINV = "11.2.0"
  FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
  
  DEPENDS =+ "mpfr gmp libmpc zlib flex-native"

-NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native"
+NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native 
zstd-native"
  
  LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"

Does master have that issue?

Cheers,

Richard


I would would be really surprised if it didn't, since it appears gcc is 
explicilty decidding to use the library if it is there. The patch 
cherry-picks with

name fuzzing so if we want to start it there, I can resubmit on master.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166444): 
https://lists.openembedded.org/g/openembedded-core/message/166444
Mute This Topic: https://lists.openembedded.org/mt/91486528/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH] gcc: depend on zstd-native

On Wed, Jun 1, 2022 at 12:27 PM Jeremy Puhlman  wrote:
>
>
>
> On 6/1/2022 3:15 PM, Richard Purdie wrote:
> > On Wed, 2022-06-01 at 16:55 -0400, Jeremy Puhlman wrote:
> >> Sharing sstate cache binaries between two systems, one with libzstd 
> >> installed
> >> and the other without, leads to various gcc components being linked against
> >> the system libzstd and failing to run on the system with out it installed.
> >>
> >> Make zstd-native from our system available.
> >>
> >> Signed-off-by: Jeremy A. Puhlman 
> >> ---
> >>   meta/recipes-devtools/gcc/gcc-11.2.inc | 2 +-
> >>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc 
> >> b/meta/recipes-devtools/gcc/gcc-11.2.inc
> >> index 68e0d203fc..e2a28468f5 100644
> >> --- a/meta/recipes-devtools/gcc/gcc-11.2.inc
> >> +++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
> >> @@ -11,7 +11,7 @@ BINV = "11.2.0"
> >>   FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
> >>
> >>   DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
> >> -NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native 
> >> flex-native"
> >> +NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native 
> >> flex-native zstd-native"
> >>
> >>   LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"
> > Does master have that issue?
> >
> > Cheers,
> >
> > Richard
>
> I would would be really surprised if it didn't, since it appears gcc is
> explicilty decidding to use the library if it is there. The patch
> cherry-picks with
> name fuzzing so if we want to start it there, I can resubmit on master.

Yes, please do!  I'll cherry-pick to kirkstone after it hits master.

Steve

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166445): 
https://lists.openembedded.org/g/openembedded-core/message/166445
Mute This Topic: https://lists.openembedded.org/mt/91486528/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] gcc: depend on zstd-native

Sharing sstate cache binaries between two systems, one with libzstd installed
and the other without, leads to various gcc components being linked against
the system libzstd and failing to run on the system with out it installed.

Make zstd-native from our system available.

Signed-off-by: Jeremy A. Puhlman 
---
 meta/recipes-devtools/gcc/gcc-12.1.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-12.1.inc 
b/meta/recipes-devtools/gcc/gcc-12.1.inc
index c8c4ae93e1..250b587e78 100644
--- a/meta/recipes-devtools/gcc/gcc-12.1.inc
+++ b/meta/recipes-devtools/gcc/gcc-12.1.inc
@@ -11,7 +11,7 @@ BINV = "12.1.0"
 FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
 
 DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
-NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native"
+NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native 
zstd-native"
 
 LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"
 
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166446): 
https://lists.openembedded.org/g/openembedded-core/message/166446
Mute This Topic: https://lists.openembedded.org/mt/91488934/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH] gcc: depend on zstd-native




On 6/1/2022 3:29 PM, Steve Sakoman wrote:

On Wed, Jun 1, 2022 at 12:27 PM Jeremy Puhlman  wrote:



On 6/1/2022 3:15 PM, Richard Purdie wrote:

On Wed, 2022-06-01 at 16:55 -0400, Jeremy Puhlman wrote:

Sharing sstate cache binaries between two systems, one with libzstd installed
and the other without, leads to various gcc components being linked against
the system libzstd and failing to run on the system with out it installed.

Make zstd-native from our system available.

Signed-off-by: Jeremy A. Puhlman 
---
   meta/recipes-devtools/gcc/gcc-11.2.inc | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc 
b/meta/recipes-devtools/gcc/gcc-11.2.inc
index 68e0d203fc..e2a28468f5 100644
--- a/meta/recipes-devtools/gcc/gcc-11.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
@@ -11,7 +11,7 @@ BINV = "11.2.0"
   FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"

   DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
-NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native"
+NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native 
zstd-native"

   LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"

Does master have that issue?

Cheers,

Richard

I would would be really surprised if it didn't, since it appears gcc is
explicilty decidding to use the library if it is there. The patch
cherry-picks with
name fuzzing so if we want to start it there, I can resubmit on master.

Yes, please do!  I'll cherry-pick to kirkstone after it hits master.


Did a quick build on master and yeah, it links against libzstd.so.1.

tmp/work/x86_64-linux/gcc-cross-x86_64/12.1.0-r0/image/home/cluge/builds/centos7/x86-generic-64-5.10-4.0-cgx/build/tmp/work/x86_64-linux/gcc-cross-x86_64/12.1.0-r0/recipe-sysroot-native/usr/libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/12.1.0/cc1
  NEEDED   libmpc.so.3
  NEEDED   libmpfr.so.6
  NEEDED   libgmp.so.10
  NEEDED   libz.so.1
  NEEDED   libzstd.so.1
  NEEDED   libm.so.6
  NEEDED   libc.so.6
  NEEDED   ld-linux-x86-64.so.2

Patch for master submitted.



Steve



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166447): 
https://lists.openembedded.org/g/openembedded-core/message/166447
Mute This Topic: https://lists.openembedded.org/mt/91486528/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 00/11] Patch review

Please review this set of patches for dunfell and have comments back by end
of day Friday.

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3738

The following changes since commit add860e1a69f848097bbc511137a62d5746e5019:

  oeqa/selftest/cve_check: add tests for recipe and image reports (2022-05-24 
04:31:18 -1000)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Dan Tran (1):
  ncurses: Fix CVE-2022-29458

Ernst Sjöstrand (2):
  cve-check: Add helper for symlink handling
  cve-check: Only include installed packages for rootfs manifest

Ranjitsinh Rathod (3):
  ruby: Upgrade ruby to 2.7.6 for security fix
  ruby: Whitelist CVE-2021-28966 as this affects Windows OS only
  libsdl2: Add fix for CVE-2021-33657

Richard Purdie (2):
  vim: Upgrade 8.2.4912 -> 8.2.5034 to fix 9 CVEs
  cve-check: Allow warnings to be disabled

Riyaz (1):
  libxml2: Fix CVE-2022-29824 for libxml2

Virendra Thakur (1):
  ffmpeg: Fix for CVE-2022-1475

leimaohui (1):
  cve-check.bbclass: Added do_populate_sdk[recrdeptask].

 meta/classes/cve-check.bbclass| 109 --
 .../libxml2/CVE-2022-29824-dependent.patch|  53 +++
 .../libxml/libxml2/CVE-2022-29824.patch   | 348 ++
 meta/recipes-core/libxml/libxml2_2.9.10.bb|   2 +
 .../ncurses/files/CVE-2022-29458.patch| 135 +++
 meta/recipes-core/ncurses/ncurses_6.2.bb  |   1 +
 .../ruby/{ruby_2.7.5.bb => ruby_2.7.6.bb} |   8 +-
 .../libsdl2/libsdl2/CVE-2021-33657.patch  |  38 ++
 .../libsdl2/libsdl2_2.0.12.bb |   1 +
 .../ffmpeg/ffmpeg/CVE-2022-1475.patch |  36 ++
 .../recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb |   1 +
 meta/recipes-support/vim/vim.inc  |   4 +-
 12 files changed, 694 insertions(+), 42 deletions(-)
 create mode 100644 
meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch
 create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch
 create mode 100644 meta/recipes-core/ncurses/files/CVE-2022-29458.patch
 rename meta/recipes-devtools/ruby/{ruby_2.7.5.bb => ruby_2.7.6.bb} (90%)
 create mode 100644 meta/recipes-graphics/libsdl2/libsdl2/CVE-2021-33657.patch
 create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2022-1475.patch

-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166448): 
https://lists.openembedded.org/g/openembedded-core/message/166448
Mute This Topic: https://lists.openembedded.org/mt/91492143/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 01/11] ruby: Upgrade ruby to 2.7.6 for security fix

From: Ranjitsinh Rathod 

Upgrade ruby to 2.7.6
Link: https://www.ruby-lang.org/en/news/2022/04/12/ruby-2-7-6-released/
This includes CVE-2022-28739 security fix

Signed-off-by: Ranjitsinh Rathod 
Signed-off-by: Ranjitsinh Rathod 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/ruby/{ruby_2.7.5.bb => ruby_2.7.6.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/ruby/{ruby_2.7.5.bb => ruby_2.7.6.bb} (95%)

diff --git a/meta/recipes-devtools/ruby/ruby_2.7.5.bb 
b/meta/recipes-devtools/ruby/ruby_2.7.6.bb
similarity index 95%
rename from meta/recipes-devtools/ruby/ruby_2.7.5.bb
rename to meta/recipes-devtools/ruby/ruby_2.7.6.bb
index 44a2527ee7..658a17659a 100644
--- a/meta/recipes-devtools/ruby/ruby_2.7.5.bb
+++ b/meta/recipes-devtools/ruby/ruby_2.7.6.bb
@@ -9,8 +9,8 @@ SRC_URI += " \

file://0001-template-Makefile.in-do-not-write-host-cross-cc-item.patch \
"
 
-SRC_URI[md5sum] = "ede247b56fb862f1f67f9471189b04d4"
-SRC_URI[sha256sum] = 
"2755b900a21235b443bb16dadd9032f784d4a88f143d852bc5d154f22b8781f1"
+SRC_URI[md5sum] = "f972fb0cce662966bec10d5c5f32d042"
+SRC_URI[sha256sum] = 
"e7203b0cc09442ed2c08936d483f8ac140ec1c72e37bb5c401646b7866cb5d10"
 
 PACKAGECONFIG ??= ""
 PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'ipv6', d)}"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166449): 
https://lists.openembedded.org/g/openembedded-core/message/166449
Mute This Topic: https://lists.openembedded.org/mt/91492145/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 02/11] ruby: Whitelist CVE-2021-28966 as this affects Windows OS only

From: Ranjitsinh Rathod 

As per below debian link, CVE-2021-28966 affects Windows only
Link: https://security-tracker.debian.org/tracker/CVE-2021-28966

Signed-off-by: Ranjitsinh Rathod 
Signed-off-by: Ranjitsinh Rathod 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/ruby/ruby_2.7.6.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-devtools/ruby/ruby_2.7.6.bb 
b/meta/recipes-devtools/ruby/ruby_2.7.6.bb
index 658a17659a..3af321a83e 100644
--- a/meta/recipes-devtools/ruby/ruby_2.7.6.bb
+++ b/meta/recipes-devtools/ruby/ruby_2.7.6.bb
@@ -12,6 +12,10 @@ SRC_URI += " \
 SRC_URI[md5sum] = "f972fb0cce662966bec10d5c5f32d042"
 SRC_URI[sha256sum] = 
"e7203b0cc09442ed2c08936d483f8ac140ec1c72e37bb5c401646b7866cb5d10"
 
+# CVE-2021-28966 is Windows specific and not affects Linux OS
+# https://security-tracker.debian.org/tracker/CVE-2021-28966
+CVE_CHECK_WHITELIST += "CVE-2021-28966"
+
 PACKAGECONFIG ??= ""
 PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'ipv6', d)}"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166450): 
https://lists.openembedded.org/g/openembedded-core/message/166450
Mute This Topic: https://lists.openembedded.org/mt/91492146/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 03/11] libsdl2: Add fix for CVE-2021-33657

From: Ranjitsinh Rathod 

Add patch to fix CVE-2021-33657 issue for libsdl2
Link: https://security-tracker.debian.org/tracker/CVE-2021-33657

Signed-off-by: Ranjitsinh Rathod 
Signed-off-by: Ranjitsinh Rathod 
Signed-off-by: Steve Sakoman 
---
 .../libsdl2/libsdl2/CVE-2021-33657.patch  | 38 +++
 .../libsdl2/libsdl2_2.0.12.bb |  1 +
 2 files changed, 39 insertions(+)
 create mode 100644 meta/recipes-graphics/libsdl2/libsdl2/CVE-2021-33657.patch

diff --git a/meta/recipes-graphics/libsdl2/libsdl2/CVE-2021-33657.patch 
b/meta/recipes-graphics/libsdl2/libsdl2/CVE-2021-33657.patch
new file mode 100644
index 00..a4ed7ab8e6
--- /dev/null
+++ b/meta/recipes-graphics/libsdl2/libsdl2/CVE-2021-33657.patch
@@ -0,0 +1,38 @@
+From 8c91cf7dba5193f5ce12d06db1336515851c9ee9 Mon Sep 17 00:00:00 2001
+From: Sam Lantinga 
+Date: Tue, 30 Nov 2021 12:36:46 -0800
+Subject: [PATCH] Always create a full 256-entry map in case color values are
+ out of range
+
+Fixes https://github.com/libsdl-org/SDL/issues/5042
+
+CVE: CVE-2021-33657
+Upstream-Status: Backport 
[https://github.com/libsdl-org/SDL/commit/8c91cf7dba5193f5ce12d06db1336515851c9ee9.patch]
+Signed-off-by: Ranjitsinh Rathod 
+
+---
+ src/video/SDL_pixels.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/video/SDL_pixels.c b/src/video/SDL_pixels.c
+index ac04533c5d5..9bb02f771d0 100644
+--- a/src/video/SDL_pixels.c
 b/src/video/SDL_pixels.c
+@@ -947,7 +947,7 @@ Map1to1(SDL_Palette * src, SDL_Palette * dst, int 
*identical)
+ }
+ *identical = 0;
+ }
+-map = (Uint8 *) SDL_malloc(src->ncolors);
++map = (Uint8 *) SDL_calloc(256, sizeof(Uint8));
+ if (map == NULL) {
+ SDL_OutOfMemory();
+ return (NULL);
+@@ -971,7 +971,7 @@ Map1toN(SDL_PixelFormat * src, Uint8 Rmod, Uint8 Gmod, 
Uint8 Bmod, Uint8 Amod,
+ SDL_Palette *pal = src->palette;
+ 
+ bpp = ((dst->BytesPerPixel == 3) ? 4 : dst->BytesPerPixel);
+-map = (Uint8 *) SDL_malloc(pal->ncolors * bpp);
++map = (Uint8 *) SDL_calloc(256, bpp);
+ if (map == NULL) {
+ SDL_OutOfMemory();
+ return (NULL);
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.12.bb 
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.12.bb
index 8e77c18f2d..44d36fca22 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.12.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.12.bb
@@ -21,6 +21,7 @@ SRC_URI = "http://www.libsdl.org/release/SDL2-${PV}.tar.gz \
file://directfb-spurious-curly-brace-missing-e.patch \
file://directfb-renderfillrect-fix.patch \
file://CVE-2020-14409-14410.patch \
+   file://CVE-2021-33657.patch \
 "
 
 S = "${WORKDIR}/SDL2-${PV}"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166451): 
https://lists.openembedded.org/g/openembedded-core/message/166451
Mute This Topic: https://lists.openembedded.org/mt/91492147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 04/11] ffmpeg: Fix for CVE-2022-1475

From: Virendra Thakur 

Add patch to fix CVE-2022-1475

Signed-off-by: Virendra Thakur 
Signed-off-by: Steve Sakoman 
---
 .../ffmpeg/ffmpeg/CVE-2022-1475.patch | 36 +++
 .../recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb |  1 +
 2 files changed, 37 insertions(+)
 create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2022-1475.patch

diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2022-1475.patch 
b/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2022-1475.patch
new file mode 100644
index 00..bd8a08a216
--- /dev/null
+++ b/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2022-1475.patch
@@ -0,0 +1,36 @@
+From: Michael Niedermayer 
+Date: Sun, 27 Feb 2022 14:43:04 +0100
+Subject: [PATCH] avcodec/g729_parser: Check channels
+
+Fixes: signed integer overflow: 10 * 808464428 cannot be represented in type 
'int'
+Fixes: assertion failure
+Fixes: ticket9651
+
+Reviewed-by: Paul B Mahol 
+Signed-off-by: Michael Niedermayer 
+(cherry picked from commit 757da974b21833529cc41bdcc9684c29660cdfa8)
+Signed-off-by: Michael Niedermayer 
+
+CVE: CVE-2022-1475
+Upstream-Status: Backport 
[https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=e9e2ddbc6c78cc18b76093617f82c920e58a8d1f]
+Comment: Patch is refreshed as per ffmpeg codebase
+Signed-off-by: Virendra Thakur 
+
+---
+ libavcodec/g729_parser.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+Index: ffmpeg-4.2.2/libavcodec/g729_parser.c
+===
+--- a/libavcodec/g729_parser.c
 b/libavcodec/g729_parser.c
+@@ -48,6 +48,9 @@ static int g729_parse(AVCodecParserConte
+ av_assert1(avctx->codec_id == AV_CODEC_ID_G729);
+ /* FIXME: replace this heuristic block_size with more precise 
estimate */
+ s->block_size = (avctx->bit_rate < 8000) ? G729D_6K4_BLOCK_SIZE : 
G729_8K_BLOCK_SIZE;
++// channels > 2 is invalid, we pass the packet on unchanged
++if (avctx->channels > 2)
++s->block_size = 0;
+ s->block_size *= avctx->channels;
+ s->duration   = avctx->frame_size;
+ }
diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb 
b/meta/recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb
index 1d6f2e528b..cbfdbf0563 100644
--- a/meta/recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb
+++ b/meta/recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb
@@ -29,6 +29,7 @@ SRC_URI = "https://www.ffmpeg.org/releases/${BP}.tar.xz \

file://0001-libavutil-include-assembly-with-full-path-from-sourc.patch \
file://CVE-2021-3566.patch \
file://CVE-2021-38291.patch \
+   file://CVE-2022-1475.patch \
   "
 SRC_URI[md5sum] = "348956fc2faa57a2f79bbb84ded9fbc3"
 SRC_URI[sha256sum] = 
"cb754255ab0ee2ea5f66f8850e1bd6ad5cac1cd855d0a2f4990fb8c668b0d29c"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166452): 
https://lists.openembedded.org/g/openembedded-core/message/166452
Mute This Topic: https://lists.openembedded.org/mt/91492149/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 06/11] libxml2: Fix CVE-2022-29824 for libxml2

From: Riyaz 

Add patch for CVE issue: CVE-2022-29824

CVE-2022-29824
Link: 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/2554a2408e09f13652049e5ffb0d26196b02ebab]
Dependent patch: 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/b07251215ef48c70c6e56f7351406c47cfca4d5b]

Signed-off-by: Riyaz 
Signed-off-by: Steve Sakoman 
---
 .../libxml2/CVE-2022-29824-dependent.patch|  53 +++
 .../libxml/libxml2/CVE-2022-29824.patch   | 348 ++
 meta/recipes-core/libxml/libxml2_2.9.10.bb|   2 +
 3 files changed, 403 insertions(+)
 create mode 100644 
meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch
 create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch

diff --git a/meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch 
b/meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch
new file mode 100644
index 00..63d613cc21
--- /dev/null
+++ b/meta/recipes-core/libxml/libxml2/CVE-2022-29824-dependent.patch
@@ -0,0 +1,53 @@
+From b07251215ef48c70c6e56f7351406c47cfca4d5b Mon Sep 17 00:00:00 2001
+From: Nick Wellnhofer 
+Date: Fri, 10 Jan 2020 15:55:07 +0100
+Subject: [PATCH] Fix integer overflow in xmlBufferResize
+
+Found by OSS-Fuzz.
+
+CVE: CVE-2022-29824
+
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/b07251215ef48c70c6e56f7351406c47cfca4d5b]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ tree.c | 9 +++--
+ 1 file changed, 7 insertions(+), 2 deletions(-)
+
+diff --git a/tree.c b/tree.c
+index 0d7fc98c..f43f6de1 100644
+--- a/tree.c
 b/tree.c
+@@ -7424,12 +7424,17 @@ xmlBufferResize(xmlBufferPtr buf, unsigned int size)
+ if (size < buf->size)
+ return 1;
+ 
++if (size > UINT_MAX - 10) {
++xmlTreeErrMemory("growing buffer");
++return 0;
++}
++
+ /* figure out new size */
+ switch (buf->alloc){
+   case XML_BUFFER_ALLOC_IO:
+   case XML_BUFFER_ALLOC_DOUBLEIT:
+   /*take care of empty case*/
+-  newSize = (buf->size ? buf->size*2 : size + 10);
++  newSize = (buf->size ? buf->size : size + 10);
+   while (size > newSize) {
+   if (newSize > UINT_MAX / 2) {
+   xmlTreeErrMemory("growing buffer");
+@@ -7445,7 +7450,7 @@ xmlBufferResize(xmlBufferPtr buf, unsigned int size)
+ if (buf->use < BASE_BUFFER_SIZE)
+ newSize = size;
+ else {
+-newSize = buf->size * 2;
++newSize = buf->size;
+ while (size > newSize) {
+ if (newSize > UINT_MAX / 2) {
+ xmlTreeErrMemory("growing buffer");
+-- 
+GitLab
+
+
diff --git a/meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch 
b/meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch
new file mode 100644
index 00..ad7b87dbc6
--- /dev/null
+++ b/meta/recipes-core/libxml/libxml2/CVE-2022-29824.patch
@@ -0,0 +1,348 @@
+From 2554a2408e09f13652049e5ffb0d26196b02ebab Mon Sep 17 00:00:00 2001
+From: Nick Wellnhofer 
+Date: Tue, 8 Mar 2022 20:10:02 +0100
+Subject: [PATCH] [CVE-2022-29824] Fix integer overflows in xmlBuf and
+ xmlBuffer
+
+In several places, the code handling string buffers didn't check for
+integer overflow or used wrong types for buffer sizes. This could
+result in out-of-bounds writes or other memory errors when working on
+large, multi-gigabyte buffers.
+
+Thanks to Felix Wilhelm for the report.
+
+CVE: CVE-2022-29824
+
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/2554a2408e09f13652049e5ffb0d26196b02ebab]
+
+Signed-off-by: Riyaz Ahmed Khan 
+
+---
+ buf.c  | 86 +++---
+ tree.c | 72 ++--
+ 2 files changed, 61 insertions(+), 97 deletions(-)
+
+diff --git a/buf.c b/buf.c
+index 24368d37..40a5ee06 100644
+--- a/buf.c
 b/buf.c
+@@ -30,6 +30,10 @@
+ #include  /* for XML_MAX_TEXT_LENGTH */
+ #include "buf.h"
+ 
++#ifndef SIZE_MAX
++#define SIZE_MAX ((size_t) -1)
++#endif
++
+ #define WITH_BUFFER_COMPAT
+ 
+ /**
+@@ -156,6 +160,8 @@ xmlBufPtr
+ xmlBufCreateSize(size_t size) {
+ xmlBufPtr ret;
+ 
++if (size == SIZE_MAX)
++return(NULL);
+ ret = (xmlBufPtr) xmlMalloc(sizeof(xmlBuf));
+ if (ret == NULL) {
+   xmlBufMemoryError(NULL, "creating buffer");
+@@ -166,8 +172,8 @@ xmlBufCreateSize(size_t size) {
+ ret->error = 0;
+ ret->buffer = NULL;
+ ret->alloc = xmlBufferAllocScheme;
+-ret->size = (size ? size+2 : 0); /* +1 for ending null */
+-ret->compat_size = (int) ret->size;
++ret->size = (size ? size + 1 : 0); /* +1 for ending null */
++ret->compat_size = (ret->size > INT_MAX ? INT_MAX : ret->size);
+ if (ret->size){
+ ret->content = (xmlChar *) xmlMallocAtomic(ret->size * 
sizeof(xmlChar));
+ if (ret->content == NULL) {
+@@ -442,23 +448,17 @@ xmlBufGrowInternal(xmlBufPtr buf, size_t len) {
+ CHECK_C

[OE-core][dunfell 05/11] ncurses: Fix CVE-2022-29458

From: Dan Tran 

ncurses 6.3 before patch 20220416 has an out-of-bounds read and
segmentation violation in convert_strings in tinfo/read_entry.c in the
terminfo library.

Backported from the link below, extracting only the relevant changes.
https://github.com/ThomasDickey/ncurses-snapshots/commit/9d1d651878d4bf0695872a64cc65ba0acb825f36

Signed-off-by: Gustavo Lima Chaves 
Signed-off-by: Dan Tran 
Signed-off-by: Steve Sakoman 
---
 .../ncurses/files/CVE-2022-29458.patch| 135 ++
 meta/recipes-core/ncurses/ncurses_6.2.bb  |   1 +
 2 files changed, 136 insertions(+)
 create mode 100644 meta/recipes-core/ncurses/files/CVE-2022-29458.patch

diff --git a/meta/recipes-core/ncurses/files/CVE-2022-29458.patch 
b/meta/recipes-core/ncurses/files/CVE-2022-29458.patch
new file mode 100644
index 00..eb1b7c96f9
--- /dev/null
+++ b/meta/recipes-core/ncurses/files/CVE-2022-29458.patch
@@ -0,0 +1,135 @@
+From 5f40697e37e195069f55528fc7a1d77e619ad104 Mon Sep 17 00:00:00 2001
+From: Dan Tran 
+Date: Fri, 13 May 2022 13:28:41 -0700
+Subject: [PATCH] ncurses 6.3 before patch 20220416 has an out-of-bounds read
+ and segmentation violation in convert_strings in tinfo/read_entry.c in the
+ terminfo library.
+
+CVE: CVE-2022-29458
+Upstream-Status: Backport
+[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009870]
+
+Signed-off-by: Gustavo Lima Chaves 
+Signed-off-by: Dan Tran 
+---
+ ncurses/tinfo/alloc_entry.c | 14 ++
+ ncurses/tinfo/read_entry.c  | 25 +++--
+ 2 files changed, 25 insertions(+), 14 deletions(-)
+
+diff --git a/ncurses/tinfo/alloc_entry.c b/ncurses/tinfo/alloc_entry.c
+index 4bf7d6c8..b49ad6aa 100644
+--- a/ncurses/tinfo/alloc_entry.c
 b/ncurses/tinfo/alloc_entry.c
+@@ -48,13 +48,11 @@
+ 
+ #include 
+ 
+-MODULE_ID("$Id: alloc_entry.c,v 1.64 2020/02/02 23:34:34 tom Exp $")
++MODULE_ID("$Id: alloc_entry.c,v 1.69 2022/04/16 22:46:53 tom Exp $")
+ 
+ #define ABSENT_OFFSET-1
+ #define CANCELLED_OFFSET -2
+ 
+-#define MAX_STRTAB4096/* documented maximum entry size */
+-
+ static char *stringbuf;   /* buffer for string capabilities */
+ static size_t next_free;  /* next free character in stringbuf */
+ 
+@@ -71,8 +69,8 @@ _nc_init_entry(ENTRY * const tp)
+ }
+ #endif
+ 
+-if (stringbuf == 0)
+-  TYPE_MALLOC(char, (size_t) MAX_STRTAB, stringbuf);
++if (stringbuf == NULL)
++  TYPE_MALLOC(char, (size_t) MAX_ENTRY_SIZE, stringbuf);
+ 
+ next_free = 0;
+ 
+@@ -108,11 +106,11 @@ _nc_save_str(const char *const string)
+* Cheat a little by making an empty string point to the end of the
+* previous string.
+*/
+-  if (next_free < MAX_STRTAB) {
++  if (next_free < MAX_ENTRY_SIZE) {
+   result = (stringbuf + next_free - 1);
+   }
+-} else if (next_free + len < MAX_STRTAB) {
+-  _nc_STRCPY(&stringbuf[next_free], string, MAX_STRTAB);
++} else if (next_free + len < MAX_ENTRY_SIZE) {
++  _nc_STRCPY(&stringbuf[next_free], string, MAX_ENTRY_SIZE);
+   DEBUG(7, ("Saved string %s", _nc_visbuf(string)));
+   DEBUG(7, ("at location %d", (int) next_free));
+   next_free += len;
+diff --git a/ncurses/tinfo/read_entry.c b/ncurses/tinfo/read_entry.c
+index 5b570b0f..23c2cebc 100644
+--- a/ncurses/tinfo/read_entry.c
 b/ncurses/tinfo/read_entry.c
+@@ -1,5 +1,5 @@
+ /
+- * Copyright 2018-2019,2020 Thomas E. Dickey*
++ * Copyright 2018-2021,2022 Thomas E. Dickey*
+  * Copyright 1998-2016,2017 Free Software Foundation, Inc.  *
+  *  *
+  * Permission is hereby granted, free of charge, to any person obtaining a  *
+@@ -42,7 +42,7 @@
+ 
+ #include 
+ 
+-MODULE_ID("$Id: read_entry.c,v 1.157 2020/02/02 23:34:34 tom Exp $")
++MODULE_ID("$Id: read_entry.c,v 1.162 2022/04/16 21:00:00 tom Exp $")
+ 
+ #define TYPE_CALLOC(type,elts) typeCalloc(type, (unsigned)(elts))
+ 
+@@ -145,6 +145,7 @@ convert_strings(char *buf, char **Strings, int count, int 
size, char *table)
+ {
+ int i;
+ char *p;
++bool corrupt = FALSE;
+ 
+ for (i = 0; i < count; i++) {
+   if (IS_NEG1(buf + 2 * i)) {
+@@ -154,8 +155,20 @@ convert_strings(char *buf, char **Strings, int count, int 
size, char *table)
+   } else if (MyNumber(buf + 2 * i) > size) {
+   Strings[i] = ABSENT_STRING;
+   } else {
+-  Strings[i] = (MyNumber(buf + 2 * i) + table);
+-  TR(TRACE_DATABASE, ("Strings[%d] = %s", i, _nc_visbuf(Strings[i])));
++  int nn = MyNumber(buf + 2 * i);
++  if (nn >= 0 && nn < size) {
++  Strings[i] = (nn + table);
++  TR(TRACE_DATABASE, ("Strings[%d] = %s", i,
++  _nc_visbuf(Strings[i])));
++  } else {
++  if (!corrupt) {
+

[OE-core][dunfell 07/11] vim: Upgrade 8.2.4912 -> 8.2.5034 to fix 9 CVEs

From: Richard Purdie 

Address CVE-2022-1621, CVE-2022-1629, CVE-2022-1674, CVE-2022-1733, 
CVE-2022-1735
CVE-2022-1769, CVE-2022-1771, CVE-2022-1785, CVE-2022-1796

Signed-off-by: Richard Purdie 
(cherry picked from commit fafce97bd440150ac5c586b53b887ee70a5b66bd)
Signed-off-by: Steve Sakoman 
---
 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 4b8f4d1dfb..9d918379b4 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -21,8 +21,8 @@ SRC_URI = 
"git://github.com/vim/vim.git;branch=master;protocol=https \
file://racefix.patch \
"
 
-PV .= ".4912"
-SRCREV = "a7583c42cd6b64fd276a5d7bb0db5ce7bfafa730"
+PV .= ".5034"
+SRCREV = "5a6ec10cc80ab02eeff644ab19b82312630ea855"
 
 # Remove when 8.3 is out
 UPSTREAM_VERSION_UNKNOWN = "1"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166455): 
https://lists.openembedded.org/g/openembedded-core/message/166455
Mute This Topic: https://lists.openembedded.org/mt/91492154/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 09/11] cve-check: Add helper for symlink handling

From: Ernst Sjöstrand 

Signed-off-by: Ernst Sjöstrand 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit 5046d54df2c3057be2afa4143a2833183fca0d67)
Signed-off-by: Steve Sakoman 
---
 meta/classes/cve-check.bbclass | 34 +-
 1 file changed, 13 insertions(+), 21 deletions(-)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index f7ed2a6ae9..3cae0e8eb2 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -75,6 +75,12 @@ CVE_CHECK_LAYER_INCLUDELIST ??= ""
 # set to "alphabetical" for version using single alphabetical character as 
increment release
 CVE_VERSION_SUFFIX ??= ""
 
+def update_symlinks(target_path, link_path):
+if link_path != target_path and os.path.exists(target_path):
+if os.path.exists(os.path.realpath(link_path)):
+os.remove(link_path)
+os.symlink(os.path.basename(target_path), link_path)
+
 def generate_json_report(d, out_path, link_path):
 if os.path.exists(d.getVar("CVE_CHECK_SUMMARY_INDEX_PATH")):
 import json
@@ -94,10 +100,7 @@ def generate_json_report(d, out_path, link_path):
 with open(out_path, "w") as f:
 json.dump(summary, f, indent=2)
 
-if link_path != out_path:
-if os.path.exists(os.path.realpath(link_path)):
-os.remove(link_path)
-os.symlink(os.path.basename(out_path), link_path)
+update_symlinks(out_path, link_path)
 
 python cve_save_summary_handler () {
 import shutil
@@ -114,14 +117,9 @@ python cve_save_summary_handler () {
 
 if os.path.exists(cve_tmp_file):
 shutil.copyfile(cve_tmp_file, cve_summary_file)
-
-if cve_summary_file and os.path.exists(cve_summary_file):
-cvefile_link = os.path.join(cvelogpath, cve_summary_name)
-# if the paths are the same don't create the link
-if cvefile_link != cve_summary_file:
-if os.path.exists(os.path.realpath(cvefile_link)):
-os.remove(cvefile_link)
-os.symlink(os.path.basename(cve_summary_file), cvefile_link)
+cvefile_link = os.path.join(cvelogpath, cve_summary_name)
+update_symlinks(cve_summary_file, cvefile_link)
+bb.plain("Complete CVE report summary created at: %s" % cvefile_link)
 
 if d.getVar("CVE_CHECK_FORMAT_JSON") == "1":
 json_summary_link_name = os.path.join(cvelogpath, 
d.getVar("CVE_CHECK_SUMMARY_FILE_NAME_JSON"))
@@ -193,15 +191,9 @@ python cve_check_write_rootfs_manifest () {
 bb.utils.mkdirhier(os.path.dirname(manifest_name))
 shutil.copyfile(cve_tmp_file, manifest_name)
 
-if manifest_name and os.path.exists(manifest_name):
-manifest_link = os.path.join(deploy_dir, "%s.cve" % link_name)
-# if they are the same don't create the link
-if manifest_link != manifest_name:
-# If we already have another manifest, update symlinks
-if os.path.exists(os.path.realpath(manifest_link)):
-os.remove(manifest_link)
-os.symlink(os.path.basename(manifest_name), manifest_link)
-bb.plain("Image CVE report stored in: %s" % manifest_name)
+manifest_link = os.path.join(deploy_dir, "%s.cve" % link_name)
+update_symlinks(manifest_name, manifest_link)
+bb.plain("Image CVE report stored in: %s" % manifest_name)
 
 if d.getVar("CVE_CHECK_FORMAT_JSON") == "1":
 link_path = os.path.join(deploy_dir, "%s.json" % link_name)
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166457): 
https://lists.openembedded.org/g/openembedded-core/message/166457
Mute This Topic: https://lists.openembedded.org/mt/91492156/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 10/11] cve-check: Only include installed packages for rootfs manifest

From: Ernst Sjöstrand 

Before this the rootfs manifest and the summary were identical.
We should separate the summary and rootfs manifest more clearly,
now the summary is for all CVEs and the rootfs manifest is only for
things in that image. This is even more useful if you build multiple
images.

Signed-off-by: Ernst Sjöstrand 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit 3b8cc6fc45f0ea5677729ee2b1819bdc7a441ab1)
Signed-off-by: Steve Sakoman 
(cherry picked from commit 65498411d73e8008d5550c2d0a1148f990717587)
Signed-off-by: Steve Sakoman 
---
 meta/classes/cve-check.bbclass | 69 ++
 1 file changed, 54 insertions(+), 15 deletions(-)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 3cae0e8eb2..29b276e491 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -171,6 +171,8 @@ python cve_check_write_rootfs_manifest () {
 """
 
 import shutil
+import json
+from oe.rootfs import image_list_installed_packages
 from oe.cve_check import cve_check_merge_jsons
 
 if d.getVar("CVE_CHECK_COPY_FILES") == "1":
@@ -181,26 +183,63 @@ python cve_check_write_rootfs_manifest () {
 if os.path.exists(deploy_file_json):
 bb.utils.remove(deploy_file_json)
 
-if os.path.exists(d.getVar("CVE_CHECK_TMP_FILE")):
-bb.note("Writing rootfs CVE manifest")
-deploy_dir = d.getVar("DEPLOY_DIR_IMAGE")
-link_name = d.getVar("IMAGE_LINK_NAME")
+# Create a list of relevant recipies
+recipies = set()
+for pkg in list(image_list_installed_packages(d)):
+pkg_info = os.path.join(d.getVar('PKGDATA_DIR'),
+'runtime-reverse', pkg)
+pkg_data = oe.packagedata.read_pkgdatafile(pkg_info)
+recipies.add(pkg_data["PN"])
+
+bb.note("Writing rootfs CVE manifest")
+deploy_dir = d.getVar("DEPLOY_DIR_IMAGE")
+link_name = d.getVar("IMAGE_LINK_NAME")
+
+json_data = {"version":"1", "package": []}
+text_data = ""
+enable_json = d.getVar("CVE_CHECK_FORMAT_JSON") == "1"
+enable_text = d.getVar("CVE_CHECK_FORMAT_TEXT") == "1"
+
+save_pn = d.getVar("PN")
+
+for pkg in recipies:
+# To be able to use the CVE_CHECK_RECIPE_FILE variable we have to 
evaluate
+# it with the different PN names set each time.
+d.setVar("PN", pkg)
+if enable_text:
+pkgfilepath = d.getVar("CVE_CHECK_RECIPE_FILE")
+if os.path.exists(pkgfilepath):
+with open(pkgfilepath) as pfile:
+text_data += pfile.read()
+
+if enable_json:
+pkgfilepath = d.getVar("CVE_CHECK_RECIPE_FILE_JSON")
+if os.path.exists(pkgfilepath):
+with open(pkgfilepath) as j:
+data = json.load(j)
+cve_check_merge_jsons(json_data, data)
+
+d.setVar("PN", save_pn)
+
+if enable_text:
+link_path = os.path.join(deploy_dir, "%s.cve" % link_name)
 manifest_name = d.getVar("CVE_CHECK_MANIFEST")
-cve_tmp_file = d.getVar("CVE_CHECK_TMP_FILE")
 
-bb.utils.mkdirhier(os.path.dirname(manifest_name))
-shutil.copyfile(cve_tmp_file, manifest_name)
+with open(manifest_name, "w") as f:
+f.write(text_data)
 
-manifest_link = os.path.join(deploy_dir, "%s.cve" % link_name)
-update_symlinks(manifest_name, manifest_link)
+update_symlinks(manifest_name, link_path)
 bb.plain("Image CVE report stored in: %s" % manifest_name)
 
-if d.getVar("CVE_CHECK_FORMAT_JSON") == "1":
-link_path = os.path.join(deploy_dir, "%s.json" % link_name)
-manifest_path = d.getVar("CVE_CHECK_MANIFEST_JSON")
-bb.note("Generating JSON CVE manifest")
-generate_json_report(d, manifest_path, link_path)
-bb.plain("Image CVE JSON report stored in: %s" % link_path)
+if enable_json:
+link_path = os.path.join(deploy_dir, "%s.json" % link_name)
+manifest_name = d.getVar("CVE_CHECK_MANIFEST_JSON")
+
+with open(manifest_name, "w") as f:
+json.dump(json_data, f, indent=2)
+
+update_symlinks(manifest_name, link_path)
+bb.plain("Image CVE JSON report stored in: %s" % manifest_name)
 }
 
 ROOTFS_POSTPROCESS_COMMAND_prepend = "${@'cve_check_write_rootfs_manifest; ' 
if d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166458): 
https://lists.openembedded.org/g/openembedded-core/message/166458
Mute This Topic: https://lists.openembedded.org/mt/91492159/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 08/11] cve-check.bbclass: Added do_populate_sdk[recrdeptask].

From: leimaohui 

As product, sdk should do cve check as well as rootfs.

Signed-off-by: Lei Maohui 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit cc17753935c5f9e08aaa6c5886f059303147c07b)
Signed-off-by: Steve Sakoman 
---
 meta/classes/cve-check.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 34c38bdf2d..f7ed2a6ae9 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -213,6 +213,7 @@ python cve_check_write_rootfs_manifest () {
 
 ROOTFS_POSTPROCESS_COMMAND_prepend = "${@'cve_check_write_rootfs_manifest; ' 
if d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
 do_rootfs[recrdeptask] += "${@'do_cve_check' if 
d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
+do_populate_sdk[recrdeptask] += "${@'do_cve_check' if 
d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
 
 def get_patches_cves(d):
 """
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166456): 
https://lists.openembedded.org/g/openembedded-core/message/166456
Mute This Topic: https://lists.openembedded.org/mt/91492155/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 11/11] cve-check: Allow warnings to be disabled