Re: Patchtest results for [OE-core][PATCH 1/2] patchtest: Fix grammar in log output
On 2/15/24 at 22:05, Patchtest wrote: Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/1-2-patchtest-Fix-grammar-in-log-output.patch FAIL: test commit message presence: Please include a commit message on your patch explaining the change (test_mbox.TestMbox.test_commit_message_presence) Brilliant! Patchtest is now reaching self-awareness :) Cheers Michael -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195739): https://lists.openembedded.org/g/openembedded-core/message/195739 Mute This Topic: https://lists.openembedded.org/mt/104381528/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 3/3] vulkan-samples: Update to tip of trunk
lets drop this patch, I think it needs some submodule syncing but I will let upstream do it. On Thu, Feb 15, 2024 at 1:23 PM Richard Purdie wrote: > > On Wed, 2024-02-14 at 12:47 -0800, Khem Raj wrote: > > This gets the needed fixes for llvm-18 based builds > > spdlog musl patches has been merged in the updated version module > > 32bit backport is also available in this version > > > > Signed-off-by: Khem Raj > > Breaks with multilib: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/8446/steps/11/logs/stdio > https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/5699/steps/11/logs/stdio > > Breaks with musl: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/8583/steps/11/logs/stdio > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/8606 > > Cheers, > > Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195738): https://lists.openembedded.org/g/openembedded-core/message/195738 Mute This Topic: https://lists.openembedded.org/mt/104361298/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] openssh: Add a work around for ICE on mips/mips64
I’m
On Thu, Feb 15, 2024 at 5:12 PM Khem Raj wrote:
> On Thu, Feb 15, 2024 at 1:29 PM Richard Purdie
> wrote:
> >
> > Unfortunately the new openssh version has an ICE on mips. This looks
> similar to:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
> >
> > Given how long these have been open, workaround the issue by disabling
> the compiler
> > hardening options on mips.
> >
> > It is likely better to do this than have the open CVEs for everyone
> > as we can't upgrade.
> >
> > An example:
> >
> > | during RTL pass: zero_call_used_regs
> > | clientloop.c: In function 'client_loop':
> > | clientloop.c:1699:1: internal compiler error: in int_mode_for_mode, at
> stor-layout.cc:407
> > | 1699 | }
> > | | ^
> > | 0x14d0acc internal_error(char const*, ...)
> > | ???:0
> > | 0x5cf765 fancy_abort(char const*, int, char const*)
> > | ???:0
> > | 0x826f1f emit_move_insn_1(rtx_def*, rtx_def*)
> > | ???:0
> > | 0x8270c5 emit_move_insn(rtx_def*, rtx_def*)
> > | ???:0
> > | 0xb7b994 default_zero_call_used_regs(HARD_REG_SET)
> > | ???:0
> > | Please submit a full bug report, with preprocessed source (by using
> -freport-bug).
> > | Please include the complete backtrace with any bug report.
> >
> > Signed-off-by: Richard Purdie
> > ---
> > meta/recipes-connectivity/openssh/openssh_9.6p1.bb | 4
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> > index 6366cefdf96..1fd36a266fd 100644
> > --- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> > +++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> > @@ -81,6 +81,10 @@ EXTRA_OECONF = "'LOGIN_PROGRAM=${base_bindir}/login' \
> > # musl doesn't implement wtmp/utmp and logwtmp
> > EXTRA_OECONF:append:libc-musl = " --disable-wtmp --disable-lastlog"
> >
> > +# Work around ICE on mips/mips64 starting in 9.6p1
> > +EXTRA_OECONF:append:mips = " --without-hardening"
> > +EXTRA_OECONF:append:mips64 = " --without-hardening"
>
> Perhaps just use mipsarch override since I imagine it will impact all
> kinds of mips.
>
Just a data point, both qemumips and qemumips64 are based on the ~2006-ish
“Malta” machine. I don’t know yet if that set of tuning is a factor (vs
“Boston” which is more like 2015). I’ll still follow through with a bug
report on gcc bugzilla.
> > +
> > # Since we do not depend on libbsd, we do not want configure to use it
> > # just because it finds libutil.h. But, specifying --disable-libutil
> > # causes compile errors, so...
> > --
> > 2.40.1
> >
> >
> >
> >
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195737):
https://lists.openembedded.org/g/openembedded-core/message/195737
Mute This Topic: https://lists.openembedded.org/mt/104381904/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 7/8] kernel: fix localversion in v6.3+
On 2/15/2024 7:43 PM, Steve Sakoman wrote:
On Thu, Feb 15, 2024 at 3:20 PM Ryan Eatmon wrote:
With this patch in place we are seeing a breakage on our kernel builds.
This patch was cherry picked from master, but the next patch on this
file in master removes the LOCALVERSION setting...
https://git.openembedded.org/openembedded-core/commit/meta/classes-recipe/kernel-arch.bbclass?h=master-next=b378eec156998eea55ba61e59103cb34fab0d07c
There is a disconnect here. Why did we change kirkstone, a stable LTS
version with a partial patch series based on master?
The original kirkstone backport request for this patch was sent to the
list for review on February 9.
There were no comments or objections, so I added it to the patch test
queue. No issues were encountered on the autobuilder, so I sent this
patch (along with the rest of the patch queue) to the list for a
second review opportunity on February 12. Once again there were no
comments or objections, so it was merged today February 15.
I follow this process because I'm not smart enough, nor do I have time
enough to thoroughly research all implications of every patch. I rely
on autobuilder testing and community review to minimize breakage.
This normally works quite well, but this time it didn't. I'll revert
this patch and if someone would like to resubmit a proper series to
deal with the issue it is trying to fix I will consider it and run it
through the same process.
I can appreciate that. My comment was more for the person who sent the
patch in the first place. You are doing a great job. I will try and
pay attention for a replacement patch coming in and review as well.
Steve
On 2/12/2024 7:54 AM, Steve Sakoman wrote:
From: Bruce Ashfield
During testing of the v6.4 reference kernel, it was noticed that
on-target modules no longer matched the magic value of the running
kernel.
This was due to a different localversion in the cross built kernel
and the scripts / resources created on target.
This was due to changes in the setlocalversion script introduced
in the v6.3 series.
The .scmversion file is no longer used (or packaged) to inhibit
the addition of a "+" (through querying of the git status of the
kernel) or the setting of a local version.
We recently introduced the KERNEL_LOCALVERSION variable to allow
recipes to place a value in .scmversion, so we extend the use of
that variable to kernel-arch.bbclass and use it to set the
exported variable LOCALVERSION.
We must do it at the kernel-arch level, as the variable must be
exported in any kernel build to ensure that setlocalversion always
correctly sets the localversion.
Signed-off-by: Bruce Ashfield
Signed-off-by: Richard Purdie
Cherry-picked from master 765b13b7305c8d2f222cfc66d77c02e6a088c691
Signed-off-by: Andreas Helbech Kleist
Signed-off-by: Steve Sakoman
---
meta/classes/kernel-arch.bbclass | 7 +++
meta/classes/kernel.bbclass | 10 --
2 files changed, 15 insertions(+), 2 deletions(-)
diff --git a/meta/classes/kernel-arch.bbclass b/meta/classes/kernel-arch.bbclass
index 4cd08b96fb..0a79dea0af 100644
--- a/meta/classes/kernel-arch.bbclass
+++ b/meta/classes/kernel-arch.bbclass
@@ -66,3 +66,10 @@ KERNEL_LD = "${CCACHE}${HOST_PREFIX}ld.bfd
${HOST_LD_KERNEL_ARCH}"
KERNEL_AR = "${CCACHE}${HOST_PREFIX}ar ${HOST_AR_KERNEL_ARCH}"
TOOLCHAIN ?= "gcc"
+# 6.3+ requires the variable LOCALVERSION to be set to not get a "+" in
+# the local version. Having it empty means nothing will be added, and any
+# value will be appended to the local kernel version. This replaces the
+# use of .scmversion file for setting a localversion without using
+# the CONFIG_LOCALVERSION option.
+KERNEL_LOCALVERSION ??= ""
+export LOCALVERSION ?= "${KERNEL_LOCALVERSION}"
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 5951347361..940f1a3cf4 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -418,7 +418,7 @@ do_compile_kernelmodules() {
if (grep -q -i -e '^CONFIG_MODULES=y$' ${B}/.config); then
oe_runmake -C ${B} ${PARALLEL_MAKE} modules ${KERNEL_EXTRA_ARGS}
- # Module.symvers gets updated during the
+ # Module.symvers gets updated during the
# building of the kernel modules. We need to
# update this in the shared workdir since some
# external kernel modules has a dependency on
@@ -635,7 +635,13 @@ kernel_do_configure() {
# $ scripts/setlocalversion . => +
# $ make kernelversion => 2.6.37
# $ make kernelrelease => 2.6.37+
- touch ${B}/.scmversion ${S}/.scmversion
+ # See kernel-arch.bbclass for post v6.3 removal of the extra
+ # + in localversion. .scmversion is no longer used, and the
+ # variable LOCALVERSION must be used
+ if [ ! -e ${B}/.scmversion -a ! -e ${S}/.scmversion ]; then
+ echo ${KERNEL_LOCALVERSION} > ${B}/.scmversion
+ echo
Re: [OE-core][kirkstone 7/8] kernel: fix localversion in v6.3+
On Thu, Feb 15, 2024 at 3:20 PM Ryan Eatmon wrote:
>
>
> With this patch in place we are seeing a breakage on our kernel builds.
> This patch was cherry picked from master, but the next patch on this
> file in master removes the LOCALVERSION setting...
>
> https://git.openembedded.org/openembedded-core/commit/meta/classes-recipe/kernel-arch.bbclass?h=master-next=b378eec156998eea55ba61e59103cb34fab0d07c
>
>
> There is a disconnect here. Why did we change kirkstone, a stable LTS
> version with a partial patch series based on master?
The original kirkstone backport request for this patch was sent to the
list for review on February 9.
There were no comments or objections, so I added it to the patch test
queue. No issues were encountered on the autobuilder, so I sent this
patch (along with the rest of the patch queue) to the list for a
second review opportunity on February 12. Once again there were no
comments or objections, so it was merged today February 15.
I follow this process because I'm not smart enough, nor do I have time
enough to thoroughly research all implications of every patch. I rely
on autobuilder testing and community review to minimize breakage.
This normally works quite well, but this time it didn't. I'll revert
this patch and if someone would like to resubmit a proper series to
deal with the issue it is trying to fix I will consider it and run it
through the same process.
Steve
> On 2/12/2024 7:54 AM, Steve Sakoman wrote:
> > From: Bruce Ashfield
> >
> > During testing of the v6.4 reference kernel, it was noticed that
> > on-target modules no longer matched the magic value of the running
> > kernel.
> >
> > This was due to a different localversion in the cross built kernel
> > and the scripts / resources created on target.
> >
> > This was due to changes in the setlocalversion script introduced
> > in the v6.3 series.
> >
> > The .scmversion file is no longer used (or packaged) to inhibit
> > the addition of a "+" (through querying of the git status of the
> > kernel) or the setting of a local version.
> >
> > We recently introduced the KERNEL_LOCALVERSION variable to allow
> > recipes to place a value in .scmversion, so we extend the use of
> > that variable to kernel-arch.bbclass and use it to set the
> > exported variable LOCALVERSION.
> >
> > We must do it at the kernel-arch level, as the variable must be
> > exported in any kernel build to ensure that setlocalversion always
> > correctly sets the localversion.
> >
> > Signed-off-by: Bruce Ashfield
> > Signed-off-by: Richard Purdie
> >
> > Cherry-picked from master 765b13b7305c8d2f222cfc66d77c02e6a088c691
> >
> > Signed-off-by: Andreas Helbech Kleist
> > Signed-off-by: Steve Sakoman
> > ---
> > meta/classes/kernel-arch.bbclass | 7 +++
> > meta/classes/kernel.bbclass | 10 --
> > 2 files changed, 15 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/classes/kernel-arch.bbclass
> > b/meta/classes/kernel-arch.bbclass
> > index 4cd08b96fb..0a79dea0af 100644
> > --- a/meta/classes/kernel-arch.bbclass
> > +++ b/meta/classes/kernel-arch.bbclass
> > @@ -66,3 +66,10 @@ KERNEL_LD = "${CCACHE}${HOST_PREFIX}ld.bfd
> > ${HOST_LD_KERNEL_ARCH}"
> > KERNEL_AR = "${CCACHE}${HOST_PREFIX}ar ${HOST_AR_KERNEL_ARCH}"
> > TOOLCHAIN ?= "gcc"
> >
> > +# 6.3+ requires the variable LOCALVERSION to be set to not get a "+" in
> > +# the local version. Having it empty means nothing will be added, and any
> > +# value will be appended to the local kernel version. This replaces the
> > +# use of .scmversion file for setting a localversion without using
> > +# the CONFIG_LOCALVERSION option.
> > +KERNEL_LOCALVERSION ??= ""
> > +export LOCALVERSION ?= "${KERNEL_LOCALVERSION}"
> > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > index 5951347361..940f1a3cf4 100644
> > --- a/meta/classes/kernel.bbclass
> > +++ b/meta/classes/kernel.bbclass
> > @@ -418,7 +418,7 @@ do_compile_kernelmodules() {
> > if (grep -q -i -e '^CONFIG_MODULES=y$' ${B}/.config); then
> > oe_runmake -C ${B} ${PARALLEL_MAKE} modules
> > ${KERNEL_EXTRA_ARGS}
> >
> > - # Module.symvers gets updated during the
> > + # Module.symvers gets updated during the
> > # building of the kernel modules. We need to
> > # update this in the shared workdir since some
> > # external kernel modules has a dependency on
> > @@ -635,7 +635,13 @@ kernel_do_configure() {
> > # $ scripts/setlocalversion . => +
> > # $ make kernelversion => 2.6.37
> > # $ make kernelrelease => 2.6.37+
> > - touch ${B}/.scmversion ${S}/.scmversion
> > + # See kernel-arch.bbclass for post v6.3 removal of the extra
> > + # + in localversion. .scmversion is no longer used, and the
> > + # variable LOCALVERSION must be used
> > + if [ ! -e ${B}/.scmversion -a ! -e ${S}/.scmversion ]; then
> > + echo ${KERNEL_LOCALVERSION} >
Re: [OE-core][kirkstone 7/8] kernel: fix localversion in v6.3+
With this patch in place we are seeing a breakage on our kernel builds.
This patch was cherry picked from master, but the next patch on this
file in master removes the LOCALVERSION setting...
https://git.openembedded.org/openembedded-core/commit/meta/classes-recipe/kernel-arch.bbclass?h=master-next=b378eec156998eea55ba61e59103cb34fab0d07c
There is a disconnect here. Why did we change kirkstone, a stable LTS
version with a partial patch series based on master?
On 2/12/2024 7:54 AM, Steve Sakoman wrote:
From: Bruce Ashfield
During testing of the v6.4 reference kernel, it was noticed that
on-target modules no longer matched the magic value of the running
kernel.
This was due to a different localversion in the cross built kernel
and the scripts / resources created on target.
This was due to changes in the setlocalversion script introduced
in the v6.3 series.
The .scmversion file is no longer used (or packaged) to inhibit
the addition of a "+" (through querying of the git status of the
kernel) or the setting of a local version.
We recently introduced the KERNEL_LOCALVERSION variable to allow
recipes to place a value in .scmversion, so we extend the use of
that variable to kernel-arch.bbclass and use it to set the
exported variable LOCALVERSION.
We must do it at the kernel-arch level, as the variable must be
exported in any kernel build to ensure that setlocalversion always
correctly sets the localversion.
Signed-off-by: Bruce Ashfield
Signed-off-by: Richard Purdie
Cherry-picked from master 765b13b7305c8d2f222cfc66d77c02e6a088c691
Signed-off-by: Andreas Helbech Kleist
Signed-off-by: Steve Sakoman
---
meta/classes/kernel-arch.bbclass | 7 +++
meta/classes/kernel.bbclass | 10 --
2 files changed, 15 insertions(+), 2 deletions(-)
diff --git a/meta/classes/kernel-arch.bbclass b/meta/classes/kernel-arch.bbclass
index 4cd08b96fb..0a79dea0af 100644
--- a/meta/classes/kernel-arch.bbclass
+++ b/meta/classes/kernel-arch.bbclass
@@ -66,3 +66,10 @@ KERNEL_LD = "${CCACHE}${HOST_PREFIX}ld.bfd
${HOST_LD_KERNEL_ARCH}"
KERNEL_AR = "${CCACHE}${HOST_PREFIX}ar ${HOST_AR_KERNEL_ARCH}"
TOOLCHAIN ?= "gcc"
+# 6.3+ requires the variable LOCALVERSION to be set to not get a "+" in
+# the local version. Having it empty means nothing will be added, and any
+# value will be appended to the local kernel version. This replaces the
+# use of .scmversion file for setting a localversion without using
+# the CONFIG_LOCALVERSION option.
+KERNEL_LOCALVERSION ??= ""
+export LOCALVERSION ?= "${KERNEL_LOCALVERSION}"
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 5951347361..940f1a3cf4 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -418,7 +418,7 @@ do_compile_kernelmodules() {
if (grep -q -i -e '^CONFIG_MODULES=y$' ${B}/.config); then
oe_runmake -C ${B} ${PARALLEL_MAKE} modules ${KERNEL_EXTRA_ARGS}
- # Module.symvers gets updated during the
+ # Module.symvers gets updated during the
# building of the kernel modules. We need to
# update this in the shared workdir since some
# external kernel modules has a dependency on
@@ -635,7 +635,13 @@ kernel_do_configure() {
# $ scripts/setlocalversion . => +
# $ make kernelversion => 2.6.37
# $ make kernelrelease => 2.6.37+
- touch ${B}/.scmversion ${S}/.scmversion
+ # See kernel-arch.bbclass for post v6.3 removal of the extra
+ # + in localversion. .scmversion is no longer used, and the
+ # variable LOCALVERSION must be used
+ if [ ! -e ${B}/.scmversion -a ! -e ${S}/.scmversion ]; then
+ echo ${KERNEL_LOCALVERSION} > ${B}/.scmversion
+ echo ${KERNEL_LOCALVERSION} > ${S}/.scmversion
+ fi
if [ "${S}" != "${B}" ] && [ -f "${S}/.config" ] && [ ! -f "${B}/.config" ]; then
mv "${S}/.config" "${B}/.config"
--
Ryan Eatmonreat...@ti.com
-
Texas Instruments, Inc. - LCPD - MGTS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195734):
https://lists.openembedded.org/g/openembedded-core/message/195734
Mute This Topic: https://lists.openembedded.org/mt/104311283/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] openssh: Add a work around for ICE on mips/mips64
On Thu, Feb 15, 2024 at 1:29 PM Richard Purdie
wrote:
>
> Unfortunately the new openssh version has an ICE on mips. This looks similar
> to:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
>
> Given how long these have been open, workaround the issue by disabling the
> compiler
> hardening options on mips.
>
> It is likely better to do this than have the open CVEs for everyone
> as we can't upgrade.
>
> An example:
>
> | during RTL pass: zero_call_used_regs
> | clientloop.c: In function 'client_loop':
> | clientloop.c:1699:1: internal compiler error: in int_mode_for_mode, at
> stor-layout.cc:407
> | 1699 | }
> | | ^
> | 0x14d0acc internal_error(char const*, ...)
> | ???:0
> | 0x5cf765 fancy_abort(char const*, int, char const*)
> | ???:0
> | 0x826f1f emit_move_insn_1(rtx_def*, rtx_def*)
> | ???:0
> | 0x8270c5 emit_move_insn(rtx_def*, rtx_def*)
> | ???:0
> | 0xb7b994 default_zero_call_used_regs(HARD_REG_SET)
> | ???:0
> | Please submit a full bug report, with preprocessed source (by using
> -freport-bug).
> | Please include the complete backtrace with any bug report.
>
> Signed-off-by: Richard Purdie
> ---
> meta/recipes-connectivity/openssh/openssh_9.6p1.bb | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> index 6366cefdf96..1fd36a266fd 100644
> --- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> +++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
> @@ -81,6 +81,10 @@ EXTRA_OECONF = "'LOGIN_PROGRAM=${base_bindir}/login' \
> # musl doesn't implement wtmp/utmp and logwtmp
> EXTRA_OECONF:append:libc-musl = " --disable-wtmp --disable-lastlog"
>
> +# Work around ICE on mips/mips64 starting in 9.6p1
> +EXTRA_OECONF:append:mips = " --without-hardening"
> +EXTRA_OECONF:append:mips64 = " --without-hardening"
Perhaps just use mipsarch override since I imagine it will impact all
kinds of mips.
> +
> # Since we do not depend on libbsd, we do not want configure to use it
> # just because it finds libutil.h. But, specifying --disable-libutil
> # causes compile errors, so...
> --
> 2.40.1
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195733):
https://lists.openembedded.org/g/openembedded-core/message/195733
Mute This Topic: https://lists.openembedded.org/mt/104381904/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/1] sstatesig: Allow exclusion of the root directory for do_package
From: Richard Purdie
The package task references WORKDIR at it's top level and we can't
easily make the timestamp for that determnistic due to writes to files
there and in other subdirs. We could try and force it to a specific value
but it is easier to just remove it from the package task, we don't need
it there or care about it in this case.
Signed-off-by: Jate Sujjavanich
(cherry picked from commit 9cceeb906527f90d8dd3aad75aa3a8805e2a1df5)
Signed-off-by: Richard Purdie
---
meta/lib/oe/sstatesig.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index aeceb100d7..65bb4efe25 100644
--- a/meta/lib/oe/sstatesig.py
+++ b/meta/lib/oe/sstatesig.py
@@ -480,8 +480,10 @@ def OEOuthashBasic(path, sigfile, task, d):
if "package_write_" in task or task == "package_qa":
include_owners = False
include_timestamps = False
+include_root = True
if task == "package":
include_timestamps = d.getVar('BUILD_REPRODUCIBLE_BINARIES') == '1'
+include_root = False
extra_content = d.getVar('HASHEQUIV_HASH_VERSION')
try:
@@ -592,7 +594,8 @@ def OEOuthashBasic(path, sigfile, task, d):
update_hash("\n")
# Process this directory and all its child files
-process(root)
+if include_root or root != ".":
+process(root)
for f in files:
if f == 'fixmepath':
continue
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195732):
https://lists.openembedded.org/g/openembedded-core/message/195732
Mute This Topic: https://lists.openembedded.org/mt/104384672/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 0/1] Backport do_package sstatesig fix
I found out that this backport is applicable to dunfell. This increased sstate reuse. Richard Purdie (1): sstatesig: Allow exclusion of the root directory for do_package meta/lib/oe/sstatesig.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195731): https://lists.openembedded.org/g/openembedded-core/message/195731 Mute This Topic: https://lists.openembedded.org/mt/104384668/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 3/6] devtool: code: Add source mapping for debug source files
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> When launching the debug configuration, the source files from the
> debug
> rootfs were openened in the editor instead of the local workspace
> files.
> We add an exception to properly map them to the file being developed
> and
> compiled by the IDE integration. This also more closely matches what
> the
> user would expect compared to native development.
>
> This is also true for the devtool fallback mode.
This sounds a little bit unexpected to me. With devtool deploy-target
the binaries which are copied to the target device have still the
absolute rpath from the real build host. The are not packaged.
I would expect something like this when a packaged binary would be
debugged. But I'm not sure if that would make sense and should be
supported.
> ---
> scripts/lib/devtool/ide_plugins/ide_code.py | 1 +
> scripts/lib/devtool/ide_sdk.py | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py
> b/scripts/lib/devtool/ide_plugins/ide_code.py
> index b2193130d2e..c063b7d0590 100644
> --- a/scripts/lib/devtool/ide_plugins/ide_code.py
> +++ b/scripts/lib/devtool/ide_plugins/ide_code.py
> @@ -234,6 +234,7 @@ class IdeVSCode(IdeBase):
> if gdb_cross_config.image_recipe.rootfs_dbg:
> launch_config['additionalSOLibSearchPath'] =
> modified_recipe.solib_search_path_str(
> gdb_cross_config.image_recipe)
> + src_file_map[os.path.join("/usr/src/debug",
> modified_recipe.pn, modified_recipe.pv)] = "${workspaceFolder}"
> src_file_map["/usr/src/debug"] = os.path.join(
> gdb_cross_config.image_recipe.rootfs_dbg, "usr",
> "src", "debug")
> else:
> diff --git a/scripts/lib/devtool/ide_sdk.py
> b/scripts/lib/devtool/ide_sdk.py
> index a82ab572998..1e36f2b2093 100755
> --- a/scripts/lib/devtool/ide_sdk.py
> +++ b/scripts/lib/devtool/ide_sdk.py
> @@ -356,6 +356,7 @@ class RecipeModified:
> 'PACKAGE_DEBUG_SPLIT_STYLE')
> self.path = recipe_d.getVar('PATH')
> self.pn = recipe_d.getVar('PN')
> + self.pv = recipe_d.getVar('PV')
> self.recipe_sysroot = os.path.realpath(
> recipe_d.getVar('RECIPE_SYSROOT'))
> self.recipe_sysroot_native = os.path.realpath(
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195730):
https://lists.openembedded.org/g/openembedded-core/message/195730
Mute This Topic: https://lists.openembedded.org/mt/104376744/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 6/6] devtool: code: Provide a generic C++ configuration
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> By default, the cpptools VSCode extension will use the host's headers
> and flags for linting. This results in a lot of include errors and
> misleading definitions. Even though this generic configuration
> doesn't
> include all the depenendencies, it is a proper fallback for recipe
> classes we do not accurately cover, with at least the right sysroot.
>
> Additionally, ide-sdk automatically detects and provides a
> launch.json
> configuration for autotools recipes so we should recommend the C++
> extensions for them.
>
> If the recipe is of another class (like Python), then the
> configuration
> will be generated but probably useless to the user. We'd need a
> mecanism
> to know if the recipe contains C/C++ but I'm not aware of any
> class-agnostic way to do it.
> ---
> scripts/lib/devtool/ide_plugins/ide_code.py | 25 ---
> --
> scripts/lib/devtool/ide_sdk.py | 3 +++
> 2 files changed, 18 insertions(+), 10 deletions(-)
>
> diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py
> b/scripts/lib/devtool/ide_plugins/ide_code.py
> index 7b683c74086..51cf2c8a736 100644
> --- a/scripts/lib/devtool/ide_plugins/ide_code.py
> +++ b/scripts/lib/devtool/ide_plugins/ide_code.py
> @@ -157,31 +157,33 @@ class IdeVSCode(IdeBase):
> IdeBase.update_json_file(
> self.dot_code_dir(modified_recipe), settings_file,
> settings_dict)
>
> + def __vscode_extensions_generic(self, modified_recipe,
> recommendations):
Here is a condition needed. This is only valid for some C/C++ recipes.
But now these extensions are also installed e.g. for Rust, Go, Python
which is wrong.
> + recommendations += [
> + "ms-vscode.cpptools",
> + "ms-vscode.cpptools-extension-pack",
> + "ms-vscode.cpptools-themes"
> + ]
> +
> def __vscode_extensions_cmake(self, modified_recipe,
> recommendations):
> if modified_recipe.build_tool is not BuildTool.CMAKE:
> return
> recommendations += [
> "twxs.cmake",
> - "ms-vscode.cmake-tools",
> - "ms-vscode.cpptools",
> - "ms-vscode.cpptools-extension-pack",
> - "ms-vscode.cpptools-themes"
> + "ms-vscode.cmake-tools"
> ]
>
> def __vscode_extensions_meson(self, modified_recipe,
> recommendations):
> if modified_recipe.build_tool is not BuildTool.MESON:
> return
> recommendations += [
> - 'mesonbuild.mesonbuild',
> - "ms-vscode.cpptools",
> - "ms-vscode.cpptools-extension-pack",
> - "ms-vscode.cpptools-themes"
> + 'mesonbuild.mesonbuild'
> ]
>
> def vscode_extensions(self, modified_recipe):
> recommendations = []
> self.__vscode_extensions_cmake(modified_recipe,
> recommendations)
> self.__vscode_extensions_meson(modified_recipe,
> recommendations)
> + self.__vscode_extensions_generic(modified_recipe,
> recommendations)
> extensions_file = 'extensions.json'
> IdeBase.update_json_file(
> self.dot_code_dir(modified_recipe), extensions_file,
> {"recommendations": recommendations})
> @@ -194,8 +196,11 @@ class IdeVSCode(IdeBase):
> properties_dict["configurationProvider"] = "ms-
> vscode.cmake-tools"
> elif modified_recipe.build_tool is BuildTool.MESON:
> properties_dict["configurationProvider"] =
> "mesonbuild.mesonbuild"
> - else: # no C/C++ build
> - return
Same issue as above: There are many recipes were a C/C++ compiler
configuration is wrong. As a next step we might add e.g.
elif autotools
...
else
return
but we cannot add a general else statement here.
> + else:
> + # Provide a generic linting configuration
> + # We provide a C++ configuration with the proper sysroot
> + properties_dict["compilerPath"] =
> os.path.join(modified_recipe.staging_bindir_toolchain,
> modified_recipe.cxx.split()[0])
> + properties_dict["compilerArgs"] =
> modified_recipe.cxx.split()[1:]
>
> properties_dicts = {
> "configurations": [
> diff --git a/scripts/lib/devtool/ide_sdk.py
> b/scripts/lib/devtool/ide_sdk.py
> index 1e36f2b2093..c82b150a83e 100755
> --- a/scripts/lib/devtool/ide_sdk.py
> +++ b/scripts/lib/devtool/ide_sdk.py
> @@ -345,6 +345,7 @@ class RecipeModified:
> self.base_libdir = recipe_d.getVar('base_libdir')
> self.bblayers = recipe_d.getVar('BBLAYERS').split()
> self.bpn = recipe_d.getVar('BPN')
> + self.cxx = recipe_d.getVar('CXX')
> self.d = recipe_d.getVar('D')
> self.fakerootcmd = recipe_d.getVar('FAKEROOTCMD')
> self.fakerootenv = recipe_d.getVar('FAKEROOTENV')
> @@ -361,6 +362,8 @@ class RecipeModified:
> recipe_d.getVar('RECIPE_SYSROOT'))
>
Re: [OE-core] [PATCH 1/6] devtool: ide: Fix topdir exception for fallback mode
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> An exception was raised because we did not have the topdir attribute
> which was used in fallback mode (non cmake/meson recipes).
>
> Already in the merge queue in Adrian's latest patches.
> ---
> scripts/lib/devtool/ide_sdk.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/lib/devtool/ide_sdk.py
> b/scripts/lib/devtool/ide_sdk.py
> index 3986dc1436a..db2e95616be 100755
> --- a/scripts/lib/devtool/ide_sdk.py
> +++ b/scripts/lib/devtool/ide_sdk.py
> @@ -366,6 +366,7 @@ class RecipeModified:
> self.target_arch = recipe_d.getVar('TARGET_ARCH')
> self.topdir = recipe_d.getVar('TOPDIR')
> self.workdir = os.path.realpath(recipe_d.getVar('WORKDIR'))
> + self.topdir = os.path.realpath(recipe_d.getVar('TOPDIR'))
I think this patch is not needed. Two lines above the variable is
already initialized.
Some time ago there was an exception but it is fixes on master-next
already.
>
> self.__init_exported_variables(recipe_d)
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195728):
https://lists.openembedded.org/g/openembedded-core/message/195728
Mute This Topic: https://lists.openembedded.org/mt/104376741/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 v4 1/2] vscode: drop .vscode folder
There is a new official bitbake plugin:
https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake
This plugin automatically updates the .vscode/settings.json file.
Having the settings.json file in git and a plugin which modifies this
file is not ideal. It can lead to anoying situations especially when
working with git. For example a git stash reverts the settings which are
automatically applied by the plugin. While git stashed the settings.json
file the plugin immediately changes the file again and tries to run
bitbake based on the newly generated settings. When git does a stash pop
the restored settings.json file conflicts with the new settigns.json
file which has been generated while the git stash took place.
Therefore this patch removes the .vscode folder from git.
Removing the settings.json leads to other issues as already described
in the commit message of 5ff688fe29. But we still need another solution
where the settings.json file is not in Git.
Discussion is here:
https://github.com/yoctoproject/vscode-bitbake/issues/95
Signed-off-by: Adrian Freihofer
---
.gitignore| 1 -
.vscode/settings.json | 32
2 files changed, 33 deletions(-)
delete mode 100644 .vscode/settings.json
diff --git a/.gitignore b/.gitignore
index f6ce090b5fc..ec0447356e2 100644
--- a/.gitignore
+++ b/.gitignore
@@ -37,4 +37,3 @@ downloads/
sstate-cache/
toaster.sqlite
.vscode/
-vscode-bitbake-build/
diff --git a/.vscode/settings.json b/.vscode/settings.json
deleted file mode 100644
index 517a86d1bfa..000
--- a/.vscode/settings.json
+++ /dev/null
@@ -1,32 +0,0 @@
-{
-"files.watcherExclude": {
-"**/.git/**": true,
-"**/cache/**": true,
-"**/tmp*/**": true,
-"**/downloads/**": true,
-"**/sstate-cache/**": true,
-"**/vscode-bitbake-build/**": true,
-"**/workspace/sources/**": true,
-"**/workspace/attic/**": true
-},
-"files.exclude": {
-"**/.git/**": true,
-"**/cache/**": true,
-"**/tmp*/**": true,
-"**/downloads/**": true,
-"**/sstate-cache/**": true,
-"**/vscode-bitbake-build/**": true,
-"**/workspace/sources/**": true,
-"**/workspace/attic/**": true
-},
-"python.analysis.exclude": [
-"**/.git/**",
-"**/cache/**",
-"**/tmp*/**",
-"**/downloads/**",
-"**/sstate-cache/**",
-"**/vscode-bitbake-build/**",
-"**/workspace/sources/**",
-"**/workspace/attic/**"
-]
-}
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195726):
https://lists.openembedded.org/g/openembedded-core/message/195726
Mute This Topic: https://lists.openembedded.org/mt/104383554/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 v4 2/2] oe-init-build-env: generate .vscode from template
Provide a reasonable default configuration for VSCode and the
yocto.bitbake extension.
The generated default configuration is generic and minimal. It's mostly
supposed to prevent VSCode from OOM exceptions if the build directory is
in the scope of the indexer plugins of VSCode.
But it also configures the yocto-bitbake plugin to just work without
manual user interaction.
The configuration is only generated if VSCode is installed. Currently,
VSCode is one of many popular editors for Yocto/OE. Removing the check
would mean that the configuration would be generated by e.g. oe-selftest
or for users not using VSCode. If it should prove useful, the check can
be removed later.
Customization for other layers is possible. A layer might provide it's
own oe-setup-build-env script which calls the oe-setup-vscode script
from poky with different folders. But it's also possible to override the
oe-setup-vscode script by another layer with a custom implementation.
Signed-off-by: Adrian Freihofer
---
oe-init-build-env | 6 +++
scripts/oe-setup-vscode | 93 +
2 files changed, 99 insertions(+)
create mode 100755 scripts/oe-setup-vscode
diff --git a/oe-init-build-env b/oe-init-build-env
index 38333ab8582..82382f27078 100755
--- a/oe-init-build-env
+++ b/oe-init-build-env
@@ -47,6 +47,12 @@ export OEROOT
unset OEROOT
return 1
}
+
+# Generate an initial configuration for VSCode and the yocto-bitbake plugin.
+if command -v code > /dev/null && [ ! -d "$OEROOT/.vscode" ]; then
+oe-setup-vscode "$OEROOT" "$BUILDDIR"
+fi
+
unset OEROOT
[ -z "$BUILDDIR" ] || cd "$BUILDDIR"
diff --git a/scripts/oe-setup-vscode b/scripts/oe-setup-vscode
new file mode 100755
index 000..b8642780d57
--- /dev/null
+++ b/scripts/oe-setup-vscode
@@ -0,0 +1,93 @@
+#!/bin/sh
+
+usage() {
+echo "$0 "
+echo " OEINIT: path to directory where the .vscode folder is"
+echo " BUILDDIR: directory passed to the oe-init-setup-env script"
+}
+
+if [ "$#" -ne 2 ]; then
+usage
+exit 1
+fi
+
+OEINIT=$(readlink -f "$1")
+BUILDDIR=$(readlink -f "$2")
+VSCODEDIR=$OEINIT/.vscode
+
+if [ ! -d "$OEINIT" ] || [ ! -d "$BUILDDIR" ]; then
+echo "$OEINIT and/or $BUILDDIR directories are not present."
+exit 1
+fi
+
+VSCODE_SETTINGS=$VSCODEDIR/settings.json
+ws_builddir="$(echo "$BUILDDIR" | sed -e "s|$OEINIT|\${workspaceFolder}|g")"
+
+# If BUILDDIR is in scope of VSCode ensure VSCode does not try to index the
build folder.
+# This would lead to a busy CPU and finally to an OOM exception.
+mkdir -p "$VSCODEDIR"
+cat < "$VSCODE_SETTINGS"
+{
+"bitbake.pathToBitbakeFolder": "\${workspaceFolder}/bitbake",
+"bitbake.pathToEnvScript": "\${workspaceFolder}/oe-init-build-env",
+"bitbake.pathToBuildFolder": "$ws_builddir",
+"bitbake.commandWrapper": "",
+"bitbake.workingDirectory": "\${workspaceFolder}",
+"files.exclude": {
+"**/.git/**": true,
+"**/_build/**": true,
+"**/buildhistory/**": true,
+"**/cache/**": true,
+"**/downloads/**": true,
+"**/node_modules/**": true,
+"**/oe-logs/**": true,
+"**/oe-workdir/**": true,
+"**/sstate-cache/**": true,
+"**/tmp*/**": true,
+"**/workspace/attic/**": true,
+"**/workspace/sources/**": true
+},
+"files.watcherExclude": {
+"**/.git/**": true,
+"**/_build/**": true,
+"**/buildhistory/**": true,
+"**/cache/**": true,
+"**/downloads/**": true,
+"**/node_modules/**": true,
+"**/oe-logs/**": true,
+"**/oe-workdir/**": true,
+"**/sstate-cache/**": true,
+"**/tmp*/**": true,
+"**/workspace/attic/**": true,
+"**/workspace/sources/**": true
+},
+"python.analysis.exclude": [
+"**/_build/**",
+"**/.git/**",
+"**/buildhistory/**",
+"**/cache/**",
+"**/downloads/**",
+"**/node_modules/**",
+"**/oe-logs/**",
+"**/oe-workdir/**",
+"**/sstate-cache/**",
+"**/tmp*/**",
+"**/workspace/attic/**",
+"**/workspace/sources/**"
+]
+}
+EOMsettings
+
+
+# Ask the user if the yocto-bitbake extension should be installed
+VSCODE_EXTENSIONS=$VSCODEDIR/extensions.json
+cat < "$VSCODE_EXTENSIONS"
+{
+"recommendations": [
+"yocto-project.yocto-bitbake"
+]
+}
+EOMextensions
+
+echo "You had no $VSCODEDIR configuration."
+echo "These configuration files have therefore been created for you."
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195727):
https://lists.openembedded.org/g/openembedded-core/message/195727
Mute This Topic: https://lists.openembedded.org/mt/104383555/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 v4 0/2] oe-init-build-env: generate .vscode from template
Changes in comparison to v3: - Add more plugin settings as suggested by Enguerrand https://lists.openembedded.org/g/openembedded-core/message/195505 Changes in comparison to v2: - Do not integrate with the oe-setup-build or templating infrastrucutre. Provide a minimalistic script which is just good enough to generate a configuration which fits for poky. - Some details will be fixed on the plugin side which allows to simplify the generated bitbake plugin configuration to a minimum. With these patches, VSCode and the new plugin from https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake should work without any manual configuration once the oe-init-build-env script has been sourced. VSCode is also configured to not index the build folder and finally crash with an OOM exception. Without these patches, the issue is that the plugin automatically updates the .vscode/settings.json file. Having the settings.json file in git and a plugin which modifies this file is not ideal. It can lead to anoying situations especially when working with git. For example a git stash reverts the settings which are automatically applied by the plugin. While git stashed the settings.json file the plugin immediately changes the file again and tries to run bitbake based on the newly generated settings. When git does a stash pop the restored settings.json file conflicts with the new settigns.json file which has been generated while the git stash took place. Just removing the settings.json from git would lead to other issues as already described in the commit message of 5ff688fe29. And the plugin needs manual configuration. Discussion is here: https://github.com/yoctoproject/vscode-bitbake/issues/95 Adrian Freihofer (2): vscode: drop .vscode folder oe-init-build-env: generate .vscode from template .gitignore | 1 - .vscode/settings.json | 32 -- oe-init-build-env | 6 +++ scripts/oe-setup-vscode | 93 + 4 files changed, 99 insertions(+), 33 deletions(-) delete mode 100644 .vscode/settings.json create mode 100755 scripts/oe-setup-vscode -- 2.43.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195725): https://lists.openembedded.org/g/openembedded-core/message/195725 Mute This Topic: https://lists.openembedded.org/mt/104383553/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 0/6] devtool: ide: Improve VSCode support
> -Original Message- > From: openembedded-core@lists.openembedded.org > On Behalf Of Richard Purdie > Sent: den 15 februari 2024 18:11 > To: Enguerrand de Ribaucourt ; > openembedded-core@lists.openembedded.org > Cc: adrian.freiho...@gmail.com; ross.bur...@arm.com; > mohammed.r...@savoirfairelinux.com > Subject: Re: [OE-core] [PATCH 0/6] devtool: ide: Improve VSCode support > > On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote: > > These patches improve the VSCode support in devtool ide-sdk from > > Adrian Freihofer. > > > > I added a generic C++ configuration for the VScode > > extension while awaiting for autotools support. > > > > A refactoring is proposed for the meson class. Without absolute compiler > > paths, the linter inside VSCode will not be able to find the > > cross-compiler. Let me know if you have any concerns about this > > refactoring. > > > > The other bug fixes are relatively minor and make the tool work for some > > edge > > cases. > > I noticed none of the patches in this series have Signed-off-by lines > which needs to be fixed before we can merge them. Patchtest should be > along shortly to say that too! Actually, there does not seem to be any messages about this from patchtest. There have been other inconsistencies reported by it since, but not these... > > I need to think about and test the meson one a bit more as absolute > paths can be a source of problems. I've not looked into the others in > detail yet. > > Cheers, > > Richard //Peter -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195724): https://lists.openembedded.org/g/openembedded-core/message/195724 Mute This Topic: https://lists.openembedded.org/mt/104376742/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 00/12] python 3.12 related fixes
With these and 3 more patches sent to the bitbake-devel group oe-selftest looks already much better: oe-selftest -a Required tests failed (successes=502, skipped=6, failures=7, errors=3) eSDK.oeSDKExtSelfTest.test_image_generation_binary_feeds: ERROR eSDK.oeSDKExtSelfTest.test_install_libraries_headers: ERROR runcmd.RunCmdTests.test_result_assertion: ERROR (0.01s) runcmd.RunCmdTests.test_result_exception: ERROR (0.02s) distrodata.Distrodata.test_checkpkg: FAILED (132.52s) incompatible_lic.NoGPL3InImagesTests.test_core_image_full_cmdline_weston: FAILED (215.33s) runtime_test.TestImage.test_testimage_apt: FAILED (807.54s) runtime_test.TestImage.test_testimage_dnf: FAILED (1032.04s) runtime_test.TestImage.test_testimage_install: FAILED (110.76s) runtime_test.TestImage.test_testimage_virgl_gtk_sdl: FAILED (724.11s) runtime_test.TestImage.test_testimage_virgl_headless: FAILED (0.04s) Note: Some opengl/weston tests are currently also failing on master on my setup. Not sure why. Lets wait for the opinion of the official Fedora 39 runner. For what ever reason recipetool seams to work differently on my machine. recipetool create -o https://github.com/mesonbuild/meson;rev=0.52.1 creates a recipe named meson.bb, not a recipe pyhton3-meson.bb. Not sure if another is a patch required which fixes two test cases: test_recipetool_create_github test_recipetool_create_github_tarball or if this depends on the host machine. Adrian Freihofer (7): oeqa: replace deprecated assertEquals oeqa/selftest/recipetool: fix for python 3.12 oeqa/selftest/oelib/buildhistory: git default branch feature-microblaze-versions.inc: python 3.12 regex meta/lib/oeqa: python 3.12 regex meta/recipes: python 3.12 regex scripts: python 3.12 regex Chris Laplante (1): recipetool/create_buildsys_python: use importlib instead of imp Ross Burton (3): populate_sdk_ext: use ConfigParser instead of SafeConfigParser runqemu: add qmp socket support oeqa/selftest/recipetool: downgrade meson version to not use pyproject.toml Trevor Gamblin (1): scripts/runqemu: fix regex escape sequences meta/classes/populate_sdk_ext.bbclass | 2 +- .../feature-microblaze-versions.inc | 2 +- meta/lib/oeqa/oetest.py | 2 +- meta/lib/oeqa/sdk/buildtools-cases/sanity.py | 2 +- meta/lib/oeqa/selftest/cases/bblayers.py | 2 +- meta/lib/oeqa/selftest/cases/devtool.py | 2 +- meta/lib/oeqa/selftest/cases/fitimage.py | 6 +-- meta/lib/oeqa/selftest/cases/liboe.py | 2 +- .../oeqa/selftest/cases/oelib/buildhistory.py | 18 +++-- meta/lib/oeqa/selftest/cases/recipetool.py| 23 ++- .../perf/perf/sort-pmuevents.py | 8 ++-- meta/recipes-rt/rt-tests/files/rt_bmark.py| 2 +- scripts/combo-layer | 2 +- scripts/contrib/bbvars.py | 6 +-- scripts/contrib/convert-overrides.py | 8 ++-- scripts/lib/checklayer/__init__.py| 4 +- scripts/lib/recipetool/create.py | 12 +++--- scripts/lib/recipetool/create_buildsys.py | 38 +-- .../lib/recipetool/create_buildsys_python.py | 5 +-- scripts/oe-check-sstate | 2 +- scripts/oe-pkgdata-util | 2 +- scripts/opkg-query-helper.py | 2 +- scripts/runqemu | 19 -- 23 files changed, 97 insertions(+), 74 deletions(-) -- 2.43.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195711): https://lists.openembedded.org/g/openembedded-core/message/195711 Mute This Topic: https://lists.openembedded.org/mt/104382805/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 12/12] scripts: python 3.12 regex
From: Adrian Freihofer
All the regexes throw a warning like this:
WARNING: scripts/lib/recipetool/create_buildsys.py:140:
SyntaxWarning: invalid escape sequence '\s'
proj_re = re.compile('project\s*\(([^)]*)\)', re.IGNORECASE)
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
Signed-off-by: Adrian Freihofer
Signed-off-by: Richard Purdie
Backported from master: 24b0ba00d4f0b4d9834f7693ecb6032dfc534a80
Signed-off-by: Adrian Freihofer
---
scripts/combo-layer | 2 +-
scripts/contrib/bbvars.py | 6 ++--
scripts/contrib/convert-overrides.py | 8 ++---
scripts/lib/checklayer/__init__.py| 4 +--
scripts/lib/recipetool/create.py | 12 +++
scripts/lib/recipetool/create_buildsys.py | 38 +++
scripts/oe-check-sstate | 2 +-
scripts/oe-pkgdata-util | 2 +-
scripts/opkg-query-helper.py | 2 +-
9 files changed, 38 insertions(+), 38 deletions(-)
diff --git a/scripts/combo-layer b/scripts/combo-layer
index 7f2020fca7..19ad32660d 100755
--- a/scripts/combo-layer
+++ b/scripts/combo-layer
@@ -483,7 +483,7 @@ def check_repo_clean(repodir):
exit if repo is dirty
"""
output=runcmd("git status --porcelain", repodir)
-r = re.compile('\?\? patch-.*/')
+r = re.compile(r'\?\? patch-.*/')
dirtyout = [item for item in output.splitlines() if not r.match(item)]
if dirtyout:
logger.error("git repo %s is dirty, please fix it first", repodir)
diff --git a/scripts/contrib/bbvars.py b/scripts/contrib/bbvars.py
index 090133600b..a9cdf082ab 100755
--- a/scripts/contrib/bbvars.py
+++ b/scripts/contrib/bbvars.py
@@ -36,8 +36,8 @@ def bbvar_is_documented(var, documented_vars):
def collect_documented_vars(docfiles):
''' Walk the docfiles and collect the documented variables '''
documented_vars = []
-prog = re.compile(".*($|[^A-Z_])')
+prog = re.compile(r".*($|[^A-Z_])')
for d in docfiles:
with open(d) as f:
documented_vars += var_prog.findall(f.read())
@@ -45,7 +45,7 @@ def collect_documented_vars(docfiles):
return documented_vars
def bbvar_doctag(var, docconf):
-prog = re.compile('^%s\[doc\] *= *"(.*)"' % (var))
+prog = re.compile(r'^%s\[doc\] *= *"(.*)"' % (var))
if docconf == "":
return "?"
diff --git a/scripts/contrib/convert-overrides.py
b/scripts/contrib/convert-overrides.py
index 1939757f1b..c69acb4095 100755
--- a/scripts/contrib/convert-overrides.py
+++ b/scripts/contrib/convert-overrides.py
@@ -81,19 +81,19 @@ skip_ext = [".html", ".patch", ".m4", ".diff"] +
args.skip_ext
vars_re = {}
for exp in vars:
-vars_re[exp] = (re.compile('((^|[#\'"\s\-\+])[A-Za-z0-9_\-:${}\.]+)_' +
exp), r"\1:" + exp)
+vars_re[exp] = (re.compile(r'((^|[#\'"\s\-\+])[A-Za-z0-9_\-:${}\.]+)_' +
exp), r"\1:" + exp)
shortvars_re = {}
for exp in shortvars:
-shortvars_re[exp] = (re.compile('((^|[#\'"\s\-\+])[A-Za-z0-9_\-:${}\.]+)_'
+ exp + '([\(\'"\s:])'), r"\1:" + exp + r"\3")
+shortvars_re[exp] =
(re.compile(r'((^|[#\'"\s\-\+])[A-Za-z0-9_\-:${}\.]+)_' + exp +
r'([\(\'"\s:])'), r"\1:" + exp + r"\3")
package_re = {}
for exp in packagevars:
-package_re[exp] = (re.compile('(^|[#\'"\s\-\+]+)' + exp + '_' +
'([$a-z"\'\s%\[<{\\\*].)'), r"\1" + exp + r":\2")
+package_re[exp] = (re.compile(r'(^|[#\'"\s\-\+]+)' + exp + r'_' +
r'([$a-z"\'\s%\[<{\\\*].)'), r"\1" + exp + r":\2")
# Other substitutions to make
subs = {
-'r = re.compile("([^:]+):\s*(.*)")' : 'r = re.compile("(^.+?):\s+(.*)")',
+'r = re.compile(r"([^:]+):\s*(.*)")' : 'r = re.compile(r"(^.+?):\s+(.*)")',
"val = d.getVar('%s_%s' % (var, pkg))" : "val = d.getVar('%s:%s' % (var,
pkg))",
"f.write('%s_%s: %s\\n' % (var, pkg, encode(val)))" : "f.write('%s:%s:
%s\\n' % (var, pkg, encode(val)))",
"d.getVar('%s_%s' % (scriptlet_name, pkg))" : "d.getVar('%s:%s' %
(scriptlet_name, pkg))",
diff --git a/scripts/lib/checklayer/__init__.py
b/scripts/lib/checklayer/__init__.py
index 938805289e..53f99dce1e 100644
--- a/scripts/lib/checklayer/__init__.py
+++ b/scripts/lib/checklayer/__init__.py
@@ -324,8 +324,8 @@ def get_signatures(builddir, failsafe=False, machine=None,
extravars=None):
else:
raise
-sig_regex = re.compile("^(?P.*:.*):(?P.*) .$")
-tune_regex = re.compile("(^|\s)SIGGEN_LOCKEDSIGS_t-(?P\S*)\s*=\s*")
+sig_regex = re.compile(r"^(?P.*:.*):(?P.*) .$")
+tune_regex = re.compile(r"(^|\s)SIGGEN_LOCKEDSIGS_t-(?P\S*)\s*=\s*")
current_tune = None
with open(sigs_file, 'r') as f:
for line in f.readlines():
diff --git a/scripts/lib/recipetool/create.py b/scripts/lib/recipetool/create.py
index 67894fb4d0..7b4c501456 100644
---
[OE-core] [kirkstone][PATCH 11/12] meta/recipes: python 3.12 regex
From: Adrian Freihofer
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
Signed-off-by: Adrian Freihofer
Signed-off-by: Richard Purdie
Cherry-picked from master: f2d80817baea298b953d6e14daad65087b3b50c9
Signed-off-by: Adrian Freihofer
---
meta/recipes-kernel/perf/perf/sort-pmuevents.py | 8
meta/recipes-rt/rt-tests/files/rt_bmark.py | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-kernel/perf/perf/sort-pmuevents.py
b/meta/recipes-kernel/perf/perf/sort-pmuevents.py
index 0362f2d8fa..0a87e553ab 100755
--- a/meta/recipes-kernel/perf/perf/sort-pmuevents.py
+++ b/meta/recipes-kernel/perf/perf/sort-pmuevents.py
@@ -36,10 +36,10 @@ with open(infile, 'r') as file:
preamble_regex = re.compile( '^(.*?)^(struct|const struct|static struct|static
const struct)', re.MULTILINE | re.DOTALL )
preamble = re.search( preamble_regex, data )
-struct_block_regex = re.compile( '^(struct|const struct|static struct|static
const struct).*?(\w+) (.*?)\[\] = {(.*?)^};', re.MULTILINE | re.DOTALL )
-field_regex = re.compile( '{.*?},', re.MULTILINE | re.DOTALL )
-cpuid_regex = re.compile( '\.cpuid = (.*?),', re.MULTILINE | re.DOTALL )
-name_regex = re.compile( '\.name = (.*?),', re.MULTILINE | re.DOTALL )
+struct_block_regex = re.compile(r'^(struct|const struct|static struct|static
const struct).*?(\w+) (.*?)\[\] = {(.*?)^};', re.MULTILINE | re.DOTALL )
+field_regex = re.compile(r'{.*?},', re.MULTILINE | re.DOTALL )
+cpuid_regex = re.compile(r'\.cpuid = (.*?),', re.MULTILINE | re.DOTALL )
+name_regex = re.compile(r'\.name = (.*?),', re.MULTILINE | re.DOTALL )
# create a dictionary structure to store all the structs, their
# types and then their fields.
diff --git a/meta/recipes-rt/rt-tests/files/rt_bmark.py
b/meta/recipes-rt/rt-tests/files/rt_bmark.py
index 3b84447a0f..2a4eed412f 100755
--- a/meta/recipes-rt/rt-tests/files/rt_bmark.py
+++ b/meta/recipes-rt/rt-tests/files/rt_bmark.py
@@ -265,7 +265,7 @@ cmd = ("cyclictest",
"-d", str(interval_delta),
"-l", str(loop_count)
)
-rex = re.compile(b"C:\s*(\d+).*Min:\s*(\d+).*Avg:\s*(\d+).*Max:\s*(\d+)")
+rex = re.compile(r"C:\s*(\d+).*Min:\s*(\d+).*Avg:\s*(\d+).*Max:\s*(\d+)")
def run_cyclictest_once():
res = subprocess.check_output(cmd)
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195722):
https://lists.openembedded.org/g/openembedded-core/message/195722
Mute This Topic: https://lists.openembedded.org/mt/104382820/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 10/12] meta/lib/oeqa: python 3.12 regex
From: Adrian Freihofer
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
Signed-off-by: Adrian Freihofer
Signed-off-by: Richard Purdie
Cherry-picked from master: 9002850f0c2e409d3bc629e36bb360b96326bb64
Signed-off-by: Adrian Freihofer
---
meta/lib/oeqa/oetest.py | 2 +-
meta/lib/oeqa/selftest/cases/bblayers.py | 2 +-
meta/lib/oeqa/selftest/cases/fitimage.py | 6 +++---
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oeqa/oetest.py b/meta/lib/oeqa/oetest.py
index 9c84466dd0..b53c611062 100644
--- a/meta/lib/oeqa/oetest.py
+++ b/meta/lib/oeqa/oetest.py
@@ -256,7 +256,7 @@ class TestContext(object):
modules = []
for test in self.testslist:
-if re.search("\w+\.\w+\.test_\S+", test):
+if re.search(r"\w+\.\w+\.test_\S+", test):
test = '.'.join(t.split('.')[:3])
module = pkgutil.get_loader(test)
modules.append(module)
diff --git a/meta/lib/oeqa/selftest/cases/bblayers.py
b/meta/lib/oeqa/selftest/cases/bblayers.py
index 7d74833f61..0b9f16eeae 100644
--- a/meta/lib/oeqa/selftest/cases/bblayers.py
+++ b/meta/lib/oeqa/selftest/cases/bblayers.py
@@ -46,7 +46,7 @@ class BitbakeLayers(OESelftestTestCase):
bb_file = os.path.join(testoutdir, recipe_path, recipe_file)
self.assertTrue(os.path.isfile(bb_file), msg = "Cannot find
xcursor-transparent-theme_0.1.1.bb in the test_bitbakelayers_flatten local
dir.")
contents = ftools.read_file(bb_file)
-find_in_contents = re.search("# bbappended from meta-selftest
#\n(.*\n)*include test_recipe.inc", contents)
+find_in_contents = re.search(r"# bbappended from meta-selftest
#\n(.*\n)*include test_recipe.inc", contents)
self.assertTrue(find_in_contents, msg = "Flattening layers did not
work. bitbake-layers flatten output: %s" % result.output)
def test_bitbakelayers_add_remove(self):
diff --git a/meta/lib/oeqa/selftest/cases/fitimage.py
b/meta/lib/oeqa/selftest/cases/fitimage.py
index d732a9020d..4d820faf92 100644
--- a/meta/lib/oeqa/selftest/cases/fitimage.py
+++ b/meta/lib/oeqa/selftest/cases/fitimage.py
@@ -202,7 +202,7 @@ UBOOT_MKIMAGE_SIGN_ARGS = "-c 'a smart comment'"
signed_sections = {}
for line in result.output.splitlines():
if line.startswith((' Configuration', ' Image')):
-in_signed = re.search('\((.*)\)', line).groups()[0]
+in_signed = re.search(r'\((.*)\)', line).groups()[0]
elif re.match('^ *', line) in (' ', ''):
in_signed = None
elif in_signed:
@@ -521,7 +521,7 @@ UBOOT_FIT_HASH_ALG = "sha256"
signed_sections = {}
for line in result.output.splitlines():
if line.startswith((' Image')):
-in_signed = re.search('\((.*)\)', line).groups()[0]
+in_signed = re.search(r'\((.*)\)', line).groups()[0]
elif re.match(' \w', line):
in_signed = None
elif in_signed:
@@ -675,7 +675,7 @@ FIT_SIGN_INDIVIDUAL = "1"
signed_sections = {}
for line in result.output.splitlines():
if line.startswith((' Image')):
-in_signed = re.search('\((.*)\)', line).groups()[0]
+in_signed = re.search(r'\((.*)\)', line).groups()[0]
elif re.match(' \w', line):
in_signed = None
elif in_signed:
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195721):
https://lists.openembedded.org/g/openembedded-core/message/195721
Mute This Topic: https://lists.openembedded.org/mt/104382817/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 09/12] feature-microblaze-versions.inc: python 3.12 regex
From: Adrian Freihofer
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
Signed-off-by: Adrian Freihofer
feature-microblaze-versions.inc#
Signed-off-by: Richard Purdie
Cherry-picked from master: 662f52f1713c9f070550fc0c874eb62312218ea4
Signed-off-by: Adrian Freihofer
---
.../machine/include/microblaze/feature-microblaze-versions.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/conf/machine/include/microblaze/feature-microblaze-versions.inc
b/meta/conf/machine/include/microblaze/feature-microblaze-versions.inc
index 5c37f49abb..658e87b8cd 100644
--- a/meta/conf/machine/include/microblaze/feature-microblaze-versions.inc
+++ b/meta/conf/machine/include/microblaze/feature-microblaze-versions.inc
@@ -16,7 +16,7 @@ def microblaze_current_version(d, gcc = False):
# find the current version, and convert it to major/minor integers
version = None
for t in (d.getVar("TUNE_FEATURES") or "").split():
-m = re.search("^v(\d+)\.(\d+)", t)
+m = re.search(r"^v(\d+)\.(\d+)", t)
if m:
version = int(m.group(1)), int(m.group(2))
break
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195720):
https://lists.openembedded.org/g/openembedded-core/message/195720
Mute This Topic: https://lists.openembedded.org/mt/104382816/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 07/12] oeqa/selftest/recipetool: downgrade meson version to not use pyproject.toml
From: Ross Burton
recipetool's pyproject.toml parsing needs tomllib (python 3.11+) or
tomli (not a hard dependency), so is prone to failing depending on the
host configuration.
Downgrade the Meson release used for the checks to 0.52.1, which was the
last release before moving to pyproject.toml.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
Backported from master: 6dfe573d83687e5431841f062442b54b9fa22ff3
Signed-off-by: Adrian Freihofer
---
meta/lib/oeqa/selftest/cases/recipetool.py | 29 --
1 file changed, 16 insertions(+), 13 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/recipetool.py
b/meta/lib/oeqa/selftest/cases/recipetool.py
index db21325155..c888770533 100644
--- a/meta/lib/oeqa/selftest/cases/recipetool.py
+++ b/meta/lib/oeqa/selftest/cases/recipetool.py
@@ -440,17 +440,19 @@ class RecipetoolCreateTests(RecipetoolBase):
self._test_recipe_contents(recipefile, checkvars, inherits)
def test_recipetool_create_github(self):
-# Basic test to see if github URL mangling works
+# Basic test to see if github URL mangling works. Deliberately use an
+# older release of Meson at present so we don't need a toml parser.
temprecipe = os.path.join(self.tempdir, 'recipe')
os.makedirs(temprecipe)
-recipefile = os.path.join(temprecipe, 'meson_git.bb')
-srcuri = 'https://github.com/mesonbuild/meson;rev=1.3.1'
-result = runCmd(['recipetool', 'create', '-o', temprecipe, srcuri])
-self.assertTrue(os.path.isfile(recipefile))
+recipefile = os.path.join(temprecipe, 'python3-meson_git.bb')
+srcuri = 'https://github.com/mesonbuild/meson;rev=0.52.1'
+cmd = ['recipetool', 'create', '-o', temprecipe, srcuri]
+result = runCmd(cmd)
+self.assertTrue(os.path.isfile(recipefile), msg="recipe %s not created
for command %s, output %s" % (recipefile, " ".join(cmd), result.output))
checkvars = {}
-checkvars['LICENSE'] = set(['Apache-2.0', 'Proprietary', 'Unknown'])
-checkvars['SRC_URI'] =
'git://github.com/mesonbuild/meson;protocol=https;branch=1.3'
-inherits = ['python_setuptools_build_meta']
+checkvars['LICENSE'] = set(['Apache-2.0', "Unknown"])
+checkvars['SRC_URI'] =
'git://github.com/mesonbuild/meson;protocol=https;branch=0.52'
+inherits = ['setuptools3']
self._test_recipe_contents(recipefile, checkvars, inherits)
def test_recipetool_create_python3_setuptools(self):
@@ -473,18 +475,19 @@ class RecipetoolCreateTests(RecipetoolBase):
self._test_recipe_contents(recipefile, checkvars, inherits)
def test_recipetool_create_github_tarball(self):
-# Basic test to ensure github URL mangling doesn't apply to release
tarballs
+# Basic test to ensure github URL mangling doesn't apply to release
tarballs.
+# Deliberately use an older release of Meson at present so we don't
need a toml parser.
temprecipe = os.path.join(self.tempdir, 'recipe')
os.makedirs(temprecipe)
-pv = '1.3.1'
-recipefile = os.path.join(temprecipe, 'meson_%s.bb' % pv)
+pv = '0.52.1'
+recipefile = os.path.join(temprecipe, 'python3-meson_%s.bb' % pv)
srcuri =
'https://github.com/mesonbuild/meson/releases/download/%s/meson-%s.tar.gz' %
(pv, pv)
result = runCmd('recipetool create -o %s %s' % (temprecipe, srcuri))
self.assertTrue(os.path.isfile(recipefile))
checkvars = {}
-checkvars['LICENSE'] = set(['Apache-2.0', 'Proprietary', 'Unknown'])
+checkvars['LICENSE'] = set(['Apache-2.0'])
checkvars['SRC_URI'] =
'https://github.com/mesonbuild/meson/releases/download/${PV}/meson-${PV}.tar.gz'
-inherits = ['python_setuptools_build_meta']
+inherits = ['setuptools3']
self._test_recipe_contents(recipefile, checkvars, inherits)
def _test_recipetool_create_git(self, srcuri, branch=None):
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195718):
https://lists.openembedded.org/g/openembedded-core/message/195718
Mute This Topic: https://lists.openembedded.org/mt/104382814/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 08/12] oeqa/selftest/oelib/buildhistory: git default branch
From: Adrian Freihofer
On hosts with git defaulting to main branch the following exception
occures:
File .../buildhistory.py", line 99, in test_compare_dict_blobs_default
blob1 = self.repo.heads.master.commit.tree.blobs[0]
^^
File "/usr/lib/python3.12/site-packages/git/util.py", line 1114, in __getattr__
return list.__getattribute__(self, attr)
^
AttributeError: 'IterableList' object has no attribute 'master'
Support main and master branch for these test cases.
Note: setting the default branch with --initial-branch requires git
version 2.28 or later. Some of the still supported host distros do not
provide this feature yet.
Signed-off-by: Adrian Freihofer
Signed-off-by: Richard Purdie
Cherry-picked from master: 7df99843d8f31d8e0c2872ff625f4a5abf28f740
Signed-off-by: Adrian Freihofer
---
.../oeqa/selftest/cases/oelib/buildhistory.py | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py
b/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py
index 33bd6df2f3..ae12aa0865 100644
--- a/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py
+++ b/meta/lib/oeqa/selftest/cases/oelib/buildhistory.py
@@ -28,6 +28,16 @@ class TestBlobParsing(OESelftestTestCase):
import shutil
shutil.rmtree(self.repo_path)
+@property
+def heads_default(self):
+"""
+Support repos defaulting to master or to main branch
+"""
+try:
+return self.repo.heads.main
+except AttributeError:
+return self.repo.heads.master
+
def commit_vars(self, to_add={}, to_remove = [], msg="A commit message"):
if len(to_add) == 0 and len(to_remove) == 0:
return
@@ -65,10 +75,10 @@ class TestBlobParsing(OESelftestTestCase):
changesmap = { "foo-2" : ("2", "8"), "bar" : ("","4"), "bar-2" :
("","5")}
self.commit_vars(to_add = { "foo" : "1", "foo-2" : "2", "foo-3" : "3"
})
-blob1 = self.repo.heads.master.commit.tree.blobs[0]
+blob1 = self.heads_default.commit.tree.blobs[0]
self.commit_vars(to_add = { "foo-2" : "8", "bar" : "4", "bar-2" : "5"
})
-blob2 = self.repo.heads.master.commit.tree.blobs[0]
+blob2 = self.heads_default.commit.tree.blobs[0]
change_records = compare_dict_blobs(os.path.join(self.repo_path,
self.test_file),
blob1, blob2, False, False)
@@ -84,10 +94,10 @@ class TestBlobParsing(OESelftestTestCase):
defaultmap = { x : ("default", "1") for x in ["PKG", "PKGE", "PKGV",
"PKGR"]}
self.commit_vars(to_add = { "foo" : "1" })
-blob1 = self.repo.heads.master.commit.tree.blobs[0]
+blob1 = self.heads_default.commit.tree.blobs[0]
self.commit_vars(to_add = { "PKG" : "1", "PKGE" : "1", "PKGV" : "1",
"PKGR" : "1" })
-blob2 = self.repo.heads.master.commit.tree.blobs[0]
+blob2 = self.heads_default.commit.tree.blobs[0]
change_records = compare_dict_blobs(os.path.join(self.repo_path,
self.test_file),
blob1, blob2, False, False)
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195719):
https://lists.openembedded.org/g/openembedded-core/message/195719
Mute This Topic: https://lists.openembedded.org/mt/104382815/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 04/12] runqemu: add qmp socket support
From: Ross Burton
Add support for qmp sockets and defaults to unix:qmp.sock if unspecified
Signed-off-by: Ross Burton
Signed-off-by: Eilís 'pidge' Ní Fhlannagáin
Signed-off-by: Richard Purdie
Backported from master: 380631797f0d63124a8c21efa93ab672dbd79283
Qemu throws many warnings without qmp and many runtime tests fail
without this patch also on kirkstone.
Signed-off-by: Adrian Freihofer
---
scripts/runqemu | 11 +++
1 file changed, 11 insertions(+)
diff --git a/scripts/runqemu b/scripts/runqemu
index b7d7c7b4e7..b8c5adcbec 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -82,6 +82,7 @@ of the following environment variables (in any order):
kvm-vhost - enable KVM with vhost when running x86/x86_64 (VT-capable CPU
required)
publicvnc - enable a VNC server open to all hosts
audio - enable audio
+qmp= - create a QMP socket (defaults to unix:qmp.sock if unspecified)
[*/]ovmf* - OVMF firmware file or base name for booting with UEFI
tcpserial= - specify tcp serial port number
qemuparams= - specify custom parameters to QEMU
@@ -216,6 +217,7 @@ class BaseConfig(object):
self.cleaned = False
# Files to cleanup after run
self.cleanup_files = []
+self.qmp = None
def acquire_taplock(self, error=True):
logger.debug("Acquiring lockfile %s..." % self.taplock)
@@ -526,6 +528,10 @@ class BaseConfig(object):
elif arg == 'publicvnc':
self.publicvnc = True
self.qemu_opt_script += ' -vnc :0'
+elif arg == "qmp":
+self.qmp = "unix:qmp.sock"
+elif arg.startswith("qmp="):
+self.qmp = arg[len('qmp='):]
elif arg.startswith('tcpserial='):
self.tcpserial_portnum = '%s' % arg[len('tcpserial='):]
elif arg.startswith('qemuparams='):
@@ -1346,6 +1352,10 @@ class BaseConfig(object):
raise RunQemuError("Failed to boot, QB_SYSTEM_NAME is NULL!")
self.qemu_system = qemu_system
+def setup_qmp(self):
+if self.qmp:
+self.qemu_opt += " -qmp %s,server,nowait" % self.qmp
+
def setup_vga(self):
if self.nographic == True:
if self.sdl == True:
@@ -1476,6 +1486,7 @@ class BaseConfig(object):
if self.snapshot:
self.qemu_opt += " -snapshot"
+self.setup_qmp()
self.setup_serial()
self.setup_vga()
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195715):
https://lists.openembedded.org/g/openembedded-core/message/195715
Mute This Topic: https://lists.openembedded.org/mt/104382810/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 06/12] oeqa/selftest/recipetool: fix for python 3.12
From: Adrian Freihofer
test_recipetool_create_github and test_recipetool_create_github_tarball
fail because the old meson version used by these tests cases does not
run on Python 3.12. The issue is in the dependencies.py which comes with
meson:
ERROR: build/tmp/work/recipetool-3z4osyl7/source/git/mesonbuild/
dependencies.py:777: SyntaxWarning: invalid escape sequence '\.'
Use meson 1.3.1 (what is currently also used on master) as a reference
for these tests.
With this version of meson, recipetool creates recipes named
meson_git.bb or meson_1.3.1.bb. Since this looks more reasonable than
e.g. python3-meson_git.bb the test gets adapted.
Signed-off-by: Adrian Freihofer
Signed-off-by: Richard Purdie
Backported from master: 7374a8a2810a6cf027bfefefe87691a3529123ff
Signed-off-by: Adrian Freihofer
---
meta/lib/oeqa/selftest/cases/recipetool.py | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/recipetool.py
b/meta/lib/oeqa/selftest/cases/recipetool.py
index db8790b57b..db21325155 100644
--- a/meta/lib/oeqa/selftest/cases/recipetool.py
+++ b/meta/lib/oeqa/selftest/cases/recipetool.py
@@ -444,13 +444,13 @@ class RecipetoolCreateTests(RecipetoolBase):
temprecipe = os.path.join(self.tempdir, 'recipe')
os.makedirs(temprecipe)
recipefile = os.path.join(temprecipe, 'meson_git.bb')
-srcuri = 'https://github.com/mesonbuild/meson;rev=0.32.0'
+srcuri = 'https://github.com/mesonbuild/meson;rev=1.3.1'
result = runCmd(['recipetool', 'create', '-o', temprecipe, srcuri])
self.assertTrue(os.path.isfile(recipefile))
checkvars = {}
-checkvars['LICENSE'] = set(['Apache-2.0'])
-checkvars['SRC_URI'] =
'git://github.com/mesonbuild/meson;protocol=https;branch=master'
-inherits = ['setuptools3']
+checkvars['LICENSE'] = set(['Apache-2.0', 'Proprietary', 'Unknown'])
+checkvars['SRC_URI'] =
'git://github.com/mesonbuild/meson;protocol=https;branch=1.3'
+inherits = ['python_setuptools_build_meta']
self._test_recipe_contents(recipefile, checkvars, inherits)
def test_recipetool_create_python3_setuptools(self):
@@ -476,15 +476,15 @@ class RecipetoolCreateTests(RecipetoolBase):
# Basic test to ensure github URL mangling doesn't apply to release
tarballs
temprecipe = os.path.join(self.tempdir, 'recipe')
os.makedirs(temprecipe)
-pv = '0.32.0'
+pv = '1.3.1'
recipefile = os.path.join(temprecipe, 'meson_%s.bb' % pv)
srcuri =
'https://github.com/mesonbuild/meson/releases/download/%s/meson-%s.tar.gz' %
(pv, pv)
result = runCmd('recipetool create -o %s %s' % (temprecipe, srcuri))
self.assertTrue(os.path.isfile(recipefile))
checkvars = {}
-checkvars['LICENSE'] = set(['Apache-2.0'])
+checkvars['LICENSE'] = set(['Apache-2.0', 'Proprietary', 'Unknown'])
checkvars['SRC_URI'] =
'https://github.com/mesonbuild/meson/releases/download/${PV}/meson-${PV}.tar.gz'
-inherits = ['setuptools3']
+inherits = ['python_setuptools_build_meta']
self._test_recipe_contents(recipefile, checkvars, inherits)
def _test_recipetool_create_git(self, srcuri, branch=None):
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195717):
https://lists.openembedded.org/g/openembedded-core/message/195717
Mute This Topic: https://lists.openembedded.org/mt/104382812/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 05/12] oeqa: replace deprecated assertEquals
From: Adrian Freihofer
assertEquals is deprecated since Python 2.7:
https://docs.python.org/2/library/unittest.html#deprecated-aliases
It throws errors at least on Python 3.12. Replace it by assertEqual.
Signed-off-by: Adrian Freihofer
Signed-off-by: Richard Purdie
Backported from master: 68286d0b70cf09a0d2950b48945c9192fb8c8769
Signed-off-by: Adrian Freihofer
---
meta/lib/oeqa/sdk/buildtools-cases/sanity.py | 2 +-
meta/lib/oeqa/selftest/cases/devtool.py | 2 +-
meta/lib/oeqa/selftest/cases/liboe.py| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/lib/oeqa/sdk/buildtools-cases/sanity.py
b/meta/lib/oeqa/sdk/buildtools-cases/sanity.py
index 64baaa8f84..68b19f4d47 100644
--- a/meta/lib/oeqa/sdk/buildtools-cases/sanity.py
+++ b/meta/lib/oeqa/sdk/buildtools-cases/sanity.py
@@ -19,4 +19,4 @@ class SanityTests(OESDKTestCase):
# Canonicalise the location of this command
tool_path = os.path.realpath(self._run("command -v %s" %
command).strip())
# Assert that the tool was found inside the SDK root
-self.assertEquals(os.path.commonprefix((sdk_base, tool_path)),
sdk_base)
+self.assertEqual(os.path.commonprefix((sdk_base, tool_path)),
sdk_base)
diff --git a/meta/lib/oeqa/selftest/cases/devtool.py
b/meta/lib/oeqa/selftest/cases/devtool.py
index aea2ad6561..dc0fc35062 100644
--- a/meta/lib/oeqa/selftest/cases/devtool.py
+++ b/meta/lib/oeqa/selftest/cases/devtool.py
@@ -919,7 +919,7 @@ class DevtoolModifyTests(DevtoolBase):
runCmd('git -C %s checkout %s' % (tempdir, branch))
with open(source, "rt") as f:
content = f.read()
-self.assertEquals(content, expected)
+self.assertEqual(content, expected)
check('devtool', 'This is a test for something\n')
check('devtool-no-overrides', 'This is a test for something\n')
check('devtool-override-qemuarm', 'This is a test for qemuarm\n')
diff --git a/meta/lib/oeqa/selftest/cases/liboe.py
b/meta/lib/oeqa/selftest/cases/liboe.py
index afe8f8809f..da88ff480e 100644
--- a/meta/lib/oeqa/selftest/cases/liboe.py
+++ b/meta/lib/oeqa/selftest/cases/liboe.py
@@ -97,6 +97,6 @@ class LibOE(OESelftestTestCase):
dstcnt = len(os.listdir(dst))
srccnt = len(os.listdir(src))
-self.assertEquals(dstcnt, len(testfiles), "Number of files in dst (%s)
differs from number of files in src(%s)." % (dstcnt, srccnt))
+self.assertEqual(dstcnt, len(testfiles), "Number of files in dst (%s)
differs from number of files in src(%s)." % (dstcnt, srccnt))
oe.path.remove(testloc)
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195716):
https://lists.openembedded.org/g/openembedded-core/message/195716
Mute This Topic: https://lists.openembedded.org/mt/104382811/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 01/12] recipetool/create_buildsys_python: use importlib instead of imp
From: Chris Laplante
'imp' was deprecated in Python 3.4 and removed in 3.12. The
piece of importlib we use has been around since 3.3.
Signed-off-by: Chris Laplante
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
Cherry-picked from master: 457f0dad87b4e45a53865b5ad2c150215bd74019
Signed-off-by: Adrian Freihofer
---
scripts/lib/recipetool/create_buildsys_python.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/scripts/lib/recipetool/create_buildsys_python.py
b/scripts/lib/recipetool/create_buildsys_python.py
index 5686a62d3f..a7eed3256f 100644
--- a/scripts/lib/recipetool/create_buildsys_python.py
+++ b/scripts/lib/recipetool/create_buildsys_python.py
@@ -10,7 +10,7 @@ import codecs
import collections
import setuptools.command.build_py
import email
-import imp
+import importlib
import glob
import itertools
import logging
@@ -561,7 +561,6 @@ class PythonRecipeHandler(RecipeHandler):
return deps
def parse_pkgdata_for_python_packages(self):
-suffixes = [t[0] for t in imp.get_suffixes()]
pkgdata_dir = tinfoil.config_data.getVar('PKGDATA_DIR')
ldata = tinfoil.config_data.createCopy()
@@ -585,7 +584,7 @@ class PythonRecipeHandler(RecipeHandler):
continue
for fn in files_info:
-for suffix in suffixes:
+for suffix in importlib.machinery.all_suffixes():
if fn.endswith(suffix):
break
else:
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195712):
https://lists.openembedded.org/g/openembedded-core/message/195712
Mute This Topic: https://lists.openembedded.org/mt/104382806/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 03/12] populate_sdk_ext: use ConfigParser instead of SafeConfigParser
From: Ross Burton
SafeConfigParser was renamed to ConfigParser in 3.2, and the
SafeConfigParser alias will be removed in 3.12.
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
Cherry-picked from master: 71b3e7f71727137b4b996cc4160c9cc1581824b8
Signed-off-by: Adrian Freihofer
---
meta/classes/populate_sdk_ext.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/populate_sdk_ext.bbclass
b/meta/classes/populate_sdk_ext.bbclass
index ca1b7753cb..bdd86863c6 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -227,7 +227,7 @@ python copy_buildsystem () {
# Write out config file for devtool
import configparser
-config = configparser.SafeConfigParser()
+config = configparser.ConfigParser()
config.add_section('General')
config.set('General', 'bitbake_subdir', conf_bbpath)
config.set('General', 'init_path', conf_initpath)
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195714):
https://lists.openembedded.org/g/openembedded-core/message/195714
Mute This Topic: https://lists.openembedded.org/mt/104382808/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH 02/12] scripts/runqemu: fix regex escape sequences
From: Trevor Gamblin
When invoking runqemu with Python 3.12, the following warning is
encountered:
|SyntaxWarning: invalid escape sequence '\.'
This is because the interpreter scans the string before it is processed
by the regex module, and it interprets the backslash as part of an
escape sequence, but not a standard one. This will be registered as an
error rather than a warning in future Python versions. To avoid the it,
simply add an extra backslash so that Python doesn't misinterpret the
string, while the regex parser still sees an escaped '.' character.
Signed-off-by: Trevor Gamblin
Signed-off-by: Richard Purdie
Backported from master: 0e8a4142bb90a92d175df6b2537d24a372356f98
Signed-off-by: Adrian Freihofer
---
scripts/runqemu | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index 729b067a9f..b7d7c7b4e7 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -362,7 +362,7 @@ class BaseConfig(object):
if p.endswith('.qemuboot.conf'):
self.qemuboot = p
self.qbconfload = True
-elif re.search('\.bin$', p) or re.search('bzImage', p) or \
+elif re.search('\\.bin$', p) or re.search('bzImage', p) or \
re.search('zImage', p) or re.search('vmlinux', p) or \
re.search('fitImage', p) or re.search('uImage', p):
self.kernel = p
@@ -376,13 +376,13 @@ class BaseConfig(object):
fst = t
break
if not fst:
-m = re.search('.*\.(.*)$', self.rootfs)
+m = re.search('.*\\.(.*)$', self.rootfs)
if m:
fst = m.group(1)
if fst:
self.check_arg_fstype(fst)
-qb = re.sub('\.' + fst + "$", '', self.rootfs)
-qb = '%s%s' % (re.sub('\.rootfs$', '', qb), '.qemuboot.conf')
+qb = re.sub('\\.' + fst + "$", '', self.rootfs)
+qb = '%s%s' % (re.sub('\\.rootfs$', '', qb), '.qemuboot.conf')
if os.path.exists(qb):
self.qemuboot = qb
self.qbconfload = True
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195713):
https://lists.openembedded.org/g/openembedded-core/message/195713
Mute This Topic: https://lists.openembedded.org/mt/104382807/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] [AUH] python3-poetry-core: upgrading to 1.9.0 SUCCEEDED
On Thu, Feb 15, 2024 at 11:43 AM Tim Orling wrote:
> This version deprecates the very PEP-517 build backend we depend upon for
> the python_poetry_core bbclass.
> We do not want to take this so late in the release cycle, nor do we want
> to add all the dependencies required to build the full poetry.
>
> https://github.com/python-poetry/poetry-core/pull/692
>
> Nevermind. This was a nothing-burger. Build of python3-tomlkit was just
fine and so were its ptests (meta-python-image-ptest-python3-tomlkit).
> On Thu, Feb 15, 2024 at 9:33 AM Auto Upgrade Helper
> wrote:
>
>> Hello,
>>
>> this email is a notification from the Auto Upgrade Helper
>> that the automatic attempt to upgrade the recipe *python3-poetry-core* to
>> *1.9.0* has Succeeded.
>>
>> Next steps:
>> - apply the patch: git am
>> 0001-python3-poetry-core-upgrade-1.8.1-1.9.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
>>
>> -- >8 --
>> From 7441a91a0d58936eb42a90698ec8e8d80f4d72ad Mon Sep 17 00:00:00 2001
>> From: Upgrade Helper
>> Date: Thu, 15 Feb 2024 08:16:50 +
>> Subject: [PATCH] python3-poetry-core: upgrade 1.8.1 -> 1.9.0
>>
>> ---
>> ...ython3-poetry-core_1.8.1.bb => python3-poetry-core_1.9.0.bb} | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> rename meta/recipes-devtools/python/{python3-poetry-core_1.8.1.bb =>
>> python3-poetry-core_1.9.0.bb} (94%)
>>
>> diff --git a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
>> b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
>> similarity index 94%
>> rename from meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
>> rename to meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
>> index fcb6d30ee0..dfb29c4b86 100644
>> --- a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
>> +++ b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
>> @@ -15,7 +15,7 @@ LIC_FILES_CHKSUM = "\
>>
>>
>> file://src/poetry/core/_vendor/tomli/LICENSE;md5=f0879d17df0110d1aa8c8c9f46f5
>> \
>> "
>>
>> -SRC_URI[sha256sum] =
>> "67a76c671da2a70e55047cddda83566035b701f7e463b32a2abfeac6e2a16376"
>> +SRC_URI[sha256sum] =
>> "fa7a4001eae8aa572ee84f35feb510b321bd652e5cf9293249d62853e1f935a2"
>>
>> inherit python_poetry_core pypi
>> PYPI_ARCHIVE_NAME = "poetry_core-${PV}.${PYPI_PACKAGE_EXT}"
>> --
>> 2.42.0
>>
>>
>>
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195710):
https://lists.openembedded.org/g/openembedded-core/message/195710
Mute This Topic: https://lists.openembedded.org/mt/104377480/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] python3-poetry-core: upgrade 1.8.1 -> 1.9.0
This version deprecates "poetry.core.masonry.builder", but we detect
"poetry.core.masonry.api" in recipetool and nothing has broken our
build of wheels.
Thanks to Ross for noticing that the
"from poetry.core.masonry.builders.wheel import WheelBuilder"
is not a massive change in practice.
Changes:
1.9.0 - 2024-02-02
Added
* Add a to key in tool.poetry.packages to allow custom subpackage names (#672).
* Add support for path dependencies that do not define a build system (#675).
* Add a tool.poetry.package-mode key to support non-package mode (#661).
Changed
* Update list of supported licenses (#659, #669, #678, #694).
* Improve support for PEP 691 JSON-based Simple API (#664).
* Establish zipapp compatibility (#670).
* Rework list of files included in build artifacts (#666).
* Improve performance by treating collections in packages as immutable (#663).
* Deprecate poetry.core.masonry.builder (#682).
* Deprecate scripts that depend on extras (#690).
Fixed
* Fix an issue where insignificant errors were printed if the working
directory is not inside a git repository (#684).
* Fix an issue where the project's directory was not recognized as git
repository on Windows due to an encoding issue (#685).
Vendoring
* fastjsonschema==2.19.1
* lark==1.1.8
https://github.com/python-poetry/poetry-core/blob/main/CHANGELOG.md#190---2024-02-02
Signed-off-by: Tim Orling
---
Tested by running meta-python-image-ptest-python3-tomlkit. All tests pass.
Manual python3> import poetry.core; print(poetry.core.__version__) worked as
well.
...ython3-poetry-core_1.8.1.bb => python3-poetry-core_1.9.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-poetry-core_1.8.1.bb =>
python3-poetry-core_1.9.0.bb} (94%)
diff --git a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
similarity index 94%
rename from meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
rename to meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
index fcb6d30ee00..dfb29c4b863 100644
--- a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
+++ b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
@@ -15,7 +15,7 @@ LIC_FILES_CHKSUM = "\
file://src/poetry/core/_vendor/tomli/LICENSE;md5=f0879d17df0110d1aa8c8c9f46f5
\
"
-SRC_URI[sha256sum] =
"67a76c671da2a70e55047cddda83566035b701f7e463b32a2abfeac6e2a16376"
+SRC_URI[sha256sum] =
"fa7a4001eae8aa572ee84f35feb510b321bd652e5cf9293249d62853e1f935a2"
inherit python_poetry_core pypi
PYPI_ARCHIVE_NAME = "poetry_core-${PV}.${PYPI_PACKAGE_EXT}"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195709):
https://lists.openembedded.org/g/openembedded-core/message/195709
Mute This Topic: https://lists.openembedded.org/mt/104382743/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] devtool: modify: Correct appending of type=git-dependency to URIs
A missing space when using :append would lead to run-on URIs if there
was no whitespace at the end of the original SRC_URI.
Signed-off-by: Peter Kjellerstedt
---
scripts/lib/devtool/standard.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index 8fb4b934d4..0243e3bc75 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -966,7 +966,7 @@ def modify(args, config, basepath, workspace):
# Assume first entry is main source extracted in ${S} so skip it
src_uri = src_uri[1::]
-#Add "type=git-dependency" to all non local sources
+# Add "type=git-dependency" to all non local sources
for url in src_uri:
if not url.startswith('file://') and not 'type=' in url:
src_uri_remove.append(url)
@@ -974,7 +974,7 @@ def modify(args, config, basepath, workspace):
if src_uri_remove:
f.write('SRC_URI:remove = "%s"\n' % ' '.join(src_uri_remove))
-f.write('SRC_URI:append = "%s"\n\n' % ' '.join(src_uri_append))
+f.write('SRC_URI:append = " %s"\n\n' % '
'.join(src_uri_append))
f.write('FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"\n')
# Local files can be modified/tracked in separate subdir under
srctree
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195708):
https://lists.openembedded.org/g/openembedded-core/message/195708
Mute This Topic: https://lists.openembedded.org/mt/104382740/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] patchtest: Add further information for failed testcases
On Thu, 2024-02-15 at 21:39 +, Simone Weiß wrote: > From: Simone Weiß > > Add more information to log messages when a test case fails. > Still keep it short and mostly reference the documentation. Reasson is that > documentation should already contain the needed information, do not duplicate > it here, so we also do not need to update here should the doc/policy change. > > Signed-off-by: Simone Weiß This does get a little tricky since the responses from patchtest on our test infrastructure has a character limit for security reasons. I have wondered if we do need to change it to some kind of code response which can then be translated back into real text. The reason for the character limit is to stop abuse of the VMs that run the tests, you can't mine bitcoin and pass them out as the failure message for example. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195707): https://lists.openembedded.org/g/openembedded-core/message/195707 Mute This Topic: https://lists.openembedded.org/mt/104382125/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] patchtest: Add further information for failed testcases
From: Simone Weiß
Add more information to log messages when a test case fails.
Still keep it short and mostly reference the documentation. Reasson is that
documentation should already contain the needed information, do not duplicate
it here, so we also do not need to update here should the doc/policy change.
Signed-off-by: Simone Weiß
---
meta/lib/patchtest/tests/test_mbox.py | 23 ++-
meta/lib/patchtest/tests/test_metadata.py | 11 ++-
meta/lib/patchtest/tests/test_patch.py| 10 ++
3 files changed, 26 insertions(+), 18 deletions(-)
diff --git a/meta/lib/patchtest/tests/test_mbox.py
b/meta/lib/patchtest/tests/test_mbox.py
index 0b623b7d17..32e60bf0f5 100644
--- a/meta/lib/patchtest/tests/test_mbox.py
+++ b/meta/lib/patchtest/tests/test_mbox.py
@@ -55,6 +55,8 @@ class TestMbox(base.Base):
poky= Project(name='Poky', listemail='p...@yoctoproject.org',
gitrepo='http://git.yoctoproject.org/cgit/cgit.cgi/poky/', paths=paths['poky'])
oe = Project(name='oe',
listemail='openembedded-de...@lists.openembedded.org',
gitrepo='http://git.openembedded.org/meta-openembedded/', paths=paths['oe'])
+commit_guide =
'https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html#implement-and-commit-changes'
+contrib_guide =
'https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html#finding-a-suitable-mailing-list'
def test_signed_off_by_presence(self):
for commit in TestMbox.commits:
@@ -88,7 +90,7 @@ class TestMbox(base.Base):
continue
l = len(shortlog)
if l > self.maxlength:
-self.fail('Edit shortlog so that it is %d characters or less
(currently %d characters)' % (self.maxlength, l),
+self.fail('Edit shortlog (first line of commit message) so
that it is %d characters or less (currently %d characters)' % (self.maxlength,
l),
commit=commit)
def test_series_merge_on_head(self):
@@ -97,7 +99,7 @@ class TestMbox(base.Base):
self.skip("Skipping merge test since patch is not intended for
master branch. Target detected is %s" % PatchTestInput.repo.branch)
if not PatchTestInput.repo.ismerged:
commithash, author, date, shortlog = headlog()
-self.fail('Series does not apply on top of target branch %s' %
PatchTestInput.repo.branch,
+self.fail('Series does not apply on top of target branch %s.' %
PatchTestInput.repo.branch,
data=[('Targeted branch', '%s (currently at %s)' %
(PatchTestInput.repo.branch, commithash))])
def test_target_mailing_list(self):
@@ -111,7 +113,7 @@ class TestMbox(base.Base):
for commit in TestMbox.commits:
match = project_regex.search_string(commit.subject)
if match:
-self.fail('Series sent to the wrong mailing list or some
patches from the series correspond to different mailing lists',
+self.fail('Series sent to the wrong mailing list or some
patches from the series correspond to different mailing lists. See also the
contributor guide: %s' % contrib_guide,
commit=commit)
for patch in self.patchset:
@@ -119,7 +121,7 @@ class TestMbox(base.Base):
base_path = folders[0]
for project in [self.bitbake, self.doc, self.oe, self.poky]:
if base_path in project.paths:
-self.fail('Series sent to the wrong mailing list or some
patches from the series correspond to different mailing lists',
+self.fail('Series sent to the wrong mailing list or some
patches from the series correspond to different mailing lists. See also the
contributor guide: %s' % contrib_guide,
data=[('Suggested ML', '%s [%s]' %
(project.listemail, project.gitrepo)),
('Patch\'s path:', patch.path)])
@@ -127,7 +129,7 @@ class TestMbox(base.Base):
if base_path.startswith('scripts'):
for poky_file in self.poky_scripts:
if patch.path.startswith(poky_file):
-self.fail('Series sent to the wrong mailing list or
some patches from the series correspond to different mailing lists',
+self.fail('Series sent to the wrong mailing list or
some patches from the series correspond to different mailing lists. See also
the contributor guide: %s' % contrib_guide,
data=[('Suggested ML', '%s [%s]' %
(self.poky.listemail, self.poky.gitrepo)),('Patch\'s path:', patch.path)])
def test_mbox_format(self):
@@ -138,22 +140,25 @@ class TestMbox(base.Base):
def test_commit_message_presence(self):
for commit in TestMbox.commits:
if not commit.commit_message.strip():
-self.fail('Please include a commit message on your
[OE-core][PATCH] patchtest-send-results: use Message-ID directly
There's no need to use regex for extracting the Message-ID field from
the patch email and mangle it by removing the angle brackets in the
process. Pull it directly from the mbox so that Patchtest's replies have
even fewer differences when compared to other replies. Also add a TODO
so that it's clear this needs adjustment when full series support is
added.
Signed-off-by: Trevor Gamblin
---
scripts/patchtest-send-results | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/scripts/patchtest-send-results b/scripts/patchtest-send-results
index 8190fe86c32..8a3dadbd111 100755
--- a/scripts/patchtest-send-results
+++ b/scripts/patchtest-send-results
@@ -65,7 +65,9 @@ subject_line = f"Patchtest results for {mbox_subject}"
reply_address = mbox[0]['from']
# extract the message ID and use that as the in-reply-to address
-in_reply_to = re.findall("<(.*)>", mbox[0]['Message-ID'])[0]
+# TODO: This will need to change again when patchtest can handle a whole
+# series at once
+in_reply_to = mbox[0]['Message-ID']
# the address the results email is sent from
from_address = "patcht...@automation.yoctoproject.org"
--
2.43.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195705):
https://lists.openembedded.org/g/openembedded-core/message/195705
Mute This Topic: https://lists.openembedded.org/mt/104382040/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 v3] openssh: Add a work around for ICE on mips/mips64
Unfortunately the new openssh version has an ICE on mips. This looks similar to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
Given how long these have been open, workaround the issue by disabling the
compiler
hardening options on mips.
It is likely better to do this than have the open CVEs for everyone
as we can't upgrade.
An example:
| during RTL pass: zero_call_used_regs
| clientloop.c: In function 'client_loop':
| clientloop.c:1699:1: internal compiler error: in int_mode_for_mode, at
stor-layout.cc:407
| 1699 | }
| | ^
| 0x14d0acc internal_error(char const*, ...)
| ???:0
| 0x5cf765 fancy_abort(char const*, int, char const*)
| ???:0
| 0x826f1f emit_move_insn_1(rtx_def*, rtx_def*)
| ???:0
| 0x8270c5 emit_move_insn(rtx_def*, rtx_def*)
| ???:0
| 0xb7b994 default_zero_call_used_regs(HARD_REG_SET)
| ???:0
| Please submit a full bug report, with preprocessed source (by using
-freport-bug).
| Please include the complete backtrace with any bug report.
Signed-off-by: Richard Purdie
---
meta/recipes-connectivity/openssh/openssh_9.6p1.bb | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
index 6366cefdf96..1fd36a266fd 100644
--- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
@@ -81,6 +81,10 @@ EXTRA_OECONF = "'LOGIN_PROGRAM=${base_bindir}/login' \
# musl doesn't implement wtmp/utmp and logwtmp
EXTRA_OECONF:append:libc-musl = " --disable-wtmp --disable-lastlog"
+# Work around ICE on mips/mips64 starting in 9.6p1
+EXTRA_OECONF:append:mips = " --without-hardening"
+EXTRA_OECONF:append:mips64 = " --without-hardening"
+
# Since we do not depend on libbsd, we do not want configure to use it
# just because it finds libutil.h. But, specifying --disable-libutil
# causes compile errors, so...
--
2.40.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195704):
https://lists.openembedded.org/g/openembedded-core/message/195704
Mute This Topic: https://lists.openembedded.org/mt/104381904/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 v2] openssh: Add a work around for ICE on mips/mips64
Unfortunately the new openssh version has an ICE on mips. This looks similar to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
Given how long these have been open, workaround the issue by disabling the
compiler
hardening options on mips.
It is likely better to do this than have the open CVEs for everyone
as we can't upgrade.
An example:
| during RTL pass: zero_call_used_regs
| clientloop.c: In function 'client_loop':
| clientloop.c:1699:1: internal compiler error: in int_mode_for_mode, at
stor-layout.cc:407
| 1699 | }
| | ^
| 0x14d0acc internal_error(char const*, ...)
| ???:0
| 0x5cf765 fancy_abort(char const*, int, char const*)
| ???:0
| 0x826f1f emit_move_insn_1(rtx_def*, rtx_def*)
| ???:0
| 0x8270c5 emit_move_insn(rtx_def*, rtx_def*)
| ???:0
| 0xb7b994 default_zero_call_used_regs(HARD_REG_SET)
| ???:0
| Please submit a full bug report, with preprocessed source (by using
-freport-bug).
| Please include the complete backtrace with any bug report.
Signed-off-by: Richard Purdie
---
meta/recipes-connectivity/openssh/openssh_9.6p1.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
index 6366cefdf96..fcd96f707f8 100644
--- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
@@ -81,6 +81,9 @@ EXTRA_OECONF = "'LOGIN_PROGRAM=${base_bindir}/login' \
# musl doesn't implement wtmp/utmp and logwtmp
EXTRA_OECONF:append:libc-musl = " --disable-wtmp --disable-lastlog"
+# Work around ICE on mips starting in 9.6p1
+EXTRA_OECONF:append:mips = " --without-hardening"
+
# Since we do not depend on libbsd, we do not want configure to use it
# just because it finds libutil.h. But, specifying --disable-libutil
# causes compile errors, so...
--
2.40.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195703):
https://lists.openembedded.org/g/openembedded-core/message/195703
Mute This Topic: https://lists.openembedded.org/mt/104381855/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 3/3] vulkan-samples: Update to tip of trunk
On Wed, 2024-02-14 at 12:47 -0800, Khem Raj wrote: > This gets the needed fixes for llvm-18 based builds > spdlog musl patches has been merged in the updated version module > 32bit backport is also available in this version > > Signed-off-by: Khem Raj Breaks with multilib: https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/8446/steps/11/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/5699/steps/11/logs/stdio Breaks with musl: https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/8583/steps/11/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/8606 Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195702): https://lists.openembedded.org/g/openembedded-core/message/195702 Mute This Topic: https://lists.openembedded.org/mt/104361298/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] usrmerge: add the distro feature to nativesdk builds when added to target and enable symlink creation for both
Hi Alejandro, On Thu, 2024-02-15 at 12:10 -0700, Alejandro Enedino Hernandez Samaniego wrote: > On 2/6/24 03:27, Richard Purdie wrote: > > > > On Thu, 2024-02-01 at 02:56 +, Maanya Goenka wrote: > > > From: Maanya Goenka > > > > > > Add usrmerge to DISTRO_FEATURES_FILTER_NATIVESDK (and > > > DISTRO_FEATURES_FILTER_NATIVE for consistency), > > > since we have come across cases where the distro feature would be > > > required by both contexts. > > > As a supplement to this change, when creating the merged usr symlinks at > > > the do_populate_sdk stage, > > > these need to be created for both the target and native sysroots within > > > the SDK. > > > > > > Signed-off-by: Maanya Goenka > > > Signed-off-by : Alejandro Hernandez Samaniego > > > --- > > > meta/classes-recipe/image.bbclass | 2 ++ > > > meta/conf/bitbake.conf| 4 ++-- > > > 2 files changed, 4 insertions(+), 2 deletions(-) > > > > This doesn't quite follow. "target", "nativesdk" and "native" are all > > different separate filesystems and not connected. Yes, you can use > > usrmerge on some (or all?) of them but you don't have to have them > > match. > > > > Forcing them to match is likely just working around an underlying issue > > which needs to be fixed. > > > > What were the real failures? > > > Apologies for the late response. > > I do agree that target, native and nativesdk are all separate and that you > could use usrmerge on some > or all. I understand your point and I'm to blame for the suggestion to add > usrmerge to the NATIVE case > for consistency. > > The proposed patch is trying to fix an issue for a use case related to > systemd. > > Newer versions of systemd do not function properly without usrmerge because > upstream systemd is dropping > support for non-usrmerge cases, which is typically fine because usrmerge > works well for the TARGET. > > https://lists.freedesktop.org/archives/systemd-devel/2022-September/048352.html > > However, we are using some NATIVESDK systemd components that require usrmerge > to work as well hence why > we needed to add usrmerge to the NATIVESDK filter since systemd components > where expecting usr/foo locations > in the nativesdk filesystem. > > While I understand that using nativesdk systemd components may not be widely > common, I do believe its a > valid usecase. > > I'd like to clarify that I'm not aware of any native systemd usecase and that > my suggestion to add usrmerge > to the NATIVE filter was only for consistency, but not required (apologies > for that again). > > I've reproduced the autobuilder failures locally and I see that taking out > usrmerge from the NATIVE filter does > get rid of the errors, if you agree with my statement that nativesdk systemd > components are a valid usecase, > we can send a v2 that adds usrmerge to the NATIVESDK filter only to fix such > cases. > > If you prefer, we could also go one step above that and create a condition to > add usrmerge to the NATIVESDK filter > only if systemd is being used or something similar. I think there is a piece of this that is still missing. Changing usrmerge in nativesdk fundamentally alters the layout of the SDK. The layout of the SDK is meant to be independent of the target (think multilibs and so on as well). What that means is that the tools are meant to work with any target system and not need to "match" their layout. This effectively means that systemd's tools aren't working properly for environments which have cross layouts. The SDK layout is already drastically different from that of the target system in that everything is installed into a deep prefix path. How long will it be before systemd drops support for that too? I don't really buy into this "systemd should dictate the layout of everything" situation we're ending up in. It does mean any given SDK can only support systemd or not systemd but not both so it breaks multiconfig too. What is systemd's position on supporting cross environments? That is effectively the real question here and it sounds like they don't support that? We already have big issues with this in the "native" tooling side of things since that cross support doesn't exist and we had to do our own emulation. So whilst I understand your usecase, I do believe this is a sign of a much deeper problem unfortunately, namely that systemd doesn't support cross environments or usage. We could probably hack around it like this for now but I'm far from sure it won't just break again in the future in worse ways. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195701): https://lists.openembedded.org/g/openembedded-core/message/195701 Mute This Topic: https://lists.openembedded.org/mt/104089708/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Patchtest results for [OE-core][PATCH 1/2] patchtest: Fix grammar in log output
Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/1-2-patchtest-Fix-grammar-in-log-output.patch FAIL: test commit message presence: Please include a commit message on your patch explaining the change (test_mbox.TestMbox.test_commit_message_presence) PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence) PASS: test author valid (test_mbox.TestMbox.test_author_valid) PASS: test max line length (test_metadata.TestMetadata.test_max_line_length) PASS: test mbox format (test_mbox.TestMbox.test_mbox_format) PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade) PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format) PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length) SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint) SKIP: pretest src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.pretest_src_uri_left_files) SKIP: test CVE check ignore: No modified recipes, skipping test (test_metadata.TestMetadata.test_cve_check_ignore) SKIP: test CVE tag format: No new CVE patches introduced (test_patch.TestPatch.test_cve_tag_format) SKIP: test Signed-off-by presence: No new CVE patches introduced (test_patch.TestPatch.test_signed_off_by_presence) SKIP: test Upstream-Status presence: No new CVE patches introduced (test_patch.TestPatch.test_upstream_status_presence_format) SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format) SKIP: test lic files chksum modified not mentioned: No modified recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned) SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence) SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence) SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint) SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head) SKIP: test src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.test_src_uri_left_files) SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence) SKIP: test target mailing list: Series merged, no reason to check other mailing lists (test_mbox.TestMbox.test_target_mailing_list) --- Please address the issues identified and submit a new revision of the patch, or alternatively, reply to this email with an explanation of why the patch should be accepted. If you believe these results are due to an error in patchtest, please submit a bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category under 'Yocto Project Subprojects'). For more information on specific failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank you! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195700): https://lists.openembedded.org/g/openembedded-core/message/195700 Mute This Topic: https://lists.openembedded.org/mt/104381528/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 v2] xz: upgrade 5.4.5 -> 5.4.6
Project has made changes to the site structure: https://tukaani.org/
| The XZ projects were moved to their own website on xz.tukaani.org in
| January 2024. The old links will be kept working via redirections.
While old release tarballs are still being accesible on the site via
redirects, new releases are no longer hosted on the site and point
directly to github - update SRC_URI.
The website change was mentioned in the COPYING file, changing its hash.
Full Changelog:
https://github.com/tukaani-project/xz/releases/tag/v5.4.6
License-Update: new URL due to website restructure
Signed-off-by: Denys Dmytriyenko
---
v2 - add License-Update: tag
meta/recipes-extended/xz/{xz_5.4.5.bb => xz_5.4.6.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-extended/xz/{xz_5.4.5.bb => xz_5.4.6.bb} (91%)
diff --git a/meta/recipes-extended/xz/xz_5.4.5.bb
b/meta/recipes-extended/xz/xz_5.4.6.bb
similarity index 91%
rename from meta/recipes-extended/xz/xz_5.4.5.bb
rename to meta/recipes-extended/xz/xz_5.4.6.bb
index ad519e5689..6c13e7ebe5 100644
--- a/meta/recipes-extended/xz/xz_5.4.5.bb
+++ b/meta/recipes-extended/xz/xz_5.4.6.bb
@@ -17,17 +17,17 @@ LICENSE:${PN}-dbg = "GPL-2.0-or-later"
LICENSE:${PN}-locale = "GPL-2.0-or-later"
LICENSE:liblzma = "PD"
-LIC_FILES_CHKSUM = "file://COPYING;md5=c8ea84ebe7b93cce676b54355dc6b2c0 \
+LIC_FILES_CHKSUM = "file://COPYING;md5=d4378ea9d5d1fc9ab0ae10d7948827d9 \
file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
file://COPYING.GPLv3;md5=1ebbd3e34237af26da5dc08a4e440464 \
file://COPYING.LGPLv2.1;md5=4fbd65380cdd255951079008b364516c \
file://lib/getopt.c;endline=23;md5=2069b0ee710572c03bb3114e4532cd84 \
"
-SRC_URI = "https://tukaani.org/xz/xz-${PV}.tar.gz \
+SRC_URI =
"https://github.com/tukaani-project/xz/releases/download/v${PV}/xz-${PV}.tar.gz
\
file://run-ptest \
"
-SRC_URI[sha256sum] =
"135c90b934aee8fbc0d467de87a05cb70d627da36abe518c357a873709e5b7d6"
+SRC_URI[sha256sum] =
"aeba3e03bf8140ddedf62a0a367158340520f6b384f75ca6045ccc6c0d43fd5c"
UPSTREAM_CHECK_REGEX = "xz-(?P\d+(\.\d+)+)\.tar"
CACHED_CONFIGUREVARS += "gl_cv_posix_shell=/bin/sh"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195699):
https://lists.openembedded.org/g/openembedded-core/message/195699
Mute This Topic: https://lists.openembedded.org/mt/104381417/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] patchtest-send-results: add --debug option
Add a -d/--debug option to patchtest-send-results so that the contents
of the constructed raw email can be checked without actually sending
anything to the list or patch author.
Signed-off-by: Trevor Gamblin
---
scripts/patchtest-send-results | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/scripts/patchtest-send-results b/scripts/patchtest-send-results
index 9fd24c9b959..8190fe86c32 100755
--- a/scripts/patchtest-send-results
+++ b/scripts/patchtest-send-results
@@ -38,6 +38,7 @@ def has_a_failed_test(raw_results):
parser = argparse.ArgumentParser(description="Send patchtest results to a
submitter for a given patch")
parser.add_argument("-p", "--patch", dest="patch", required=True, help="The
patch file to summarize")
+parser.add_argument("-d", "--debug", dest="debug", required=False,
action='store_true', help="Print raw email headers and content, but don't
actually send it")
args = parser.parse_args()
if not os.path.exists(args.patch):
@@ -92,12 +93,16 @@ if has_a_failed_test(testresult):
'\nMIME-Version: 1.0" + \
"\nContent-type:
Multipart/Mixed;boundary="NextPart"\n\n--NextPart\nContent-Type:
text/plain\n\n' + \
reply_contents + '\n\n--NextPart'
-response = ses_client.send_raw_email(
-Source="patcht...@automation.yoctoproject.org",
-RawMessage={
-"Data": raw_data,
-},
-)
+
+if args.debug:
+print(f"RawMessage: \n\n{raw_data}")
+else:
+response = ses_client.send_raw_email(
+Source="patcht...@automation.yoctoproject.org",
+RawMessage={
+"Data": raw_data,
+},
+)
else:
print(f"No failures identified for {args.patch}.")
--
2.43.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195698):
https://lists.openembedded.org/g/openembedded-core/message/195698
Mute This Topic: https://lists.openembedded.org/mt/104381294/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] patchtest: Fix grammar in log output
Signed-off-by: Trevor Gamblin
---
scripts/patchtest | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/patchtest b/scripts/patchtest
index 8c9a73e1dba..d0dc6e8fac5 100755
--- a/scripts/patchtest
+++ b/scripts/patchtest
@@ -162,7 +162,7 @@ def run(patch, logfile=None):
print('--\n')
if premerge_result == 2 and postmerge_result == 2:
-logger.error('patchtest: Not any test cases found - did you specify
the correct suite directory?')
+logger.error('patchtest: No test cases found - did you specify the
correct suite directory?')
if premerge_result == 1 or postmerge_result == 1:
logger.error('patchtest: At least one patchtest caused a failure or an
error - please check')
else:
--
2.43.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195697):
https://lists.openembedded.org/g/openembedded-core/message/195697
Mute This Topic: https://lists.openembedded.org/mt/104381293/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] Patchtest results for [PATCH] xz: upgrade 5.4.5 -> 5.4.6
Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/xz-upgrade-5.4.5---5.4.6.patch FAIL: test lic files chksum modified not mentioned: LIC_FILES_CHKSUM changed without "License-Update:" tag and description in commit message (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned) PASS: pretest src uri left files (test_metadata.TestMetadata.pretest_src_uri_left_files) PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore) PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence) PASS: test author valid (test_mbox.TestMbox.test_author_valid) PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence) PASS: test max line length (test_metadata.TestMetadata.test_max_line_length) PASS: test mbox format (test_mbox.TestMbox.test_mbox_format) PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade) PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format) PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length) PASS: test src uri left files (test_metadata.TestMetadata.test_src_uri_left_files) SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint) SKIP: test CVE tag format: No new CVE patches introduced (test_patch.TestPatch.test_cve_tag_format) SKIP: test Signed-off-by presence: No new CVE patches introduced (test_patch.TestPatch.test_signed_off_by_presence) SKIP: test Upstream-Status presence: No new CVE patches introduced (test_patch.TestPatch.test_upstream_status_presence_format) SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format) SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence) SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence) SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint) SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head) SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence) SKIP: test target mailing list: Series merged, no reason to check other mailing lists (test_mbox.TestMbox.test_target_mailing_list) --- Please address the issues identified and submit a new revision of the patch, or alternatively, reply to this email with an explanation of why the patch should be accepted. If you believe these results are due to an error in patchtest, please submit a bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category under 'Yocto Project Subprojects'). For more information on specific failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank you! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195696): https://lists.openembedded.org/g/openembedded-core/message/195696 Mute This Topic: https://lists.openembedded.org/mt/104381231/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] xz: upgrade 5.4.5 -> 5.4.6
Project has made changes to the site structure: https://tukaani.org/
| The XZ projects were moved to their own website on xz.tukaani.org in
| January 2024. The old links will be kept working via redirections.
While old release tarballs are still being accesible on the site via
redirects, new releases are no longer hosted on the site and point
directly to github - update SRC_URI.
The website change was mentioned in the COPYING file, changing its hash.
Full Changelog:
https://github.com/tukaani-project/xz/releases/tag/v5.4.6
Signed-off-by: Denys Dmytriyenko
---
meta/recipes-extended/xz/{xz_5.4.5.bb => xz_5.4.6.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-extended/xz/{xz_5.4.5.bb => xz_5.4.6.bb} (91%)
diff --git a/meta/recipes-extended/xz/xz_5.4.5.bb
b/meta/recipes-extended/xz/xz_5.4.6.bb
similarity index 91%
rename from meta/recipes-extended/xz/xz_5.4.5.bb
rename to meta/recipes-extended/xz/xz_5.4.6.bb
index ad519e5689..6c13e7ebe5 100644
--- a/meta/recipes-extended/xz/xz_5.4.5.bb
+++ b/meta/recipes-extended/xz/xz_5.4.6.bb
@@ -17,17 +17,17 @@ LICENSE:${PN}-dbg = "GPL-2.0-or-later"
LICENSE:${PN}-locale = "GPL-2.0-or-later"
LICENSE:liblzma = "PD"
-LIC_FILES_CHKSUM = "file://COPYING;md5=c8ea84ebe7b93cce676b54355dc6b2c0 \
+LIC_FILES_CHKSUM = "file://COPYING;md5=d4378ea9d5d1fc9ab0ae10d7948827d9 \
file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
file://COPYING.GPLv3;md5=1ebbd3e34237af26da5dc08a4e440464 \
file://COPYING.LGPLv2.1;md5=4fbd65380cdd255951079008b364516c \
file://lib/getopt.c;endline=23;md5=2069b0ee710572c03bb3114e4532cd84 \
"
-SRC_URI = "https://tukaani.org/xz/xz-${PV}.tar.gz \
+SRC_URI =
"https://github.com/tukaani-project/xz/releases/download/v${PV}/xz-${PV}.tar.gz
\
file://run-ptest \
"
-SRC_URI[sha256sum] =
"135c90b934aee8fbc0d467de87a05cb70d627da36abe518c357a873709e5b7d6"
+SRC_URI[sha256sum] =
"aeba3e03bf8140ddedf62a0a367158340520f6b384f75ca6045ccc6c0d43fd5c"
UPSTREAM_CHECK_REGEX = "xz-(?P\d+(\.\d+)+)\.tar"
CACHED_CONFIGUREVARS += "gl_cv_posix_shell=/bin/sh"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195695):
https://lists.openembedded.org/g/openembedded-core/message/195695
Mute This Topic: https://lists.openembedded.org/mt/104381081/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] [AUH] python3-poetry-core: upgrading to 1.9.0 SUCCEEDED
This version deprecates the very PEP-517 build backend we depend upon for
the python_poetry_core bbclass.
We do not want to take this so late in the release cycle, nor do we want to
add all the dependencies required to build the full poetry.
https://github.com/python-poetry/poetry-core/pull/692
On Thu, Feb 15, 2024 at 9:33 AM Auto Upgrade Helper
wrote:
> Hello,
>
> this email is a notification from the Auto Upgrade Helper
> that the automatic attempt to upgrade the recipe *python3-poetry-core* to
> *1.9.0* has Succeeded.
>
> Next steps:
> - apply the patch: git am
> 0001-python3-poetry-core-upgrade-1.8.1-1.9.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
>
> -- >8 --
> From 7441a91a0d58936eb42a90698ec8e8d80f4d72ad Mon Sep 17 00:00:00 2001
> From: Upgrade Helper
> Date: Thu, 15 Feb 2024 08:16:50 +
> Subject: [PATCH] python3-poetry-core: upgrade 1.8.1 -> 1.9.0
>
> ---
> ...ython3-poetry-core_1.8.1.bb => python3-poetry-core_1.9.0.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-devtools/python/{python3-poetry-core_1.8.1.bb =>
> python3-poetry-core_1.9.0.bb} (94%)
>
> diff --git a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
> b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
> similarity index 94%
> rename from meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
> rename to meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
> index fcb6d30ee0..dfb29c4b86 100644
> --- a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
> +++ b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
> @@ -15,7 +15,7 @@ LIC_FILES_CHKSUM = "\
>
>
> file://src/poetry/core/_vendor/tomli/LICENSE;md5=f0879d17df0110d1aa8c8c9f46f5
> \
> "
>
> -SRC_URI[sha256sum] =
> "67a76c671da2a70e55047cddda83566035b701f7e463b32a2abfeac6e2a16376"
> +SRC_URI[sha256sum] =
> "fa7a4001eae8aa572ee84f35feb510b321bd652e5cf9293249d62853e1f935a2"
>
> inherit python_poetry_core pypi
> PYPI_ARCHIVE_NAME = "poetry_core-${PV}.${PYPI_PACKAGE_EXT}"
> --
> 2.42.0
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195694):
https://lists.openembedded.org/g/openembedded-core/message/195694
Mute This Topic: https://lists.openembedded.org/mt/104377480/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] usrmerge: add the distro feature to nativesdk builds when added to target and enable symlink creation for both
On 2/6/24 03:27, Richard Purdie wrote: On Thu, 2024-02-01 at 02:56 +, Maanya Goenka wrote: From: Maanya Goenka Add usrmerge to DISTRO_FEATURES_FILTER_NATIVESDK (and DISTRO_FEATURES_FILTER_NATIVE for consistency), since we have come across cases where the distro feature would be required by both contexts. As a supplement to this change, when creating the merged usr symlinks at the do_populate_sdk stage, these need to be created for both the target and native sysroots within the SDK. Signed-off-by: Maanya Goenka Signed-off-by : Alejandro Hernandez Samaniego --- meta/classes-recipe/image.bbclass | 2 ++ meta/conf/bitbake.conf| 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) This doesn't quite follow. "target", "nativesdk" and "native" are all different separate filesystems and not connected. Yes, you can use usrmerge on some (or all?) of them but you don't have to have them match. Forcing them to match is likely just working around an underlying issue which needs to be fixed. What were the real failures? Hello Richard, Apologies for the late response. I do agree that target, native and nativesdk are all separate and that you could use usrmerge on some or all. I understand your point and I'm to blame for the suggestion to add usrmerge to the NATIVE case for consistency. The proposed patch is trying to fix an issue for a use case related to systemd. Newer versions of systemd do not function properly without usrmerge because upstream systemd is dropping support for non-usrmerge cases, which is typically fine because usrmerge works well for the TARGET. https://lists.freedesktop.org/archives/systemd-devel/2022-September/048352.html However, we are using some NATIVESDK systemd components that require usrmerge to work as well hence why we needed to add usrmerge to the NATIVESDK filter since systemd components where expecting usr/foo locations in the nativesdk filesystem. While I understand that using nativesdk systemd components may not be widely common, I do believe its a valid usecase. I'd like to clarify that I'm not aware of any native systemd usecase and that my suggestion to add usrmerge to the NATIVE filter was only for consistency, but not required (apologies for that again). I've reproduced the autobuilder failures locally and I see that taking out usrmerge from the NATIVE filter does get rid of the errors, if you agree with my statement that nativesdk systemd components are a valid usecase, we can send a v2 that adds usrmerge to the NATIVESDK filter only to fix such cases. If you prefer, we could also go one step above that and create a condition to add usrmerge to the NATIVESDK filter only if systemd is being used or something similar. Cheers, Alejandro For example, this would stop native or nativesdk sstate being reused between differently configured builds when it could be. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195693): https://lists.openembedded.org/g/openembedded-core/message/195693 Mute This Topic: https://lists.openembedded.org/mt/104089708/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] zlib: upgrade 1.3 -> 1.3.1
Refresh local patch.
Changelog:
https://github.com/madler/zlib/releases/tag/v1.3.1
Signed-off-by: Denys Dmytriyenko
---
...configure-Pass-LDFLAGS-to-link-tests.patch | 22 +--
.../zlib/{zlib_1.3.bb => zlib_1.3.1.bb} | 2 +-
2 files changed, 11 insertions(+), 13 deletions(-)
rename meta/recipes-core/zlib/{zlib_1.3.bb => zlib_1.3.1.bb} (94%)
diff --git
a/meta/recipes-core/zlib/zlib/0001-configure-Pass-LDFLAGS-to-link-tests.patch
b/meta/recipes-core/zlib/zlib/0001-configure-Pass-LDFLAGS-to-link-tests.patch
index e6cc915ba5..07b2cd3879 100644
---
a/meta/recipes-core/zlib/zlib/0001-configure-Pass-LDFLAGS-to-link-tests.patch
+++
b/meta/recipes-core/zlib/zlib/0001-configure-Pass-LDFLAGS-to-link-tests.patch
@@ -1,7 +1,7 @@
Upstream-Status: Submitted [https://github.com/madler/zlib/pull/599]
Signed-off-by: Ross Burton
-From f15584918a7fbbe3cc794ad59100e5e8153ea9f6 Mon Sep 17 00:00:00 2001
+From ea77f1f003a4d18b23cca703f3c824942863a1b4 Mon Sep 17 00:00:00 2001
From: Khem Raj
Date: Tue, 8 Mar 2022 22:38:47 -0800
Subject: [PATCH] configure: Pass LDFLAGS to link tests
@@ -13,24 +13,25 @@ tests perform correctly. Without this some tests may fail
resulting in
wrong confgure result, ending in miscompiling the package
Signed-off-by: Khem Raj
+
---
configure | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/configure b/configure
-index 52ff4a0..d04ee59 100755
+index c55098a..a7c6d72 100755
--- a/configure
+++ b/configure
-@@ -427,7 +427,7 @@ if test $shared -eq 1; then
+@@ -443,7 +443,7 @@ if test $shared -eq 1; then
echo Checking for shared library support... | tee -a configure.log
# we must test in two steps (cc then ld), required at least on SunOS 4.x
- if try $CC -w -c $SFLAGS $test.c &&
+ if try $CC -c $SFLAGS $test.c &&
- try $LDSHARED $SFLAGS -o $test$shared_ext $test.o; then
+ try $LDSHARED $SFLAGS $LDFLAGS -o $test$shared_ext $test.o; then
echo Building shared library $SHAREDLIBV with $CC. | tee -a configure.log
elif test -z "$old_cc" -a -z "$old_cflags"; then
echo No shared library support. | tee -a configure.log
-@@ -503,7 +503,7 @@ int main(void) {
+@@ -505,7 +505,7 @@ int main(void) {
}
EOF
fi
@@ -39,7 +40,7 @@ index 52ff4a0..d04ee59 100755
sizet=`./$test`
echo "Checking for a pointer-size integer type..." $sizet"." | tee -a
configure.log
CFLAGS="${CFLAGS} -DNO_SIZE_T=${sizet}"
-@@ -537,7 +537,7 @@ int main(void) {
+@@ -539,7 +539,7 @@ int main(void) {
return 0;
}
EOF
@@ -48,7 +49,7 @@ index 52ff4a0..d04ee59 100755
echo "Checking for fseeko... Yes." | tee -a configure.log
else
CFLAGS="${CFLAGS} -DNO_FSEEKO"
-@@ -554,7 +554,7 @@ cat > $test.c < $test.c <
int main() { return strlen(strerror(errno)); }
EOF
@@ -57,7 +58,7 @@ index 52ff4a0..d04ee59 100755
echo "Checking for strerror... Yes." | tee -a configure.log
else
CFLAGS="${CFLAGS} -DNO_STRERROR"
-@@ -661,7 +661,7 @@ int main()
+@@ -663,7 +663,7 @@ int main()
return (mytest("Hello%d\n", 1));
}
EOF
@@ -66,7 +67,7 @@ index 52ff4a0..d04ee59 100755
echo "Checking for vsnprintf() in stdio.h... Yes." | tee -a configure.log
echo >> configure.log
-@@ -751,7 +751,7 @@ int main()
+@@ -753,7 +753,7 @@ int main()
}
EOF
@@ -75,6 +76,3 @@ index 52ff4a0..d04ee59 100755
echo "Checking for snprintf() in stdio.h... Yes." | tee -a configure.log
echo >> configure.log
---
-2.25.1
-
diff --git a/meta/recipes-core/zlib/zlib_1.3.bb
b/meta/recipes-core/zlib/zlib_1.3.1.bb
similarity index 94%
rename from meta/recipes-core/zlib/zlib_1.3.bb
rename to meta/recipes-core/zlib/zlib_1.3.1.bb
index ede75f90bd..e6a81ef789 100644
--- a/meta/recipes-core/zlib/zlib_1.3.bb
+++ b/meta/recipes-core/zlib/zlib_1.3.1.bb
@@ -13,7 +13,7 @@ SRC_URI = "https://zlib.net/${BP}.tar.gz \
"
UPSTREAM_CHECK_URI = "http://zlib.net/;
-SRC_URI[sha256sum] =
"ff0ba4c292013dbc27530b3a81e1f9a813cd39de01ca5e0f8bf355702efa593e"
+SRC_URI[sha256sum] =
"9a93b2b7dfdac77ceba5a558a580e74667dd6fede4585b91eefb60f03b72df23"
# When a new release is made the previous release is moved to fossils/, so add
this
# to PREMIRRORS so it is also searched automatically.
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195692):
https://lists.openembedded.org/g/openembedded-core/message/195692
Mute This Topic: https://lists.openembedded.org/mt/104379162/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] gcc: Oe-selftest failures analysis - x86-64
On Thu, Feb 15, 2024 at 2:29 AM Sadineni, Harish via lists.openembedded.org wrote: > > Hi all, > > > We are analysing the test failures reported by the autobilder at > https://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/qemux86-64-tc/testresults.json > The autobuilder result summary as follows: > === > qemux86-64 PTest Result Summary > === > --- > Recipe | Passed | Failed| Skipped | > --- > gcc | 124420 | 37| 23809 | > gcc-g++ | 196231 | 39| 17314 | > gcc-libatomic | 27 | 1 | 27 | > gcc-libgomp| 3407| 16| 1981 | > gcc-libitm | 24 | 1 | 24 > | > gcc-libstdc++-v3 | 9705| 32| 5464 | > > > > We started with 'gcc.dg' module failures(13 failues, listed below) reported > in > https://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/testresult-report.txt. > ptestresult.gcc.gcc.dg/analyzer/data-model-4.c (test for excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O0 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O1 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O2 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O2 -flto > -fno-use-linker-plugin -flto-partition=none (test for excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O3 -g (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -Os (test for > excess errors) torture tests could be due to limited memory ( RAM ). how much RAM is available to qemu ? perhaps try to raise it and see if that helps. > ptestresult.gcc.gcc.dg/pr56837.c scan-tree-dump-times optimized "memset > ..c, 68, 16384.;" 1 > ptestresult.gcc.gcc.dg/vect/vect-ifcvt-18.c scan-tree-dump vect > "vectorized 3 loops" > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-10.c (test for excess errors) > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-16f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-17f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-18f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > vect-simd-clone depends on avx runtime I think. so maybe thats the issue here. > > > Out of these, except 'gcc.gcc.dg/vect/vect-simd-clone-10.c' all others are > fialed in gcc upstream. > > > We've analyzed the failed case 'vect-simd-clone-10.c' and find the root > cause, it is the bug is in gcc test suite. > > GCC Bug raised - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113899 > > > We are working on other module failures (g++,libatomic...), keep you posted > here. > > > Thanks and Regards, > Harish sadineni > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195691): https://lists.openembedded.org/g/openembedded-core/message/195691 Mute This Topic: https://lists.openembedded.org/mt/104370247/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 v2] overlayfs-etc: add option to skip creation of mount dirs
Hi Baruch, That's a good question. Bruce, if we need a new kernel feature (squashfs), the only way would be first to contribute it to https://git.yoctoproject.org/yocto-kernel-cache/ ? Or there's another way to enable a specific kernel configuration in a selftest? Slava On 14.02.2024 07:54, Baruch Siach wrote: Makes sense. I added mkdirhier of OVERLAYFS_ETC_MOUNT_POINT for the case of OVERLAYFS_ETC_CREATE_MOUNT_DIRS == 0. Let me know if there is a better solution for read-only filesystems. The trouble with testing is that I could not find any existing feature in yocto-kernel-cache that enables either CONFIG_SQUASHFS or CONFIG_EROFS_FS. Is there another way to enable kernel features for the test? Thanks, baruch -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195690): https://lists.openembedded.org/g/openembedded-core/message/195690 Mute This Topic: https://lists.openembedded.org/mt/104317307/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] waf.bbclass: Print waf output on unparsable version
On AB runs of reproducible-meta-oe/Repro meta-oe/meta-oe,
"waf --version" does not seem to contain the version but an error
message with "RuntimeWarning: " [0].
Since the actual output is not saved anywhere, it is quite hard to
debug.
This patch detects the problematic case and send it to the log where it
will be seen and fixed. As a side-effect, this error will now only be a
warning.
Here is a partial backtrace for this (full back trace visible in [0]):
NOTE: recipe mpv-0.35.1-r0: task do_configure: Started
ERROR: mpv-0.35.1-r0 do_configure: Error executing a python function in
exec_func_python() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function:
*** 0002:waf_preconfigure(d)
File: '$TOP/meta/classes-recipe/waf.bbclass', lineno: 58, function:
waf_preconfigure
0056:result = subprocess.check_output([python, wafbin,
'--version'], cwd=subsrcdir, stderr=subprocess.STDOUT)
0057:version = result.decode('utf-8').split()[1]
*** 0058:if bb.utils.vercmp_string_op(version, "1.8.7", ">="):
[...]
File: '$TOP/bitbake/lib/bb/utils.py', lineno: 91, function: split_version
*** 0091:e = int(s.split(":")[0])
Exception: ValueError: invalid literal for int() with base 10:
'RuntimeWarning'
[0]:
https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/11/steps/32/logs/stdio
line 31883
Signed-off-by: Yoann Congal
---
meta/classes-recipe/waf.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/waf.bbclass b/meta/classes-recipe/waf.bbclass
index 5fa0cc4987..70bf3be8fd 100644
--- a/meta/classes-recipe/waf.bbclass
+++ b/meta/classes-recipe/waf.bbclass
@@ -55,7 +55,10 @@ python waf_preconfigure() {
try:
result = subprocess.check_output([python, wafbin, '--version'],
cwd=subsrcdir, stderr=subprocess.STDOUT)
version = result.decode('utf-8').split()[1]
-if bb.utils.vercmp_string_op(version, "1.8.7", ">="):
+if not bb.utils.is_semver(version):
+bb.warn("Unable to parse \"waf --version\" output. Assuming waf
version without bindir/libdir support.")
+bb.warn("waf·--version·output = \n%s" % result.decode('utf-8'))
+elif bb.utils.vercmp_string_op(version, "1.8.7", ">="):
d.setVar("WAF_EXTRA_CONF", "--bindir=${bindir} --libdir=${libdir}")
except subprocess.CalledProcessError as e:
bb.warn("Unable to execute waf --version, exit code %d. Assuming waf
version without bindir/libdir support." % e.returncode)
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195689):
https://lists.openembedded.org/g/openembedded-core/message/195689
Mute This Topic: https://lists.openembedded.org/mt/104377678/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] numactl: upgrading to 2.0.18 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *numactl* to *2.0.18* has Succeeded. Next steps: - apply the patch: git am 0001-numactl-upgrade-2.0.17-2.0.18.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 -- >8 -- >From f2de26b265797b2250859ce73e96849fd883cb18 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Thu, 15 Feb 2024 17:21:56 + Subject: [PATCH] numactl: upgrade 2.0.17 -> 2.0.18 --- .../numactl/numactl/0001-define-run-test-target.patch | 8 ++-- .../numactl/numactl/Fix-the-test-output-format.patch | 3 ++- meta/recipes-support/numactl/numactl_git.bb | 4 ++-- 3 files changed, 10 insertions(+), 5 deletions(-) diff --git a/meta/recipes-support/numactl/numactl/0001-define-run-test-target.patch b/meta/recipes-support/numactl/numactl/0001-define-run-test-target.patch index 185dcb3e2d..6da1db97d2 100644 --- a/meta/recipes-support/numactl/numactl/0001-define-run-test-target.patch +++ b/meta/recipes-support/numactl/numactl/0001-define-run-test-target.patch @@ -1,4 +1,7 @@ -rename test target as run-test +From cdee7a5b111af415c9b3d24e2a4b840ba2e89061 Mon Sep 17 00:00:00 2001 +From: Roy Li +Date: Mon, 19 Oct 2020 14:42:11 -0700 +Subject: [PATCH] rename test target as run-test Upstream-Status: Pending @@ -8,12 +11,13 @@ not suitable for cross-compile environment, so rename it as run-test. and define test target to compile the test files. Signed-off-by: Roy Li + --- Makefile.am | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am -index e84b21e..94a8bff 100644 +index da01d27..c738b93 100644 --- a/Makefile.am +++ b/Makefile.am @@ -126,7 +126,9 @@ regress2: $(check_PROGRAMS) diff --git a/meta/recipes-support/numactl/numactl/Fix-the-test-output-format.patch b/meta/recipes-support/numactl/numactl/Fix-the-test-output-format.patch index 00c4f9dfcb..e156ae95a3 100644 --- a/meta/recipes-support/numactl/numactl/Fix-the-test-output-format.patch +++ b/meta/recipes-support/numactl/numactl/Fix-the-test-output-format.patch @@ -1,4 +1,4 @@ -From 59fd750a84bbe5874dec936d2bee9ef11a1b6505 Mon Sep 17 00:00:00 2001 +From 7c75a1fe5b0559e8eb7dc677d853feaae1404ba5 Mon Sep 17 00:00:00 2001 From: Li xin Date: Tue, 21 Jul 2015 02:01:22 +0900 Subject: [PATCH] Fix the test output format @@ -8,6 +8,7 @@ Upstream-Status: Pending Signed-off-by: Roy Li Signed-off-by: Li Xin Signed-off-by: Xiangyu Chen + --- test/regress | 6 +++--- test/regress2 | 11 +-- diff --git a/meta/recipes-support/numactl/numactl_git.bb b/meta/recipes-support/numactl/numactl_git.bb index bc5b09fc82..bd16df91ec 100644 --- a/meta/recipes-support/numactl/numactl_git.bb +++ b/meta/recipes-support/numactl/numactl_git.bb @@ -10,8 +10,8 @@ inherit autotools-brokensep ptest LIC_FILES_CHKSUM = "file://README.md;beginline=19;endline=32;md5=9f34c3af4ed6f3f5df0da5f3c0835a43" -SRCREV = "c1165896572b74e971d817909bf652066ddf801a" -PV = "2.0.17" +SRCREV = "3871b1c42fc71bceadafd745d2eff5dddfc2d67e" +PV = "2.0.18" SRC_URI = "git://github.com/numactl/numactl;branch=master;protocol=https \ file://Fix-the-test-output-format.patch \ -- 2.42.0 0001-numactl-upgrade-2.0.17-2.0.18.patch Description: Binary data packages/core2-64-poky-linux/numactl: PV changed from "2.0.17" to "2.0.18" packages/core2-64-poky-linux/numactl: PKGV changed from 2.0.17 [default] to 2.0.18 [default] packages/core2-64-poky-linux/numactl/numactl-dbg: PV changed from "2.0.17" to "2.0.18" packages/core2-64-poky-linux/numactl/numactl-dbg: PKGV changed from 2.0.17 [default] to 2.0.18 [default] packages/core2-64-poky-linux/numactl/numactl-dbg: PKGSIZE changed from 737512 to 739840 (+0%) packages/core2-64-poky-linux/numactl/numactl-dev: PV changed from "2.0.17" to "2.0.18" packages/core2-64-poky-linux/numactl/numactl-dev: PKGV changed from 2.0.17 [default] to 2.0.18 [default] packages/core2-64-poky-linux/numactl/numactl-dev: PKGSIZE changed from 17244 to 17644 (+2%) packages/core2-64-poky-linux/numactl/numactl-doc: PV changed from "2.0.17" to "2.0.18" packages/core2-64-poky-linux/numactl/numactl-doc: PKGV changed from 2.0.17 [default] to 2.0.18 [default] packages/core2-64-poky-linux/numactl/numactl-doc: PKGSIZE
[OE-core] [AUH] gstreamer1.0-python: upgrading to 1.22.10 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-python* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-python-upgrade-1.22.9-1.22.10.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
-- >8 --
>From 49f1dc514872f76b1c966f0a7920276b5c6ecf1a Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 15:13:39 +
Subject: [PATCH] gstreamer1.0-python: upgrade 1.22.9 -> 1.22.10
---
...eamer1.0-python_1.22.9.bb => gstreamer1.0-python_1.22.10.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-python_1.22.9.bb =>
gstreamer1.0-python_1.22.10.bb} (91%)
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.22.9.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.22.10.bb
similarity index 91%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.22.9.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.22.10.bb
index e086fa6866..b829a0fc62 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.22.9.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.22.10.bb
@@ -8,7 +8,7 @@ LICENSE = "LGPL-2.1-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=c34deae4e395ca07e725ab0076a5f740"
SRC_URI =
"https://gstreamer.freedesktop.org/src/${PNREAL}/${PNREAL}-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"3f9d5c6ffefda268703744b592a6b3983aa6723273b1220ecbcb62c2a589"
+SRC_URI[sha256sum] =
"99e37ea9f7163099734f9b0fce361bc67a0e7a65ffba9bc497127506a3fdedb3"
DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base python3-pygobject"
RDEPENDS:${PN} += "gstreamer1.0 gstreamer1.0-plugins-base python3-pygobject"
--
2.42.0
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-dbg: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-dbg:
PKGSIZE changed from 151368 to 151384 (+0%)
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-dbg: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-dev: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-dev: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-doc: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-doc: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-locale: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-locale:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-src: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-src: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-staticdev:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python-staticdev:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python/gstreamer1.0-python: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-python: PV changed from "1.22.9" to
"1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-python: SRC_URI changed from
"https://gstreamer.freedesktop.org/src/gst-python/gst-python-1.22.9.tar.xz; to
"https://gstreamer.freedesktop.org/src/gst-python/gst-python-1.22.10.tar.xz;
packages/core2-64-poky-linux/gstreamer1.0-python: PKGV changed from 1.22.9
[default] to 1.22.10 [default]
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (0 cached, 914 parsed). 1858 targets, 46
skipped, 0 masked, 0 errors.
Removing 77 recipes
[OE-core] [AUH] libproxy: upgrading to 0.5.4 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libproxy* to *0.5.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libproxy-upgrade-0.5.3-0.5.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
-- >8 --
>From c57b0dfc167062c880bfdbf8708d0890f9a069e5 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 17:17:26 +
Subject: [PATCH] libproxy: upgrade 0.5.3 -> 0.5.4
---
.../libproxy/{libproxy_0.5.3.bb => libproxy_0.5.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/libproxy/{libproxy_0.5.3.bb => libproxy_0.5.4.bb}
(95%)
diff --git a/meta/recipes-support/libproxy/libproxy_0.5.3.bb
b/meta/recipes-support/libproxy/libproxy_0.5.4.bb
similarity index 95%
rename from meta/recipes-support/libproxy/libproxy_0.5.3.bb
rename to meta/recipes-support/libproxy/libproxy_0.5.4.bb
index db88af093e..b4f4c6d254 100644
--- a/meta/recipes-support/libproxy/libproxy_0.5.3.bb
+++ b/meta/recipes-support/libproxy/libproxy_0.5.4.bb
@@ -14,7 +14,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=4fbd65380cdd255951079008b364516c \
DEPENDS = "glib-2.0"
SRC_URI = "git://github.com/libproxy/libproxy;protocol=https;branch=main"
-SRCREV = "29d51a611f28af0bdbd51a5779cc8df264c8dcff"
+SRCREV = "dff9a603d823dcc740ec966cd27960daa6b891b1"
S = "${WORKDIR}/git"
inherit meson pkgconfig gobject-introspection vala gi-docgen
--
2.42.0
0001-libproxy-upgrade-0.5.3-0.5.4.patch
Description: Binary data
packages/core2-64-poky-linux/libproxy: PV changed from "0.5.3" to "0.5.4"
packages/core2-64-poky-linux/libproxy: PKGV changed from 0.5.3 [default] to
0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy-dbg: PV changed from "0.5.3" to
"0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy-dbg: FILELIST: removed
"/usr/lib/.debug/libproxy.so.1", added "/usr/lib/.debug/libproxy.so.0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy-dbg: PKGV changed from 0.5.3
[default] to 0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy-dbg: PKGSIZE changed from 138608
to 135592 (-2%)
packages/core2-64-poky-linux/libproxy/libproxy-dev: PV changed from "0.5.3" to
"0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy-dev: PKGV changed from 0.5.3
[default] to 0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy-doc: PV changed from "0.5.3" to
"0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy-doc: PKGV changed from 0.5.3
[default] to 0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy-locale: PV changed from "0.5.3"
to "0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy-locale: PKGV changed from 0.5.3
[default] to 0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy-src: PV changed from "0.5.3" to
"0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy-src: PKGV changed from 0.5.3
[default] to 0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy-src: PKGSIZE changed from 63507
to 62614 (-1%)
packages/core2-64-poky-linux/libproxy/libproxy-staticdev: PV changed from
"0.5.3" to "0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy-staticdev: PKGV changed from
0.5.3 [default] to 0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy: FILES: removed
"/usr/lib/libproxy/0.5.3/modules", added "/usr/lib/libproxy/0.5.4/modules"
packages/core2-64-poky-linux/libproxy/libproxy: PV changed from "0.5.3" to
"0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy: FILELIST: added
"/usr/lib/libproxy.so.0.5.4"
packages/core2-64-poky-linux/libproxy/libproxy: PKGV changed from 0.5.3
[default] to 0.5.4 [default]
packages/core2-64-poky-linux/libproxy/libproxy: PKGSIZE changed from 64072 to
64017 (-0%)
Changes to packages/core2-64-poky-linux/libproxy (sysroot):
/usr/lib/libproxy.so.1 changed type from file to symlink
/usr/lib/libproxy.so.1 changed permissions from rwxr-xr-x to rwxrwxrwx
/usr/lib/libproxy.so.1 changed symlink target from None to libproxy.so.0.5.4
/usr/lib/libproxy.so.0.5.4 was added
packages/core2-64-poky-linux/libproxy/libproxy: FILELIST: added
"/usr/lib/libproxy.so.0.5.4"
Changes to packages/core2-64-poky-linux/libproxy (sysroot):
/usr/lib/libproxy.so.1 changed type from file to symlink
/usr/lib/libproxy.so.1 changed permissions from
[OE-core] [AUH] libusb1: upgrading to 1.0.27 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libusb1* to *1.0.27* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libusb1-upgrade-1.0.26-1.0.27.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
-- >8 --
>From 95b00d25e1be62244b8dc97db0187821640a5a6e Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 17:19:13 +
Subject: [PATCH] libusb1: upgrade 1.0.26 -> 1.0.27
---
...k-with-latomic-only-if-no-atomic-bui.patch | 46 ---
.../{libusb1_1.0.26.bb => libusb1_1.0.27.bb} | 5 +-
2 files changed, 2 insertions(+), 49 deletions(-)
delete mode 100644
meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
rename meta/recipes-support/libusb/{libusb1_1.0.26.bb => libusb1_1.0.27.bb}
(87%)
diff --git
a/meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
b/meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
deleted file mode 100644
index 3c223e0822..00
---
a/meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
+++ /dev/null
@@ -1,46 +0,0 @@
-From 95e601ce116dd46ea7915c171976b85ea0905d58 Mon Sep 17 00:00:00 2001
-From: Lonnie Abelbeck
-Date: Sun, 8 May 2022 14:05:56 -0500
-Subject: [PATCH] configure.ac: Link with -latomic only if no atomic builtins
-
-Follow-up to 561dbda, a check of GCC atomic builtins needs to be done
-first.
-
-I'm no autoconf guru, but using this:
-https://github.com/mesa3d/mesa/blob/0df485c285b73c34ba9062f0c27e55c3c702930d/configure.ac#L469
-as inspiration, I created a pre-check before calling AC_SEARCH_LIBS(...)
-
-Fixes #1135
-Closes #1139
-Upstream-Status: Backport
[https://github.com/kraj/libusb/commit/95e601ce116dd46ea7915c171976b85ea0905d58]
-Signed-off-by: Khem Raj
- configure.ac | 16 +++-
- libusb/version_nano.h | 2 +-
- 2 files changed, 16 insertions(+), 2 deletions(-)
-
a/configure.ac
-+++ b/configure.ac
-@@ -153,7 +153,21 @@ if test "x$platform" = xposix; then
- AC_SEARCH_LIBS([pthread_create], [pthread],
- [test "x$ac_cv_search_pthread_create" != "xnone required" &&
AC_SUBST(THREAD_LIBS, [-lpthread])],
- [], [])
-- AC_SEARCH_LIBS([__atomic_fetch_add_4], [atomic])
-+ dnl Check for new-style atomic builtins. We first check without linking
to -latomic.
-+ AC_MSG_CHECKING(whether __atomic_load_n is supported)
-+ AC_LINK_IFELSE([AC_LANG_SOURCE([[
-+ #include
-+ int main() {
-+ struct {
-+ uint64_t *v;
-+ } x;
-+ return (int)__atomic_load_n(x.v, __ATOMIC_ACQUIRE) &
-+ (int)__atomic_add_fetch(x.v, (uint64_t)1,
__ATOMIC_ACQ_REL);
-+ }]])], GCC_ATOMIC_BUILTINS_SUPPORTED=yes,
GCC_ATOMIC_BUILTINS_SUPPORTED=no)
-+ AC_MSG_RESULT($GCC_ATOMIC_BUILTINS_SUPPORTED)
-+ if test "x$GCC_ATOMIC_BUILTINS_SUPPORTED" != xyes; then
-+ AC_SEARCH_LIBS([__atomic_fetch_add_4], [atomic])
-+ fi
- elif test "x$platform" = xwindows; then
- AC_DEFINE([PLATFORM_WINDOWS], [1], [Define to 1 if compiling for a
Windows platform.])
- else
diff --git a/meta/recipes-support/libusb/libusb1_1.0.26.bb
b/meta/recipes-support/libusb/libusb1_1.0.27.bb
similarity index 87%
rename from meta/recipes-support/libusb/libusb1_1.0.26.bb
rename to meta/recipes-support/libusb/libusb1_1.0.27.bb
index 2af6fcdea7..f4af2bb977 100644
--- a/meta/recipes-support/libusb/libusb1_1.0.26.bb
+++ b/meta/recipes-support/libusb/libusb1_1.0.27.bb
@@ -11,14 +11,13 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=fbc093901857fcd118f065f900982c24"
BBCLASSEXTEND = "native nativesdk"
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/libusb-${PV}.tar.bz2 \
-
file://0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch \
file://run-ptest \
- "
+ "
GITHUB_BASE_URI = "https://github.com/libusb/libusb/releases;
UPSTREAM_CHECK_REGEX = "releases/tag/v?(?P\d+(\.\d+)+)$"
-SRC_URI[sha256sum] =
[OE-core] [AUH] libgit2: upgrading to 1.7.2 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libgit2* to *1.7.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libgit2-upgrade-1.7.1-1.7.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
-- >8 --
>From a4e09492eaa1e0f49269b6f9c4a878ca9a8d6416 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 16:57:20 +
Subject: [PATCH] libgit2: upgrade 1.7.1 -> 1.7.2
---
.../libgit2/{libgit2_1.7.1.bb => libgit2_1.7.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/libgit2/{libgit2_1.7.1.bb => libgit2_1.7.2.bb}
(92%)
diff --git a/meta/recipes-support/libgit2/libgit2_1.7.1.bb
b/meta/recipes-support/libgit2/libgit2_1.7.2.bb
similarity index 92%
rename from meta/recipes-support/libgit2/libgit2_1.7.1.bb
rename to meta/recipes-support/libgit2/libgit2_1.7.2.bb
index 92af0b8454..d1629c0c0b 100644
--- a/meta/recipes-support/libgit2/libgit2_1.7.1.bb
+++ b/meta/recipes-support/libgit2/libgit2_1.7.2.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=5bdf47bbc9a39dc6ce076d59e322dc17"
DEPENDS = "curl openssl zlib libssh2 libgcrypt libpcre2"
SRC_URI =
"git://github.com/libgit2/libgit2.git;branch=maint/v1.7;protocol=https"
-SRCREV = "a2bde63741977ca0f4ef7db2f609df320be67a08"
+SRCREV = "a418d9d4ab87bae16b87d8f37143a4687ae0e4b2"
S = "${WORKDIR}/git"
--
2.42.0
0001-libgit2-upgrade-1.7.1-1.7.2.patch
Description: Binary data
packages/core2-64-poky-linux/libgit2: PV changed from "1.7.1" to "1.7.2"
packages/core2-64-poky-linux/libgit2: PKGV changed from 1.7.1 [default] to
1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2-dbg: PV changed from "1.7.1" to
"1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2-dbg: PKGSIZE changed from 9876904
to 9876304 (-0%)
packages/core2-64-poky-linux/libgit2/libgit2-dbg: PKGV changed from 1.7.1
[default] to 1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2-dbg: FILELIST: removed
"/usr/lib/.debug/libgit2.so.1.7.1", added "/usr/lib/.debug/libgit2.so.1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2-dev: PV changed from "1.7.1" to
"1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2-dev: PKGV changed from 1.7.1
[default] to 1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2-doc: PV changed from "1.7.1" to
"1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2-doc: PKGV changed from 1.7.1
[default] to 1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2-locale: PV changed from "1.7.1" to
"1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2-locale: PKGV changed from 1.7.1
[default] to 1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2-src: PV changed from "1.7.1" to
"1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2-src: PKGSIZE changed from 4172330
to 4172460 (+0%)
packages/core2-64-poky-linux/libgit2/libgit2-src: PKGV changed from 1.7.1
[default] to 1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2-staticdev: PV changed from "1.7.1"
to "1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2-staticdev: PKGV changed from 1.7.1
[default] to 1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2: PV changed from "1.7.1" to "1.7.2"
packages/core2-64-poky-linux/libgit2/libgit2: PKGV changed from 1.7.1 [default]
to 1.7.2 [default]
packages/core2-64-poky-linux/libgit2/libgit2: FILELIST: removed
"/usr/lib/libgit2.so.1.7.1", added "/usr/lib/libgit2.so.1.7.2"
Changes to packages/core2-64-poky-linux/libgit2 (sysroot):
/usr/lib/libgit2.so.1.7 changed symlink target from libgit2.so.1.7.1 to
libgit2.so.1.7.2
/usr/lib/libgit2.so.1.7.1 moved to /usr/lib/libgit2.so.1.7.2
packages/core2-64-poky-linux/libgit2/libgit2: FILELIST: removed
"/usr/lib/libgit2.so.1.7.1", added "/usr/lib/libgit2.so.1.7.2"
Changes to packages/core2-64-poky-linux/libgit2 (sysroot):
/usr/lib/libgit2.so.1.7 changed symlink target from libgit2.so.1.7.1 to
libgit2.so.1.7.2
/usr/lib/libgit2.so.1.7.1 moved to /usr/lib/libgit2.so.1.7.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195688):
https://lists.openembedded.org/g/openembedded-core/message/195688
Mute This Topic: https://lists.openembedded.org/mt/104377583/21656
Group Owner:
[OE-core] [AUH] gst-devtools: upgrading to 1.22.10 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gst-devtools* to *1.22.10*
has Succeeded.
Next steps:
- apply the patch: git am 0001-gst-devtools-upgrade-1.22.9-1.22.10.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
-- >8 --
>From b8cf5d5489fe7dc4bd2452266fc4d91d2c2e8c3a Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:41:34 +
Subject: [PATCH] gst-devtools: upgrade 1.22.9 -> 1.22.10
---
.../0001-connect-has-a-different-signature-on-musl.patch | 3 ++-
.../{gst-devtools_1.22.9.bb => gst-devtools_1.22.10.bb}| 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
rename meta/recipes-multimedia/gstreamer/{gst-devtools_1.22.9.bb =>
gst-devtools_1.22.10.bb} (95%)
diff --git
a/meta/recipes-multimedia/gstreamer/gst-devtools/0001-connect-has-a-different-signature-on-musl.patch
b/meta/recipes-multimedia/gstreamer/gst-devtools/0001-connect-has-a-different-signature-on-musl.patch
index c0e4581358..21e30d6d46 100644
---
a/meta/recipes-multimedia/gstreamer/gst-devtools/0001-connect-has-a-different-signature-on-musl.patch
+++
b/meta/recipes-multimedia/gstreamer/gst-devtools/0001-connect-has-a-different-signature-on-musl.patch
@@ -1,4 +1,4 @@
-From 73b1002eda17451db1f58431b42c25203f1d3097 Mon Sep 17 00:00:00 2001
+From 0c73b8131efba63c5cd37ea8c7551434c3b57304 Mon Sep 17 00:00:00 2001
From: Khem Raj
Date: Sun, 9 Sep 2018 17:38:10 -0700
Subject: [PATCH] connect has a different signature on musl
@@ -11,6 +11,7 @@ typcasted to struct sockaddr_in* type inside the function
before use
Upstream-Status: Pending
Signed-off-by: Khem Raj
+
---
validate/plugins/fault_injection/socket_interposer.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.9.bb
b/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.10.bb
similarity index 95%
rename from meta/recipes-multimedia/gstreamer/gst-devtools_1.22.9.bb
rename to meta/recipes-multimedia/gstreamer/gst-devtools_1.22.10.bb
index f60234b528..363d12612f 100644
--- a/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.9.bb
+++ b/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.10.bb
@@ -12,7 +12,7 @@ SRC_URI =
"https://gstreamer.freedesktop.org/src/gst-devtools/gst-devtools-${PV}
file://0001-connect-has-a-different-signature-on-musl.patch \
"
-SRC_URI[sha256sum] =
"02e29400b44e9cc603aa6444dee5726b57edabef6455e6d0921ffed6f13840ee"
+SRC_URI[sha256sum] =
"0e1ec0d0b8f2d3d314a397399cd01dfc50c02ac088176996f934758119075ea9"
DEPENDS = "json-glib glib-2.0 glib-2.0-native gstreamer1.0
gstreamer1.0-plugins-base"
RRECOMMENDS:${PN} = "git"
--
2.42.0
packages/core2-64-poky-linux/gst-devtools/gst-devtools-dbg: FILELIST: removed
"/usr/lib/.debug/libgstvalidate-default-overrides-1.0.so.0.2209.0
/usr/lib/.debug/libgstvalidate-1.0.so.0.2209.0", added
"/usr/lib/.debug/libgstvalidate-1.0.so.0.2210.0
/usr/lib/.debug/libgstvalidate-default-overrides-1.0.so.0.2210.0"
packages/core2-64-poky-linux/gst-devtools/gst-devtools-dbg: PV changed from
"1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gst-devtools/gst-devtools-dbg: PKGSIZE changed
from 2561160 to 2561240 (+0%)
packages/core2-64-poky-linux/gst-devtools/gst-devtools-dbg: PKGV changed from
1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gst-devtools/gst-devtools-dev: PV changed from
"1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gst-devtools/gst-devtools-dev: PKGSIZE changed
from 395497 to 395498 (+0%)
packages/core2-64-poky-linux/gst-devtools/gst-devtools-dev: PKGV changed from
1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gst-devtools/gst-devtools-doc: PV changed from
"1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gst-devtools/gst-devtools-doc: PKGV changed from
1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gst-devtools/gst-devtools-locale: PV changed from
"1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gst-devtools/gst-devtools-locale: PKGV changed
from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gst-devtools/gst-devtools-src: PV changed from
"1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gst-devtools/gst-devtools-src: PKGV
[OE-core] [AUH] gstreamer1.0-rtsp-server: upgrading to 1.22.10 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-rtsp-server* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-rtsp-server-upgrade-1.22.9-1.22.10.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
-- >8 --
>From 362cfda2035809c165286405656f1d28a2bdb31c Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 15:16:47 +
Subject: [PATCH] gstreamer1.0-rtsp-server: upgrade 1.22.9 -> 1.22.10
---
...tsp-server_1.22.9.bb => gstreamer1.0-rtsp-server_1.22.10.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-rtsp-server_1.22.9.bb
=> gstreamer1.0-rtsp-server_1.22.10.bb} (90%)
diff --git
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server_1.22.9.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server_1.22.10.bb
similarity index 90%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server_1.22.9.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server_1.22.10.bb
index e232263a46..0e910e3dc4 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server_1.22.9.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server_1.22.10.bb
@@ -10,7 +10,7 @@ PNREAL = "gst-rtsp-server"
SRC_URI =
"https://gstreamer.freedesktop.org/src/${PNREAL}/${PNREAL}-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"808af148f89404ff74850f8ca5272bed4bfe67f9620231dc4514fd07eb26d0a4"
+SRC_URI[sha256sum] =
"60eb4f80b5a7ca929c21a61d50be9813a3413787959a5875de56a8ad5ca25f35"
S = "${WORKDIR}/${PNREAL}-${PV}"
--
2.42.0
0001-gstreamer1.0-rtsp-server-upgrade-1.22.9-1.22.10.patch
Description: Binary data
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-apps:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-apps:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-dbg:
PKGSIZE changed from 1563144 to 1563152 (+0%)
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-dbg:
FILELIST: removed "/usr/lib/.debug/libgstrtspserver-1.0.so.0.2209.0", added
"/usr/lib/.debug/libgstrtspserver-1.0.so.0.2210.0"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-dbg:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-dbg:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-dev:
PKGSIZE changed from 979411 to 979412 (+0%)
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-dev:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-dev:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-doc:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-doc:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-glib:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-glib:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-locale:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-locale:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-meta:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-meta:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-rtsp-server/gstreamer1.0-rtsp-server-rtspclientsink:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
[OE-core] [AUH] libpng: upgrading to 1.6.42 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libpng* to *1.6.42* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libpng -V 1.6.42
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1857 entries from dependency cache.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-b7e29840db99b212fea1b1aa2367fe2a98d07755"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:b7e29840db99b212fea1b1aa2367fe2a98d07755"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match,
100% complete)
done.
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
Loading cache...done.
Loaded 1857 entries from dependency cache.
Parsing recipes...done.
Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-b7e29840db99b212fea1b1aa2367fe2a98d07755"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:b7e29840db99b212fea1b1aa2367fe2a98d07755"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96%
complete)
done.
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
NOTE: The errors for this build are stored in
/home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215152249.txt
You can send the errors to a reports server by running:
send-error-report
/home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215152249.txt
[-s server]
NOTE: The contents of these logs will be posted in public if you use the above
command with the default server. Please ensure you remove any identifying or
proprietary information when prompted before sending.
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching
https://downloads.sourceforge.net/libpng/libpng16/libpng-1.6.42.tar.xz...
ERROR: Bitbake Fetcher Error: UnpackError('Unpack command
PATH="/home/pokybuild/yocto-worker/auh/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/scripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-c19n0ui0/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-c19n0ui0/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-c19n0ui0/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-c19n0ui0/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-c19n0ui0/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-c19n0ui0/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/hosttools"
xz -dc /srv/aut
obuilder/autobuilder.yocto.io/current_sources/libpng-1.6.42.tar.xz | tar
--extract --no-same-owner -f - failed with return value 2',
'https://downloads.sourceforge.net/libpng/libpng16/libpng-1.6.42.tar.xz')
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-c19n0ui0/work/temp/log.do_unpack.405528
ERROR: Failed to fetch URL
https://downloads.sourceforge.net/libpng/libpng16/libpng-1.6.42.tar.xz
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
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] icu: upgrading to 74-2 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *icu* to *74-2* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade icu -V 74-2
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1857 entries from dependency cache.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-80a361dcef41da3c1c486879bea167af5e18d820"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:80a361dcef41da3c1c486879bea167af5e18d820"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 23 (100% match,
100% complete)
done.
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
Loading cache...done.
Loaded 1857 entries from dependency cache.
Parsing recipes...done.
Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-80a361dcef41da3c1c486879bea167af5e18d820"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:80a361dcef41da3c1c486879bea167af5e18d820"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0%
complete)
done.
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 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: 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: Fetching
https://github.com/unicode-org/icu/releases/download/release-74-2/icu4c-74_2-src.tgz;name=code...
INFO: Rebasing devtool onto a1878f7f36979adca66ab54804a463a688767df3
INFO: Rebasing devtool-override-class-target onto
a1878f7f36979adca66ab54804a463a688767df3
Traceback (most recent call last):
File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 350, in
ret = main()
^^
File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 337, in
main
ret = args.func(args, config, basepath, workspace)
File "/home/pokybuild/yocto-worker/auh/build/scripts/lib/devtool/upgrade.py",
line 582, in upgrade
new_licenses = _extract_licenses(srctree_s, (rd.getVar('LIC_FILES_CHKSUM')
or ""))
^^^
File "/home/pokybuild/yocto-worker/auh/build/scripts/lib/devtool/upgrade.py",
line 490, in _extract_licenses
with open(os.path.join(srcpath, path), 'rb') as f:
^^^
FileNotFoundError: [Errno 2] No such file or directory:
'/home/pokybuild/yocto-worker/auh/build/build/workspace/sources/icu/source/../LICENSE'
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 (#195667):
https://lists.openembedded.org/g/openembedded-core/message/195667
Mute This Topic: https://lists.openembedded.org/mt/104377562/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] sqlite3: upgrading to 3.45.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *sqlite3* to *3.45.1* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade sqlite3 -V 3.45.1 NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-fb7e1e9ea6ec97d9a42acdbc79899575ed077326" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:fb7e1e9ea6ec97d9a42acdbc79899575ed077326" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 9 Local 9 Mirrors 0 Missed 0 Current 21 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-fb7e1e9ea6ec97d9a42acdbc79899575ed077326" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:fb7e1e9ea6ec97d9a42acdbc79899575ed077326" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks WARNING: Failed to fetch URL http://www.sqlite.org/2023/sqlite-autoconf-3450100.tar.gz, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds NOTE: The errors for this build are stored in /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215172450.txt You can send the errors to a reports server by running: send-error-report /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215172450.txt [-s server] NOTE: The contents of these logs will be posted in public if you use the above command with the default server. Please ensure you remove any identifying or proprietary information when prompted before sending. INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Fetching http://www.sqlite.org/2023/sqlite-autoconf-3450100.tar.gz... ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export SSL_CERT_FILE="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; export GIT_SSL_CAINFO="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; 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/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/scripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-yicvekmz/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-yicvekmz/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-yicvekmz/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipe tool-yicvekmz/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-yicvekmz/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-yicvekmz/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/hosttools"; export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp --user-agent='Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0' -O
[OE-core] [AUH] gstreamer1.0-omx: upgrading to 1.22.10 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-omx* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am 0001-gstreamer1.0-omx-upgrade-1.22.9-1.22.10.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
-- >8 --
>From 639b8c605673ce82b7b5c50b95644b45c8167898 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:50:50 +
Subject: [PATCH] gstreamer1.0-omx: upgrade 1.22.9 -> 1.22.10
---
.../{gstreamer1.0-omx_1.22.9.bb => gstreamer1.0-omx_1.22.10.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-omx_1.22.9.bb =>
gstreamer1.0-omx_1.22.10.bb} (95%)
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.9.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.10.bb
similarity index 95%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.9.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.10.bb
index 05d64748bb..4cb83937dc 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.9.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.10.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=4fbd65380cdd255951079008b364516c \
SRC_URI = "https://gstreamer.freedesktop.org/src/gst-omx/gst-omx-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"9362d6117985d09dcf6e27bdaef377dc08efb7df01d00101d04fb644addac61e"
+SRC_URI[sha256sum] =
"ce0126f6de908df4fa7b12136d47d6840dd9f7131ae997e55a817d96a2728a41"
S = "${WORKDIR}/gst-omx-${PV}"
--
2.42.0
0001-gstreamer1.0-omx-upgrade-1.22.9-1.22.10.patch
Description: Binary data
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-dbg: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-dbg: PKGSIZE
changed from 1224832 to 1224864 (+0%)
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-dbg: PV changed
from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-dev: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-dev: PV changed
from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-doc: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-doc: PV changed
from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-locale: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-locale: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-src: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-src: PV changed
from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-staticdev: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx-staticdev: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx: PKGV changed
from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx/gstreamer1.0-omx: PV changed from
"1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-omx: PKGV changed from 1.22.9
[default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-omx: SRC_URI changed from
"https://gstreamer.freedesktop.org/src/gst-omx/gst-omx-1.22.9.tar.xz; to
"https://gstreamer.freedesktop.org/src/gst-omx/gst-omx-1.22.10.tar.xz;
packages/core2-64-poky-linux/gstreamer1.0-omx: PV changed from "1.22.9" to
"1.22.10"
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (0 cached, 914 parsed). 1858 targets, 46
skipped, 0 masked, 0 errors.
Removing 109 recipes from the core2-64 sysroot...done.
Removing 108 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS
[OE-core] [AUH] puzzles: upgrading to 7a93ae5d3c90cb5d1d8d775a8cd9d30bc745f658 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *puzzles* to *7a93ae5d3c90cb5d1d8d775a8cd9d30bc745f658* has Succeeded. Next steps: - apply the patch: git am 0001-puzzles-upgrade-to-latest-revision.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 -- >8 -- From 581efc4ef6f52470dacc646ecc8a33c468487356 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Thu, 15 Feb 2024 15:25:58 + Subject: [PATCH] puzzles: upgrade to latest revision --- meta/recipes-sato/puzzles/puzzles_git.bb | 23 +-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/meta/recipes-sato/puzzles/puzzles_git.bb b/meta/recipes-sato/puzzles/puzzles_git.bb index ab4b2394b8..6101635f56 100644 --- a/meta/recipes-sato/puzzles/puzzles_git.bb +++ b/meta/recipes-sato/puzzles/puzzles_git.bb @@ -1,8 +1,27 @@ +# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'. +# The following is the difference between the old and the new license text. +# Please update the LICENSE value if needed, and summarize the changes in +# the commit message via 'License-Update:' tag. +# (example: 'License-Update: copyright years updated.') +# +# The changes: +# +# --- LICENCE +# +++ LICENCE +# @@ -1,4 +1,4 @@ +# -This software is copyright (c) 2004-2023 Simon Tatham. +# +This software is copyright (c) 2004-2024 Simon Tatham. +# +# Portions copyright Richard Boulton, James Harvey, Mike Pinna, Jonas +# Kölker, Dariusz Olszewski, Michael Schierl, Lambros Lambrou, Bernd +# +# + SUMMARY = "Simon Tatham's Portable Puzzle Collection" DESCRIPTION = "Collection of small computer programs which implement one-player puzzle games." HOMEPAGE = "http://www.chiark.greenend.org.uk/~sgtatham/puzzles/; LICENSE = "MIT" -LIC_FILES_CHKSUM = "file://LICENCE;md5=92d2b7a2fc96b5f7f17101df7db1fefa" +LIC_FILES_CHKSUM = "file://LICENCE;md5=191542b32377bde254e9799e0a46f18b" # gtk support includes a bunch of x11 headers REQUIRED_DISTRO_FEATURES = "x11" @@ -10,7 +29,7 @@ REQUIRED_DISTRO_FEATURES = "x11" SRC_URI = "git://git.tartarus.org/simon/puzzles.git;branch=main;protocol=https" UPSTREAM_CHECK_COMMITS = "1" -SRCREV = "08365fb260ae6e32442dd9f196e65d13facb4b33" +SRCREV = "7a93ae5d3c90cb5d1d8d775a8cd9d30bc745f658" PE = "2" PV = "0.0+git" -- 2.42.0 packages/core2-64-poky-linux/puzzles/puzzles-dbg: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-dev: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-dev: RRECOMMENDS: removed "puzzles (['= 2:0.0+git0+08365fb260-r0'])", added "puzzles (['= 2:0.0+git0+7a93ae5d3c-r0'])" packages/core2-64-poky-linux/puzzles/puzzles-doc: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-locale: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-src: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-src: PKGSIZE changed from 3838531 to 3838603 (+0%) packages/core2-64-poky-linux/puzzles/puzzles-staticdev: RDEPENDS: removed "puzzles-dev (['= 2:0.0+git0+08365fb260-r0'])", added "puzzles-dev (['= 2:0.0+git0+7a93ae5d3c-r0'])" packages/core2-64-poky-linux/puzzles/puzzles-staticdev: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c 0001-puzzles-upgrade-to-latest-revision.patch Description: Binary data packages/core2-64-poky-linux/puzzles/puzzles-dbg: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-dev: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-dev: RRECOMMENDS: removed "puzzles (['= 2:0.0+git0+08365fb260-r0'])", added "puzzles (['= 2:0.0+git0+7a93ae5d3c-r0'])" packages/core2-64-poky-linux/puzzles/puzzles-doc: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-locale: PKGV changed from 0.0+git0+08365fb260 to 0.0+git0+7a93ae5d3c packages/core2-64-poky-linux/puzzles/puzzles-src:
[OE-core] [AUH] gstreamer1.0: upgrading to 1.22.10 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0* to *1.22.10*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-gstreamer1.0-upgrade-1.22.9-1.22.10.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
-- >8 --
>From 62d5778f340110426d5bf248d95f0c19118f6a0a Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 15:21:58 +
Subject: [PATCH] gstreamer1.0: upgrade 1.22.9 -> 1.22.10
---
...spect-the-idententaion-used-in-meson.patch | 2 +-
...ts-add-support-for-install-the-tests.patch | 4 +-
...s-use-a-dictionaries-for-environment.patch | 20 +-
...er-script-to-run-the-installed_tests.patch | 40 +--
...r1.0_1.22.9.bb => gstreamer1.0_1.22.10.bb} | 2 +-
5 files changed, 32 insertions(+), 36 deletions(-)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0_1.22.9.bb =>
gstreamer1.0_1.22.10.bb} (97%)
diff --git
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-tests-respect-the-idententaion-used-in-meson.patch
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-tests-respect-the-idententaion-used-in-meson.patch
index 1b9278db04..0d839bd6c8 100644
---
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-tests-respect-the-idententaion-used-in-meson.patch
+++
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-tests-respect-the-idententaion-used-in-meson.patch
@@ -1,4 +1,4 @@
-From 559e1dd850b2b9eb3a415aa43e932e5e48f605cd Mon Sep 17 00:00:00 2001
+From 5372cd5bf2a9dd247b9c5fc6e4fe248046dbb085 Mon Sep 17 00:00:00 2001
From: Jose Quaresma
Date: Sun, 11 Apr 2021 19:48:13 +0100
Subject: [PATCH] tests: respect the idententaion used in meson
diff --git
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-tests-add-support-for-install-the-tests.patch
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-tests-add-support-for-install-the-tests.patch
index 568e38cbf1..64717e66c3 100644
---
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-tests-add-support-for-install-the-tests.patch
+++
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-tests-add-support-for-install-the-tests.patch
@@ -1,4 +1,4 @@
-From 08b1aaff972a7f6349373fc1ad4cc23081adb52c Mon Sep 17 00:00:00 2001
+From 27e977d03b0f7c1d0bf19621ef0cec0585410e7b Mon Sep 17 00:00:00 2001
From: Jose Quaresma
Date: Sun, 11 Apr 2021 19:48:13 +0100
Subject: [PATCH] tests: add support for install the tests
@@ -20,7 +20,7 @@ Signed-off-by: Jose Quaresma
create mode 100644 tests/check/template.test.in
diff --git a/meson.build b/meson.build
-index f9f591d..3906fb3 100644
+index 60c7bec..f7650b1 100644
--- a/meson.build
+++ b/meson.build
@@ -606,6 +606,10 @@ if bashcomp_dep.found()
diff --git
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0003-tests-use-a-dictionaries-for-environment.patch
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0003-tests-use-a-dictionaries-for-environment.patch
index 10a6dcc619..0fd830f150 100644
---
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0003-tests-use-a-dictionaries-for-environment.patch
+++
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0003-tests-use-a-dictionaries-for-environment.patch
@@ -1,7 +1,7 @@
-From fe830f0f75f3b4b41e3dbef8d4cf6ee4103c9e06 Mon Sep 17 00:00:00 2001
+From 7041bc5adf9501beb1428d8bbae6b351a6bf07f9 Mon Sep 17 00:00:00 2001
From: Jose Quaresma
Date: Sat, 24 Apr 2021 10:34:47 +0100
-Subject: [PATCH 3/4] tests: use a dictionaries for environment
+Subject: [PATCH] tests: use a dictionaries for environment
meson environment() can't be passed to configure_file and it is needed for
installed_tests,
use a dictionary as this is simplest solution to install the environment.
@@ -9,15 +9,16 @@ use a dictionary as this is simplest solution to install the
environment.
Upstream-Status: Submitted
[https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/789]
Signed-off-by: Jose Quaresma
+
---
- subprojects/gstreamer/tests/check/meson.build | 21 ---
+ tests/check/meson.build | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
-diff --git a/subprojects/gstreamer/tests/check/meson.build
b/subprojects/gstreamer/tests/check/meson.build
-index
[OE-core] [AUH] libsdl2: upgrading to 2.30.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsdl2* to *2.30.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsdl2-upgrade-2.28.5-2.30.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
-- >8 --
>From ac94f03ba14596f601174c5ff0dc4973d587032e Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 13:11:11 +
Subject: [PATCH] libsdl2: upgrade 2.28.5 -> 2.30.0
---
.../{libsdl2_2.28.5.bb => libsdl2_2.30.0.bb} | 32 +++
1 file changed, 25 insertions(+), 7 deletions(-)
rename meta/recipes-graphics/libsdl2/{libsdl2_2.28.5.bb => libsdl2_2.30.0.bb}
(75%)
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.28.5.bb
b/meta/recipes-graphics/libsdl2/libsdl2_2.30.0.bb
similarity index 75%
rename from meta/recipes-graphics/libsdl2/libsdl2_2.28.5.bb
rename to meta/recipes-graphics/libsdl2/libsdl2_2.30.0.bb
index fd876df0ad..1a3802af53 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.28.5.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.30.0.bb
@@ -1,3 +1,22 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- LICENSE.txt
+# +++ LICENSE.txt
+# @@ -1,4 +1,4 @@
+# -Copyright (C) 1997-2023 Sam Lantinga
+# +Copyright (C) 1997-2024 Sam Lantinga
+#
+# This software is provided 'as-is', without any express or implied
+# warranty. In no event will the authors be held liable for any damages
+#
+#
+
SUMMARY = "Simple DirectMedia Layer"
DESCRIPTION = "Simple DirectMedia Layer is a cross-platform multimedia \
library designed to provide low level access to audio, keyboard, mouse, \
@@ -8,12 +27,11 @@ BUGTRACKER = "http://bugzilla.libsdl.org/;
SECTION = "libs"
LICENSE = "Zlib & BSD-2-Clause"
-LIC_FILES_CHKSUM = "\
-file://LICENSE.txt;md5=31f575634fd56b27fc6b6cbe8dc9bd38 \
-file://src/hidapi/LICENSE.txt;md5=7c3949a631240cb6c31c50f3eb696077 \
-file://src/hidapi/LICENSE-bsd.txt;md5=b5fa085ce0926bb50d0621620a82361f \
-file://src/video/yuv2rgb/LICENSE;md5=79f8f3418d91531e05f0fc94ca67e071 \
-"
+LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=25231a5b96ccdd8f39eb53c07717be64 \
+
file://src/hidapi/LICENSE.txt;md5=7c3949a631240cb6c31c50f3eb696077 \
+
file://src/hidapi/LICENSE-bsd.txt;md5=b5fa085ce0926bb50d0621620a82361f \
+
file://src/video/yuv2rgb/LICENSE;md5=79f8f3418d91531e05f0fc94ca67e071 \
+"
# arm-neon adds MIT license
LICENSE:append = " ${@bb.utils.contains('PACKAGECONFIG', 'arm-neon', '& MIT',
'', d)}"
@@ -25,7 +43,7 @@ SRC_URI = "http://www.libsdl.org/release/SDL2-${PV}.tar.gz;
S = "${WORKDIR}/SDL2-${PV}"
-SRC_URI[sha256sum] =
"332cb37d0be20cb9541739c61f79bae5a477427d79ae85e352089afdafe4"
+SRC_URI[sha256sum] =
"36e2e41557e0fa4a1519315c0f5958a87ccb27e25c51776beb6f1239526447b0"
inherit cmake lib_package binconfig-disabled pkgconfig upstream-version-is-even
--
2.42.0
packages/core2-64-poky-linux/libsdl2: SRC_URI changed from
"http://www.libsdl.org/release/SDL2-2.28.5.tar.gz; to
"http://www.libsdl.org/release/SDL2-2.30.0.tar.gz;
packages/core2-64-poky-linux/libsdl2: PKGV changed from 2.28.5 [default] to
2.30.0 [default]
packages/core2-64-poky-linux/libsdl2: PV changed from "2.28.5" to "2.30.0"
packages/core2-64-poky-linux/libsdl2/libsdl2-bin: PKGV changed from 2.28.5
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/libsdl2/libsdl2-bin: PV changed from "2.28.5" to
"2.30.0"
packages/core2-64-poky-linux/libsdl2/libsdl2-dbg: PKGV changed from 2.28.5
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/libsdl2/libsdl2-dbg: PV changed from "2.28.5" to
"2.30.0"
packages/core2-64-poky-linux/libsdl2/libsdl2-dbg: FILELIST: removed
"/usr/lib/.debug/libSDL2-2.0.so.0.2800.5", added
"/usr/lib/.debug/libSDL2-2.0.so.0.3000.0"
packages/core2-64-poky-linux/libsdl2/libsdl2-dbg: PKGSIZE changed from 7065280
to 7203104 (+2%)
packages/core2-64-poky-linux/libsdl2/libsdl2-dev: PKGV changed
[OE-core] [AUH] xprop: 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 *xprop* to *1.2.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xprop-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
-- >8 --
>From 48e0253043f0ae5731cb83e0ddc619b579e73b22 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:17:17 +
Subject: [PATCH] xprop: upgrade 1.2.6 -> 1.2.7
---
.../xorg-app/{xprop_1.2.6.bb => xprop_1.2.7.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xorg-app/{xprop_1.2.6.bb => xprop_1.2.7.bb} (86%)
diff --git a/meta/recipes-graphics/xorg-app/xprop_1.2.6.bb
b/meta/recipes-graphics/xorg-app/xprop_1.2.7.bb
similarity index 86%
rename from meta/recipes-graphics/xorg-app/xprop_1.2.6.bb
rename to meta/recipes-graphics/xorg-app/xprop_1.2.7.bb
index 438a897f1e..96e364b2b3 100644
--- a/meta/recipes-graphics/xorg-app/xprop_1.2.6.bb
+++ b/meta/recipes-graphics/xorg-app/xprop_1.2.7.bb
@@ -15,4 +15,4 @@ DEPENDS += "libxmu"
PE = "1"
SRC_URI_EXT = "xz"
-SRC_URI[sha256sum] =
"580b8525b12ecc0144aa16c88b0aafa76d2e799b44c8c6c50f9ce92788b5586e"
+SRC_URI[sha256sum] =
"4436e3148bb91a162406230d9f736a49ca8b50b74790015dc15d78d6ce8e825f"
--
2.42.0
packages/core2-64-poky-linux/xprop: SRC_URI changed from
"https://www.x.org/releases//individual/app/xprop-1.2.6.tar.xz; to
"https://www.x.org/releases//individual/app/xprop-1.2.7.tar.xz;
packages/core2-64-poky-linux/xprop: PV changed from "1.2.6" to "1.2.7"
packages/core2-64-poky-linux/xprop: PKGV changed from 1.2.6 [default] to 1.2.7
[default]
packages/core2-64-poky-linux/xprop/xprop-dbg: PV changed from "1.2.6" to "1.2.7"
packages/core2-64-poky-linux/xprop/xprop-dbg: PKGV changed from 1.2.6 [default]
to 1.2.7 [default]
packages/core2-64-poky-linux/xprop/xprop-dev: PV changed from "1.2.6" to "1.2.7"
packages/core2-64-poky-linux/xprop/xprop-dev: PKGV changed from 1.2.6 [default]
to 1.2.7 [default]
packages/core2-64-poky-linux/xprop/xprop-doc: PV changed from "1.2.6" to "1.2.7"
packages/core2-64-poky-linux/xprop/xprop-doc: PKGV changed from 1.2.6 [default]
to 1.2.7 [default]
packages/core2-64-poky-linux/xprop/xprop-locale: PV changed from "1.2.6" to
"1.2.7"
packages/core2-64-poky-linux/xprop/xprop-locale: PKGV changed from 1.2.6
[default] to 1.2.7 [default]
packages/core2-64-poky-linux/xprop/xprop-src: PKGSIZE changed from 71371 to
71380 (+0%)
packages/core2-64-poky-linux/xprop/xprop-src: PV changed from "1.2.6" to "1.2.7"
packages/core2-64-poky-linux/xprop/xprop-src: PKGV changed from 1.2.6 [default]
to 1.2.7 [default]
packages/core2-64-poky-linux/xprop/xprop-staticdev: PV changed from "1.2.6" to
"1.2.7"
packages/core2-64-poky-linux/xprop/xprop-staticdev: PKGV changed from 1.2.6
[default] to 1.2.7 [default]
packages/core2-64-poky-linux/xprop/xprop: PV changed from "1.2.6" to "1.2.7"
packages/core2-64-poky-linux/xprop/xprop: PKGV changed from 1.2.6 [default] to
1.2.7 [default]
0001-xprop-upgrade-1.2.6-1.2.7.patch
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195646):
https://lists.openembedded.org/g/openembedded-core/message/195646
Mute This Topic: https://lists.openembedded.org/mt/104377541/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] lttng-ust: upgrading to 2.13.7 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *lttng-ust* to *2.13.7* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe lttng-ust failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-4d8fea01d12c7b8d5b653330b8273e56db3fb5bb" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:4d8fea01d12c7b8d5b653330b8273e56db3fb5bb" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-4d8fea01d12c7b8d5b653330b8273e56db3fb5bb" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:4d8fea01d12c7b8d5b653330b8273e56db3fb5bb" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 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://lttng.org/files/lttng-ust/lttng-ust-2.13.7.tar.bz2... INFO: Rebasing devtool onto af3d29e61aff2b6c74dfdb753e41feef4a74fdbf WARNING: Command 'git rebase af3d29e61aff2b6c74dfdb753e41feef4a74fdbf' failed: Auto-merging src/python-lttngust/Makefile.am CONFLICT (content): Merge conflict in src/python-lttngust/Makefile.am You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/lttng-ust INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/lttng-ust/lttng-ust_2.13.7.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 (#195657): https://lists.openembedded.org/g/openembedded-core/message/195657 Mute This Topic: https://lists.openembedded.org/mt/104377552/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] libpciaccess: upgrading to 0.18 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libpciaccess* to *0.18* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libpciaccess-upgrade-0.17-0.18.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
-- >8 --
>From f38a2472c1bdba08ddf377e0174f9717cbb19965 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:18:37 +
Subject: [PATCH] libpciaccess: upgrade 0.17 -> 0.18
---
...pwrite-pread-instead-of-64bit-versio.patch | 39 ---
...pciaccess_0.17.bb => libpciaccess_0.18.bb} | 28 +++--
2 files changed, 24 insertions(+), 43 deletions(-)
delete mode 100644
meta/recipes-graphics/xorg-lib/libpciaccess/0001-linux_sysfs-Use-pwrite-pread-instead-of-64bit-versio.patch
rename meta/recipes-graphics/xorg-lib/{libpciaccess_0.17.bb =>
libpciaccess_0.18.bb} (24%)
diff --git
a/meta/recipes-graphics/xorg-lib/libpciaccess/0001-linux_sysfs-Use-pwrite-pread-instead-of-64bit-versio.patch
b/meta/recipes-graphics/xorg-lib/libpciaccess/0001-linux_sysfs-Use-pwrite-pread-instead-of-64bit-versio.patch
deleted file mode 100644
index 512a473e20..00
---
a/meta/recipes-graphics/xorg-lib/libpciaccess/0001-linux_sysfs-Use-pwrite-pread-instead-of-64bit-versio.patch
+++ /dev/null
@@ -1,39 +0,0 @@
-From d20ff4f2e4feaafa6a6191b9cae3815b85617943 Mon Sep 17 00:00:00 2001
-From: Khem Raj
-Date: Fri, 11 Nov 2022 11:15:58 -0800
-Subject: [PATCH] linux_sysfs: Use pwrite/pread instead of 64bit versions
-
-pread64/pwrite64 are aliased to pread/pwrite when largefile support is
-enabled e.g. using _FILE_OFFSET_BITS=64 macro
-
-Upstream-Status: Submitted
[https://gitlab.freedesktop.org/xorg/lib/libpciaccess/-/merge_requests/26]
-Signed-off-by: Khem Raj
- src/linux_sysfs.c | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/src/linux_sysfs.c b/src/linux_sysfs.c
-index d62f48c..20c800e 100644
a/src/linux_sysfs.c
-+++ b/src/linux_sysfs.c
-@@ -462,7 +462,7 @@ pci_device_linux_sysfs_read( struct pci_device * dev, void
* data,
-
-
- while ( temp_size > 0 ) {
-- const ssize_t bytes = pread64( fd, data_bytes, temp_size, offset );
-+ const ssize_t bytes = pread( fd, data_bytes, temp_size, offset );
-
- /* If zero bytes were read, then we assume it's the end of the
-* config file.
-@@ -522,7 +522,7 @@ pci_device_linux_sysfs_write( struct pci_device * dev,
const void * data,
-
-
- while ( temp_size > 0 ) {
-- const ssize_t bytes = pwrite64( fd, data_bytes, temp_size, offset );
-+ const ssize_t bytes = pwrite( fd, data_bytes, temp_size, offset );
-
- /* If zero bytes were written, then we assume it's the end of the
-* config file.
---
-2.38.1
-
diff --git a/meta/recipes-graphics/xorg-lib/libpciaccess_0.17.bb
b/meta/recipes-graphics/xorg-lib/libpciaccess_0.18.bb
similarity index 24%
rename from meta/recipes-graphics/xorg-lib/libpciaccess_0.17.bb
rename to meta/recipes-graphics/xorg-lib/libpciaccess_0.18.bb
index 54bdb08976..d275076043 100644
--- a/meta/recipes-graphics/xorg-lib/libpciaccess_0.17.bb
+++ b/meta/recipes-graphics/xorg-lib/libpciaccess_0.18.bb
@@ -1,3 +1,25 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- COPYING
+# +++ COPYING
+# @@ -2,7 +2,7 @@
+# (C) Copyright Eric Anholt 2006
+# (C) Copyright Mark Kettenis 2011
+# (C) Copyright Robert Millan 2012
+# -Copyright (c) 2007, 2008, 2009, 2011, 2012, 2013 Oracle and/or its
affiliates.
+# +Copyright (c) 2007, 2008, 2009, 2011, 2012, 2016 Oracle and/or its
affiliates.
+# Copyright 2009, 2012 Red Hat, Inc.
+# All Rights Reserved.
+#
+#
+#
+
SUMMARY = "Generic PCI access library for X"
DESCRIPTION = "libpciaccess provides functionality for X to access the \
@@ -5,12 +27,10 @@ PCI bus and devices in a platform-independent way."
require xorg-lib-common.inc
-SRC_URI +=
[OE-core] [AUH] libtraceevent: upgrading to 1.8.2 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libtraceevent* to *1.8.2* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libtraceevent failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-08a21abdc7184bc6c6a2c1aee479aac6e2cd148f" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:08a21abdc7184bc6c6a2c1aee479aac6e2cd148f" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 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 6f6d5802f31992e7527a4c32b43a32fda6bf6bdf WARNING: Command 'git rebase 6f6d5802f31992e7527a4c32b43a32fda6bf6bdf' failed: Auto-merging meson.build CONFLICT (content): Merge conflict in meson.build Auto-merging meson_options.txt You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/libtraceevent INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/libtraceevent/libtraceevent_1.8.2.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 (#195651): https://lists.openembedded.org/g/openembedded-core/message/195651 Mute This Topic: https://lists.openembedded.org/mt/104377546/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] glslang: upgrading to 1.3.275.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glslang* to *1.3.275.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-glslang-upgrade-1.3.268.0-1.3.275.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
-- >8 --
>From 4da49d939c048174a5e623b0d80df536bba3ae78 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 13:06:07 +
Subject: [PATCH] glslang: upgrade 1.3.268.0 -> 1.3.275.0
---
.../glslang/0001-generate-glslang-pkg-config.patch | 12 ++--
.../{glslang_1.3.268.0.bb => glslang_1.3.275.0.bb} | 2 +-
2 files changed, 7 insertions(+), 7 deletions(-)
rename meta/recipes-graphics/glslang/{glslang_1.3.268.0.bb =>
glslang_1.3.275.0.bb} (96%)
diff --git
a/meta/recipes-graphics/glslang/glslang/0001-generate-glslang-pkg-config.patch
b/meta/recipes-graphics/glslang/glslang/0001-generate-glslang-pkg-config.patch
index a2dcb13b36..7ed938e0b8 100644
---
a/meta/recipes-graphics/glslang/glslang/0001-generate-glslang-pkg-config.patch
+++
b/meta/recipes-graphics/glslang/glslang/0001-generate-glslang-pkg-config.patch
@@ -1,4 +1,4 @@
-From e8c1b7e1dc6d108a3b49d0adfdc4f836cfafcf1a Mon Sep 17 00:00:00 2001
+From a369bce8dd890f6260fc29b941b07b0a6c284a3c Mon Sep 17 00:00:00 2001
From: Jose Quaresma
Date: Sun, 7 Feb 2021 01:30:39 +
Subject: [PATCH] generate glslang pkg-config
@@ -16,21 +16,21 @@ Signed-off-by: Jose Quaresma
create mode 100644 glslang/glslang.pc.cmake.in
diff --git a/glslang/CMakeLists.txt b/glslang/CMakeLists.txt
-index 72e82b48..c6188e12 100644
+index 37eecaad..6974935c 100644
--- a/glslang/CMakeLists.txt
+++ b/glslang/CMakeLists.txt
-@@ -223,6 +223,8 @@ if(ENABLE_GLSLANG_INSTALL)
+@@ -251,6 +251,8 @@ if(PROJECT_IS_TOP_LEVEL)
")
install(FILES "${CMAKE_CURRENT_BINARY_DIR}/glslangTargets.cmake"
DESTINATION ${CMAKE_INSTALL_LIBDIR}/cmake)
endif()
+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/glslang.pc.cmake.in
${CMAKE_CURRENT_BINARY_DIR}/pkgconfig/glslang.pc @ONLY)
+install(FILES ${CMAKE_CURRENT_BINARY_DIR}/pkgconfig/glslang.pc
DESTINATION ${CMAKE_INSTALL_LIBDIR}/pkgconfig)
- set(ALL_HEADERS
- ${GLSLANG_HEADERS}
+ set(PUBLIC_HEADERS
+ Public/ResourceLimits.h
diff --git a/glslang/glslang.pc.cmake.in b/glslang/glslang.pc.cmake.in
new file mode 100644
-index ..948a0952
+index ..43104e68
--- /dev/null
+++ b/glslang/glslang.pc.cmake.in
@@ -0,0 +1,11 @@
diff --git a/meta/recipes-graphics/glslang/glslang_1.3.268.0.bb
b/meta/recipes-graphics/glslang/glslang_1.3.275.0.bb
similarity index 96%
rename from meta/recipes-graphics/glslang/glslang_1.3.268.0.bb
rename to meta/recipes-graphics/glslang/glslang_1.3.275.0.bb
index 033830ba36..2fd1e72a26 100644
--- a/meta/recipes-graphics/glslang/glslang_1.3.268.0.bb
+++ b/meta/recipes-graphics/glslang/glslang_1.3.275.0.bb
@@ -8,7 +8,7 @@ HOMEPAGE =
"https://www.khronos.org/opengles/sdk/tools/Reference-Compiler;
LICENSE = "BSD-3-Clause & BSD-2-Clause & MIT & Apache-2.0 &
GPL-3-with-bison-exception"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=2a2b5acd7bc4844964cfda45fe807dc3"
-SRCREV = "36d08c0d940cf307a23928299ef52c7970d8cee6"
+SRCREV = "a91631b260cba3f22858d6c6827511e636c2458a"
SRC_URI =
"git://github.com/KhronosGroup/glslang.git;protocol=https;branch=main \
file://0001-generate-glslang-pkg-config.patch \
"
--
2.42.0
packages/core2-64-poky-linux/glslang/glslang-dbg: PKGSIZE changed from 82309528
to 82472200 (+0%)
packages/core2-64-poky-linux/glslang/glslang-dbg: FILELIST: removed
"/usr/lib/.debug/libSPIRV.so.13.1.1 /usr/lib/.debug/libglslang.so.13.1.1
/usr/lib/.debug/libSPVRemapper.so.13.1.1
/usr/lib/.debug/libglslang-default-resource-limits.so.13.1.1
/usr/lib/.debug/libHLSL.so.13.1.1", added "/usr/lib/.debug/libglslang.so.14.0.0
/usr/lib/.debug/libglslang-default-resource-limits.so.14.0.0
/usr/lib/.debug/libSPIRV.so.14.0.0 /usr/lib/.debug/libSPVRemapper.so.14.0.0"
packages/core2-64-poky-linux/glslang/glslang-dbg: PKGV changed from 1.3.268.0
[default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/glslang/glslang-dbg: PV changed from "1.3.268.0"
to "1.3.275.0"
packages/core2-64-poky-linux/glslang/glslang-dev: PKGSIZE changed from 1019651
[OE-core] [AUH] makedepend: upgrading to 1.0.9 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *makedepend* to *1.0.9* has
Succeeded.
Next steps:
- apply the patch: git am 0001-makedepend-upgrade-1.0.8-1.0.9.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
-- >8 --
>From 843fdc2033a3189d72dd7672b5819c6283ae3ff0 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:30:27 +
Subject: [PATCH] makedepend: upgrade 1.0.8 -> 1.0.9
---
.../xorg-util/{makedepend_1.0.8.bb => makedepend_1.0.9.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xorg-util/{makedepend_1.0.8.bb =>
makedepend_1.0.9.bb} (88%)
diff --git a/meta/recipes-graphics/xorg-util/makedepend_1.0.8.bb
b/meta/recipes-graphics/xorg-util/makedepend_1.0.9.bb
similarity index 88%
rename from meta/recipes-graphics/xorg-util/makedepend_1.0.8.bb
rename to meta/recipes-graphics/xorg-util/makedepend_1.0.9.bb
index ad769de205..6db7d04079 100644
--- a/meta/recipes-graphics/xorg-util/makedepend_1.0.8.bb
+++ b/meta/recipes-graphics/xorg-util/makedepend_1.0.9.bb
@@ -17,4 +17,4 @@ BBCLASSEXTEND = "native"
LIC_FILES_CHKSUM = "file://COPYING;md5=43a6eda34b48ee821b3b66f4f753ce4f"
-SRC_URI[sha256sum] =
"275f0d2b196bfdc740aab9f02bb48cb7a97e4dfea011a7b468ed5648d0019e54"
+SRC_URI[sha256sum] =
"bc94ffda6cd4671603a69c39dbe8f96b317707b9185b2aaa3b54b5d134b41884"
--
2.42.0
packages/core2-64-poky-linux/makedepend: SRC_URI changed from
"https://www.x.org/releases//individual/util/makedepend-1.0.8.tar.gz; to
"https://www.x.org/releases//individual/util/makedepend-1.0.9.tar.gz;
packages/core2-64-poky-linux/makedepend: PKGV changed from 1.0.8 [default] to
1.0.9 [default]
packages/core2-64-poky-linux/makedepend: PV changed from "1.0.8" to "1.0.9"
packages/core2-64-poky-linux/makedepend/makedepend-dbg: PKGV changed from 1.0.8
[default] to 1.0.9 [default]
packages/core2-64-poky-linux/makedepend/makedepend-dbg: PV changed from "1.0.8"
to "1.0.9"
packages/core2-64-poky-linux/makedepend/makedepend-dbg: PKGSIZE changed from
91528 to 93472 (+2%)
packages/core2-64-poky-linux/makedepend/makedepend-dev: PKGV changed from 1.0.8
[default] to 1.0.9 [default]
packages/core2-64-poky-linux/makedepend/makedepend-dev: PV changed from "1.0.8"
to "1.0.9"
packages/core2-64-poky-linux/makedepend/makedepend-doc: PKGV changed from 1.0.8
[default] to 1.0.9 [default]
packages/core2-64-poky-linux/makedepend/makedepend-doc: PV changed from "1.0.8"
to "1.0.9"
packages/core2-64-poky-linux/makedepend/makedepend-locale: PKGV changed from
1.0.8 [default] to 1.0.9 [default]
packages/core2-64-poky-linux/makedepend/makedepend-locale: PV changed from
"1.0.8" to "1.0.9"
packages/core2-64-poky-linux/makedepend/makedepend-src: PKGV changed from 1.0.8
[default] to 1.0.9 [default]
packages/core2-64-poky-linux/makedepend/makedepend-src: PV changed from "1.0.8"
to "1.0.9"
packages/core2-64-poky-linux/makedepend/makedepend-src: PKGSIZE changed from
80831 to 94763 (+17%)
packages/core2-64-poky-linux/makedepend/makedepend-staticdev: PKGV changed from
1.0.8 [default] to 1.0.9 [default]
packages/core2-64-poky-linux/makedepend/makedepend-staticdev: PV changed from
"1.0.8" to "1.0.9"
packages/core2-64-poky-linux/makedepend/makedepend: PKGV changed from 1.0.8
[default] to 1.0.9 [default]
packages/core2-64-poky-linux/makedepend/makedepend: PV changed from "1.0.8" to
"1.0.9"
0001-makedepend-upgrade-1.0.8-1.0.9.patch
Description: Binary data
packages/core2-64-poky-linux/makedepend/makedepend-src: PKGSIZE changed from
80831 to 94763 (+17%)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195645):
https://lists.openembedded.org/g/openembedded-core/message/195645
Mute This Topic: https://lists.openembedded.org/mt/104377540/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] vulkan-utility-libraries: upgrading to 1.3.275.0 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-utility-libraries* to
*1.3.275.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-vulkan-utility-libraries-upgrade-1.3.268.0-1.3.275.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
-- >8 --
>From 0d58ee560a2344b56b328cc6185f38809917242e Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:04:29 +
Subject: [PATCH] vulkan-utility-libraries: upgrade 1.3.268.0 -> 1.3.275.0
---
...aries_1.3.268.0.bb => vulkan-utility-libraries_1.3.275.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/vulkan/{vulkan-utility-libraries_1.3.268.0.bb =>
vulkan-utility-libraries_1.3.275.0.bb} (95%)
diff --git a/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.268.0.bb
b/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.275.0.bb
similarity index 95%
rename from meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.268.0.bb
rename to meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.275.0.bb
index fee4ba6cc9..759a03926b 100644
--- a/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.268.0.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.275.0.bb
@@ -10,7 +10,7 @@ LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE.md;md5=4ca2d6799091aaa98a8520f1b793939b"
SRC_URI =
"git://github.com/KhronosGroup/Vulkan-Utility-Libraries.git;branch=main;protocol=https"
-SRCREV = "c9ca4ac620a238a93c65d864f2eaa33954d74509"
+SRCREV = "4cfc176e3242b4dbdfd3f6c5680c5d8f2cb7db45"
S = "${WORKDIR}/git"
--
2.42.0
0001-vulkan-utility-libraries-upgrade-1.3.268.0-1.3.275.0.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1857 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (913 cached, 1 parsed). 1857 targets, 35
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-64 sysroot...done.
Removing 1 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-760e9878e2889dea9c2269e1dd9bba5aba3a5be8"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:760e9878e2889dea9c2269e1dd9bba5aba3a5be8"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 106 Local 97 Mirrors 0 Missed 9 Current 202 (91% match,
97% complete)
done.
NOTE: Executing Tasks
NOTE: Running setscene task 236 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.275.0.bb:do_populate_lic_setscene)
NOTE: Running setscene task 238 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.275.0.bb:do_deploy_source_date_epoch_setscene)
NOTE: recipe vulkan-utility-libraries-1.3.275.0-r0: task
do_populate_lic_setscene: Started
NOTE: recipe vulkan-utility-libraries-1.3.275.0-r0: task
do_deploy_source_date_epoch_setscene: Started
NOTE: recipe vulkan-utility-libraries-1.3.275.0-r0: task
do_deploy_source_date_epoch_setscene: Succeeded
NOTE: recipe vulkan-utility-libraries-1.3.275.0-r0: task
do_populate_lic_setscene: Succeeded
NOTE: Running setscene task 308 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.275.0.bb:do_recipe_qa_setscene)
NOTE: recipe vulkan-utility-libraries-1.3.275.0-r0: task do_recipe_qa_setscene:
Started
NOTE: recipe vulkan-utility-libraries-1.3.275.0-r0: task do_recipe_qa_setscene:
Succeeded
NOTE: Setscene tasks completed
NOTE: Running task 903 of 923
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-utility-libraries_1.3.275.0.bb:do_fetch)
NOTE: recipe vulkan-utility-libraries-1.3.275.0-r0: task
[OE-core] [AUH] taglib: upgrading to 2.0 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *taglib* to *2.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-taglib-upgrade-1.13.1-2.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
-- >8 --
>From e84e7727093f0f3214e8c77305e5e1639586f353 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 17:26:04 +
Subject: [PATCH] taglib: upgrade 1.13.1 -> 2.0
---
meta/recipes-support/taglib/{taglib_1.13.1.bb => taglib_2.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/taglib/{taglib_1.13.1.bb => taglib_2.0.bb} (95%)
diff --git a/meta/recipes-support/taglib/taglib_1.13.1.bb
b/meta/recipes-support/taglib/taglib_2.0.bb
similarity index 95%
rename from meta/recipes-support/taglib/taglib_1.13.1.bb
rename to meta/recipes-support/taglib/taglib_2.0.bb
index b26563ae91..f05e12ea30 100644
--- a/meta/recipes-support/taglib/taglib_1.13.1.bb
+++ b/meta/recipes-support/taglib/taglib_2.0.bb
@@ -11,7 +11,7 @@ DEPENDS = "zlib"
SRC_URI = "http://taglib.github.io/releases/${BP}.tar.gz;
-SRC_URI[sha256sum] =
"c8da2b10f1bfec2cd7dbfcd33f4a2338db0765d851a50583d410bacf055cfd0b"
+SRC_URI[sha256sum] =
"e36ea877a6370810b97d84cf8f72b1e4ed205149ab3ac8232d44c850f38a2859"
UPSTREAM_CHECK_URI = "https://taglib.org/;
UPSTREAM_CHECK_REGEX = "taglib-(?P\d+(\.\d+)+)\.tar"
--
2.42.0
0001-taglib-upgrade-1.13.1-2.0.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1859 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (913 cached, 1 parsed). 1857 targets, 35
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-64 sysroot...done.
Removing 1 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-fb7e1e9ea6ec97d9a42acdbc79899575ed077326"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:fb7e1e9ea6ec97d9a42acdbc79899575ed077326"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 110 Local 101 Mirrors 0 Missed 9 Current 198 (91% match,
97% complete)
done.
NOTE: Executing Tasks
NOTE: Running setscene task 208 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/zlib/zlib_1.3.bb:do_create_spdx_setscene)
NOTE: Running setscene task 215 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/taglib/taglib_2.0.bb:do_populate_lic_setscene)
NOTE: Running setscene task 217 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/taglib/taglib_2.0.bb:do_deploy_source_date_epoch_setscene)
NOTE: recipe zlib-1.3-r0: task do_create_spdx_setscene: Started
NOTE: recipe taglib-2.0-r0: task do_populate_lic_setscene: Started
NOTE: recipe taglib-2.0-r0: task do_deploy_source_date_epoch_setscene: Started
NOTE: recipe zlib-1.3-r0: task do_create_spdx_setscene: Succeeded
NOTE: Running setscene task 277 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/gcc/gcc-runtime_13.2.bb:do_create_spdx_setscene)
NOTE: recipe taglib-2.0-r0: task do_populate_lic_setscene: Succeeded
NOTE: recipe taglib-2.0-r0: task do_deploy_source_date_epoch_setscene: Succeeded
NOTE: Running setscene task 278 of 308
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/taglib/taglib_2.0.bb:do_recipe_qa_setscene)
NOTE: recipe taglib-2.0-r0: task do_recipe_qa_setscene: Started
NOTE: recipe gcc-runtime-13.2.0-r0: task do_create_spdx_setscene: Started
NOTE: recipe taglib-2.0-r0: task do_recipe_qa_setscene: Succeeded
NOTE: Running task 681 of 925
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/taglib/taglib_2.0.bb:do_fetch)
NOTE: recipe gcc-runtime-13.2.0-r0: task do_create_spdx_setscene: Succeeded
NOTE: Running setscene task 282 of 308
[OE-core] [AUH] gtk+3: upgrading to 3.24.41 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.41* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe gtk+3 failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-6f7ab7398d4773f464cdc5b662b6141792984ab1" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:6f7ab7398d4773f464cdc5b662b6141792984ab1" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-6f7ab7398d4773f464cdc5b662b6141792984ab1" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:6f7ab7398d4773f464cdc5b662b6141792984ab1" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% complete) done. 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 DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 98% |### | 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://ftp.gnome.org/pub/gnome/sources/gtk+/3.24/gtk+-3.24.41.tar.xz... INFO: Rebasing devtool onto 4c350503f7bd87531cb99db78b967fcd4d1622e7 WARNING: Command 'git rebase 4c350503f7bd87531cb99db78b967fcd4d1622e7' failed: Auto-merging gdk/gdkdisplay.c Auto-merging gdk/gdkgl.c CONFLICT (content): Merge conflict in gdk/gdkgl.c Auto-merging gdk/gdkglcontext.c Auto-merging gdk/gdkwindow.c Auto-merging 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/workspace/sources/gtk+3 INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/gtk+3/gtk+3_3.24.41.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 (#195628): https://lists.openembedded.org/g/openembedded-core/message/195628 Mute This Topic: https://lists.openembedded.org/mt/104377523/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] attr: upgrading to 2.5.2 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *attr* to *2.5.2* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade attr -V 2.5.2 NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-ed5bd9174e7053dc753389e9c2836d812889b40d" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:ed5bd9174e7053dc753389e9c2836d812889b40d" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 12 Local 9 Mirrors 0 Missed 3 Current 17 (75% match, 89% complete) Removing 1 stale sstate objects for arch x86_64...done. NOTE: Executing Tasks Log data follows: | DEBUG: Executing python function do_unpack | DEBUG: Executing python function base_do_unpack | NOTE: Unpacking /srv/autobuilder/autobuilder.yocto.io/current_sources/attr-2.5.1.tar.gz to /home/pokybuild/yocto-worker/auh/build/build/tmp/work/core2-64-poky-linux/attr/2.5.1/devtooltmp-qih0zc9g/workdir/ | DEBUG: Searching for run-ptest in paths: | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/poky | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/poky | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/poky | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/qemux86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/qemux86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/qemux86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/qemuall | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/qemuall | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/qemuall | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/x86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/x86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/x86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/ | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/ | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/ | DEBUG: Using /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/run-ptest for run-ptest | NOTE: Unpacking /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/run-ptest to /home/pokybuild/yocto-worker/auh/build/build/tmp/work/core2-64-poky-linux/attr/2.5.1/devtooltmp-qih0zc9g/workdir/ | DEBUG: Searching for 0001-attr.c-Include-libgen.h-for-posix-version-of-basenam.patch in paths: | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/poky | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/poky | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/poky | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/qemux86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/qemux86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/qemux86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/qemuall | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/qemuall | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/qemuall | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/x86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/x86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/x86-64 | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr-2.5.1/ | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/ | /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/files/ | DEBUG: Using /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/0001-attr.c-Include-libgen.h-for-posix-version-of-basenam.patch for 0001-attr.c-Include-libgen.h-for-posix-version-of-basenam.patch | NOTE: Unpacking /home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr/0001-attr.c-Include-libgen.h-for-posix-version-of-basenam.patch
[OE-core] [AUH] shaderc: upgrading to 2023.8 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *shaderc* to *2023.8* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe shaderc failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-f4c72618967f22102f0185f6fd8177726fc4582d" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:f4c72618967f22102f0185f6fd8177726fc4582d" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 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 e6edd6d48fa5bdd9d176794c6810fae7f8e938e1 WARNING: Command 'git rebase e6edd6d48fa5bdd9d176794c6810fae7f8e938e1' failed: Auto-merging glslc/CMakeLists.txt CONFLICT (content): Merge conflict in glslc/CMakeLists.txt Auto-merging libshaderc/CMakeLists.txt CONFLICT (content): Merge conflict in libshaderc/CMakeLists.txt Auto-merging libshaderc/README.md CONFLICT (content): Merge conflict in libshaderc/README.md Auto-merging libshaderc_util/CMakeLists.txt CONFLICT (content): Merge conflict in libshaderc_util/CMakeLists.txt You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/shaderc INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/shaderc/shaderc_2023.8.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 (#195632): https://lists.openembedded.org/g/openembedded-core/message/195632 Mute This Topic: https://lists.openembedded.org/mt/104377527/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] spirv-headers: upgrading to 1.3.275.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *spirv-headers* to *1.3.275.0*
has Succeeded.
Next steps:
- apply the patch: git am
0001-spirv-headers-upgrade-1.3.268.0-1.3.275.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
-- >8 --
>From 5223ea58521260be6e52e9923a4920a0fcd53500 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 13:44:22 +
Subject: [PATCH] spirv-headers: upgrade 1.3.268.0 -> 1.3.275.0
---
.../{spirv-headers_1.3.268.0.bb => spirv-headers_1.3.275.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/spir/{spirv-headers_1.3.268.0.bb =>
spirv-headers_1.3.275.0.bb} (93%)
diff --git a/meta/recipes-graphics/spir/spirv-headers_1.3.268.0.bb
b/meta/recipes-graphics/spir/spirv-headers_1.3.275.0.bb
similarity index 93%
rename from meta/recipes-graphics/spir/spirv-headers_1.3.268.0.bb
rename to meta/recipes-graphics/spir/spirv-headers_1.3.275.0.bb
index 7045f70473..598a8fc209 100644
--- a/meta/recipes-graphics/spir/spirv-headers_1.3.268.0.bb
+++ b/meta/recipes-graphics/spir/spirv-headers_1.3.275.0.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "https://www.khronos.org/registry/spir-v;
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c938b85bceb8fb26c1a807f28a52ae2d"
-SRCREV = "e867c06631767a2d96424cbec530f9ee5e78180f"
+SRCREV = "1c6bb2743599e6eb6f37b2969acc0aef812e32e3"
SRC_URI =
"git://github.com/KhronosGroup/SPIRV-Headers;protocol=https;branch=main"
PE = "1"
# These recipes need to be updated in lockstep with each other:
--
2.42.0
0001-spirv-headers-upgrade-1.3.268.0-1.3.275.0.patch
Description: Binary data
packages/core2-64-poky-linux/spirv-headers: PKGV changed from 1.3.268.0
[default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers: PV changed from "1.3.268.0" to
"1.3.275.0"
packages/core2-64-poky-linux/spirv-headers/spirv-headers-dbg: PKGV changed from
1.3.268.0 [default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers/spirv-headers-dbg: PV changed from
"1.3.268.0" to "1.3.275.0"
packages/core2-64-poky-linux/spirv-headers/spirv-headers-dev: PKGSIZE changed
from 2902543 to 2907497 (+0%)
packages/core2-64-poky-linux/spirv-headers/spirv-headers-dev: PKGV changed from
1.3.268.0 [default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers/spirv-headers-dev: PV changed from
"1.3.268.0" to "1.3.275.0"
packages/core2-64-poky-linux/spirv-headers/spirv-headers-doc: PKGV changed from
1.3.268.0 [default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers/spirv-headers-doc: PV changed from
"1.3.268.0" to "1.3.275.0"
packages/core2-64-poky-linux/spirv-headers/spirv-headers-locale: PKGV changed
from 1.3.268.0 [default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers/spirv-headers-locale: PV changed
from "1.3.268.0" to "1.3.275.0"
packages/core2-64-poky-linux/spirv-headers/spirv-headers-src: PKGV changed from
1.3.268.0 [default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers/spirv-headers-src: PV changed from
"1.3.268.0" to "1.3.275.0"
packages/core2-64-poky-linux/spirv-headers/spirv-headers-staticdev: PKGV
changed from 1.3.268.0 [default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers/spirv-headers-staticdev: PV changed
from "1.3.268.0" to "1.3.275.0"
packages/core2-64-poky-linux/spirv-headers/spirv-headers: PKGV changed from
1.3.268.0 [default] to 1.3.275.0 [default]
packages/core2-64-poky-linux/spirv-headers/spirv-headers: PV changed from
"1.3.268.0" to "1.3.275.0"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195636):
https://lists.openembedded.org/g/openembedded-core/message/195636
Mute This Topic: https://lists.openembedded.org/mt/104377531/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] waffle: upgrading to 1.8.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *waffle* to *1.8.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe waffle failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-edb87566e68e64da977d30b725ca6191b1e57314" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:edb87566e68e64da977d30b725ca6191b1e57314" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 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 580b912a30085528886603942c100c7b309b3bdb WARNING: Command 'git rebase 580b912a30085528886603942c100c7b309b3bdb' failed: Auto-merging meson.build CONFLICT (content): Merge conflict in meson.build Auto-merging src/waffle/meson.build CONFLICT (content): Merge conflict in src/waffle/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/workspace/sources/waffle INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/waffle/waffle_1.8.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 (#195627): https://lists.openembedded.org/g/openembedded-core/message/195627 Mute This Topic: https://lists.openembedded.org/mt/104377522/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 257 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffoscope* to *257* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-253-257.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
-- >8 --
>From 9f648f95d8f8ff4583cf79a079a78e40aab97af2 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 16:50:33 +
Subject: [PATCH] diffoscope: upgrade 253 -> 257
---
.../diffoscope/{diffoscope_253.bb => diffoscope_257.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/diffoscope/{diffoscope_253.bb =>
diffoscope_257.bb} (93%)
diff --git a/meta/recipes-support/diffoscope/diffoscope_253.bb
b/meta/recipes-support/diffoscope/diffoscope_257.bb
similarity index 93%
rename from meta/recipes-support/diffoscope/diffoscope_253.bb
rename to meta/recipes-support/diffoscope/diffoscope_257.bb
index a1fc63efc3..91e6719a58 100644
--- a/meta/recipes-support/diffoscope/diffoscope_253.bb
+++ b/meta/recipes-support/diffoscope/diffoscope_257.bb
@@ -12,7 +12,7 @@ PYPI_PACKAGE = "diffoscope"
inherit pypi setuptools3
-SRC_URI[sha256sum] =
"ca3d826b691f4998d6de28a016b3555d56a7283b97ad92944ce643ea6e7eb614"
+SRC_URI[sha256sum] =
"1bceee9ca6fe2d7faa2f21daf9f4a83d83e1f1be8b682691b1d985d5e870077f"
RDEPENDS:${PN} += "\
binutils \
--
2.42.0
packages/core2-64-poky-linux/diffoscope/diffoscope-dbg: PV changed from "253"
to "257"
packages/core2-64-poky-linux/diffoscope/diffoscope-dbg: PKGV changed from 253
[default] to 257 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-dev: PV changed from "253"
to "257"
packages/core2-64-poky-linux/diffoscope/diffoscope-dev: PKGV changed from 253
[default] to 257 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-doc: PV changed from "253"
to "257"
packages/core2-64-poky-linux/diffoscope/diffoscope-doc: PKGV changed from 253
[default] to 257 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-locale: PV changed from
"253" to "257"
packages/core2-64-poky-linux/diffoscope/diffoscope-locale: PKGV changed from
253 [default] to 257 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-src: PV changed from "253"
to "257"
packages/core2-64-poky-linux/diffoscope/diffoscope-src: PKGV changed from 253
[default] to 257 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-staticdev: PV changed from
"253" to "257"
packages/core2-64-poky-linux/diffoscope/diffoscope-staticdev: PKGV changed from
253 [default] to 257 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope: FILELIST: directory renamed
/usr/lib/python3.12/site-packages/diffoscope-253.dist-info ->
/usr/lib/python3.12/site-packages/diffoscope-257.dist-info, added
"/usr/lib/python3.12/site-packages/diffoscope/comparators/xar.py
/usr/lib/python3.12/site-packages/diffoscope/comparators/__pycache__/xar.cpython-312.pyc"
packages/core2-64-poky-linux/diffoscope/diffoscope: PKGSIZE changed from
1333244 to 1350079 (+1%)
packages/core2-64-poky-linux/diffoscope/diffoscope: PV changed from "253" to
"257"
packages/core2-64-poky-linux/diffoscope/diffoscope: PKGV changed from 253
[default] to 257 [default]
packages/core2-64-poky-linux/diffoscope: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/d/diffoscope/diffoscope-253.tar.gz;downloadfilename=diffoscope-253.tar.gz;
to
"https://files.pythonhosted.org/packages/source/d/diffoscope/diffoscope-257.tar.gz;downloadfilename=diffoscope-257.tar.gz;
packages/core2-64-poky-linux/diffoscope: PV changed from "253" to "257"
packages/core2-64-poky-linux/diffoscope: PKGV changed from 253 [default] to 257
[default]
Changes to packages/core2-64-poky-linux/diffoscope (sysroot):
/usr/lib/python3.12/site-packages/diffoscope-253.dist-info moved to
/usr/lib/python3.12/site-packages/diffoscope-257.dist-info
/usr/lib/python3.12/site-packages/diffoscope/comparators/__pycache__/xar.cpython-312.pyc
was added
/usr/lib/python3.12/site-packages/diffoscope/comparators/xar.py was added
0001-diffoscope-upgrade-253-257.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (0
[OE-core] [AUH] shadow: upgrading to 4.15.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *shadow* to *4.15.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade shadow -V 4.15.0 NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1858 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-751ddabb138ced670a1c043db561c90a4bfc3c4b" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:751ddabb138ced670a1c043db561c90a4bfc3c4b" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1858 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-751ddabb138ced670a1c043db561c90a4bfc3c4b" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:751ddabb138ced670a1c043db561c90a4bfc3c4b" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks WARNING: Failed to fetch URL https://github.com/shadow-maint/shadow/releases/download/4.15.0/shadow-4.15.0.tar.gz, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds NOTE: The errors for this build are stored in /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215114727.txt You can send the errors to a reports server by running: send-error-report /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215114727.txt [-s server] NOTE: The contents of these logs will be posted in public if you use the above command with the default server. Please ensure you remove any identifying or proprietary information when prompted before sending. 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: Fetching https://github.com/shadow-maint/shadow/releases/download/4.15.0/shadow-4.15.0.tar.gz... ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export SSL_CERT_FILE="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; export GIT_SSL_CAINFO="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; 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/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/scripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-jx3wh1jq/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-jx3wh1jq/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-jx3wh1jq/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipe tool-jx3wh1jq/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-jx3wh1jq/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-jx3wh1jq/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/hosttools"; export HOME="/home/pokybuild";
[OE-core] [AUH] vulkan-tools: upgrading to 1.3.275.0 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.3.275.0*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-vulkan-tools-upgrade-1.3.268.0-1.3.275.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
-- >8 --
>From cd9ae068f0ca8b1c8bf6e015b775480b8ee019ba Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:03:06 +
Subject: [PATCH] vulkan-tools: upgrade 1.3.268.0 -> 1.3.275.0
---
.../{vulkan-tools_1.3.268.0.bb => vulkan-tools_1.3.275.0.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/vulkan/{vulkan-tools_1.3.268.0.bb =>
vulkan-tools_1.3.275.0.bb} (96%)
diff --git a/meta/recipes-graphics/vulkan/vulkan-tools_1.3.268.0.bb
b/meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb
similarity index 96%
rename from meta/recipes-graphics/vulkan/vulkan-tools_1.3.268.0.bb
rename to meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb
index 78bd9b0e04..b4bd23b837 100644
--- a/meta/recipes-graphics/vulkan/vulkan-tools_1.3.268.0.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb
@@ -7,7 +7,7 @@ SECTION = "libs"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57"
SRC_URI =
"git://github.com/KhronosGroup/Vulkan-Tools.git;branch=main;protocol=https"
-SRCREV = "1532001f7edae559af1988293eec90bc5e2607d5"
+SRCREV = "c86d42cf9eb620eeac377e3bff46ae342c5cd664"
S = "${WORKDIR}/git"
--
2.42.0
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1857 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (913 cached, 1 parsed). 1857 targets, 35
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-64 sysroot...done.
Removing 1 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-0e1df9287d168ef55fe497e165c5ed88cd8839c8"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:0e1df9287d168ef55fe497e165c5ed88cd8839c8"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 209 Local 200 Mirrors 0 Missed 9 Current 357 (95% match,
98% complete)
done.
NOTE: Executing Tasks
NOTE: Running setscene task 433 of 566
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb:do_populate_lic_setscene)
NOTE: Running setscene task 435 of 566
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb:do_deploy_source_date_epoch_setscene)
NOTE: recipe vulkan-tools-1.3.275.0-r0: task do_populate_lic_setscene: Started
NOTE: recipe vulkan-tools-1.3.275.0-r0: task
do_deploy_source_date_epoch_setscene: Started
NOTE: recipe vulkan-tools-1.3.275.0-r0: task
do_deploy_source_date_epoch_setscene: Succeeded
NOTE: recipe vulkan-tools-1.3.275.0-r0: task do_populate_lic_setscene: Succeeded
NOTE: Running setscene task 566 of 566
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb:do_recipe_qa_setscene)
NOTE: recipe vulkan-tools-1.3.275.0-r0: task do_recipe_qa_setscene: Started
NOTE: recipe vulkan-tools-1.3.275.0-r0: task do_recipe_qa_setscene: Succeeded
NOTE: Setscene tasks completed
NOTE: Running task 1575 of 1595
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb:do_fetch)
NOTE: recipe vulkan-tools-1.3.275.0-r0: task do_fetch: Started
NOTE: recipe vulkan-tools-1.3.275.0-r0: task do_fetch: Succeeded
NOTE: Running task 1576 of 1595
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/vulkan/vulkan-tools_1.3.275.0.bb:do_unpack)
NOTE: Running task 1577 of 1595
[OE-core] [AUH] enchant2: upgrading to 2.6.7 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *enchant2* to *2.6.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-enchant2-upgrade-2.6.5-2.6.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
-- >8 --
>From 5a0f2f6fc1ad0d455afaa1d066944946cbfc558f Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 16:53:36 +
Subject: [PATCH] enchant2: upgrade 2.6.5 -> 2.6.7
---
.../enchant/{enchant2_2.6.5.bb => enchant2_2.6.7.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/enchant/{enchant2_2.6.5.bb => enchant2_2.6.7.bb}
(91%)
diff --git a/meta/recipes-support/enchant/enchant2_2.6.5.bb
b/meta/recipes-support/enchant/enchant2_2.6.7.bb
similarity index 91%
rename from meta/recipes-support/enchant/enchant2_2.6.5.bb
rename to meta/recipes-support/enchant/enchant2_2.6.7.bb
index 1d5c716bab..b31bdc422b 100644
--- a/meta/recipes-support/enchant/enchant2_2.6.5.bb
+++ b/meta/recipes-support/enchant/enchant2_2.6.7.bb
@@ -12,7 +12,7 @@ DEPENDS = "glib-2.0 groff-native"
inherit autotools pkgconfig github-releases
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/enchant-${PV}.tar.gz"
-SRC_URI[sha256sum] =
"9e8fd28cb65a7b6da3545878a5c2f52a15f03c04933a5ff48db89fe86845728e"
+SRC_URI[sha256sum] =
"a1c2e5b59acca000bbfb24810af4a1165733d407f2154786588e076c8cd57bfc"
GITHUB_BASE_URI = "https://github.com/AbiWord/enchant/releases;
--
2.42.0
0001-enchant2-upgrade-2.6.5-2.6.7.patch
Description: Binary data
packages/core2-64-poky-linux/enchant2/enchant2-dbg: PKGSIZE changed from 167072
to 168080 (+1%)
packages/core2-64-poky-linux/enchant2/enchant2-dbg: PV changed from "2.6.5" to
"2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2-dbg: FILELIST: removed
"/usr/lib/.debug/libenchant-2.so.2.6.5", added
"/usr/lib/.debug/libenchant-2.so.2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2-dbg: PKGV changed from 2.6.5
[default] to 2.6.7 [default]
packages/core2-64-poky-linux/enchant2/enchant2-dev: PV changed from "2.6.5" to
"2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2-dev: PKGV changed from 2.6.5
[default] to 2.6.7 [default]
packages/core2-64-poky-linux/enchant2/enchant2-doc: PKGSIZE changed from 21756
to 22056 (+1%)
packages/core2-64-poky-linux/enchant2/enchant2-doc: PV changed from "2.6.5" to
"2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2-doc: PKGV changed from 2.6.5
[default] to 2.6.7 [default]
packages/core2-64-poky-linux/enchant2/enchant2-locale: PV changed from "2.6.5"
to "2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2-locale: PKGV changed from 2.6.5
[default] to 2.6.7 [default]
packages/core2-64-poky-linux/enchant2/enchant2-src: PKGSIZE changed from 168111
to 168424 (+0%)
packages/core2-64-poky-linux/enchant2/enchant2-src: PV changed from "2.6.5" to
"2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2-src: PKGV changed from 2.6.5
[default] to 2.6.7 [default]
packages/core2-64-poky-linux/enchant2/enchant2-staticdev: PV changed from
"2.6.5" to "2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2-staticdev: PKGV changed from
2.6.5 [default] to 2.6.7 [default]
packages/core2-64-poky-linux/enchant2/enchant2: PV changed from "2.6.5" to
"2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2: FILELIST: removed
"/usr/lib/libenchant-2.so.2.6.5", added "/usr/lib/libenchant-2.so.2.6.7"
packages/core2-64-poky-linux/enchant2/enchant2: PKGV changed from 2.6.5
[default] to 2.6.7 [default]
packages/core2-64-poky-linux/enchant2: PV changed from "2.6.5" to "2.6.7"
packages/core2-64-poky-linux/enchant2: SRC_URI changed from
"https://github.com/AbiWord/enchant/releases/download/v2.6.5/enchant-2.6.5.tar.gz;
to
"https://github.com/AbiWord/enchant/releases/download/v2.6.7/enchant-2.6.7.tar.gz;
packages/core2-64-poky-linux/enchant2: PKGV changed from 2.6.5 [default] to
2.6.7 [default]
Changes to packages/core2-64-poky-linux/enchant2 (sysroot):
/usr/lib/libenchant-2.so.2 changed symlink target from libenchant-2.so.2.6.5
to libenchant-2.so.2.6.7
/usr/lib/libenchant-2.so changed symlink target from libenchant-2.so.2.6.5 to
libenchant-2.so.2.6.7
/usr/lib/libenchant-2.so.2.6.5 moved to /usr/lib/libenchant-2.so.2.6.7
packages/core2-64-poky-linux/enchant2/enchant2:
[OE-core] [AUH] libxext: upgrading to 1.3.6 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxext* to *1.3.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxext-upgrade-1.3.5-1.3.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
-- >8 --
>From 09370674ea3c75e4afc72ab91495d3276e43b5fa Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:20:55 +
Subject: [PATCH] libxext: upgrade 1.3.5 -> 1.3.6
---
.../xorg-lib/{libxext_1.3.5.bb => libxext_1.3.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xorg-lib/{libxext_1.3.5.bb => libxext_1.3.6.bb}
(89%)
diff --git a/meta/recipes-graphics/xorg-lib/libxext_1.3.5.bb
b/meta/recipes-graphics/xorg-lib/libxext_1.3.6.bb
similarity index 89%
rename from meta/recipes-graphics/xorg-lib/libxext_1.3.5.bb
rename to meta/recipes-graphics/xorg-lib/libxext_1.3.6.bb
index 7d0597ef1d..275926a885 100644
--- a/meta/recipes-graphics/xorg-lib/libxext_1.3.5.bb
+++ b/meta/recipes-graphics/xorg-lib/libxext_1.3.6.bb
@@ -21,4 +21,4 @@ PE = "1"
XORG_PN = "libXext"
BBCLASSEXTEND = "native nativesdk"
-SRC_URI[sha256sum] =
"db14c0c895c57ea33a8559de8cb2b93dc76c42ea4a39e294d175938a133d7bca"
+SRC_URI[sha256sum] =
"edb59fa23994e405fdc5b400afdf5820ae6160b94f35e3dc3da4457a16e89753"
--
2.42.0
0001-libxext-upgrade-1.3.5-1.3.6.patch
Description: Binary data
packages/core2-64-poky-linux/libxext: PKGV changed from 1.3.5 [default] to
1.3.6 [default]
packages/core2-64-poky-linux/libxext: PV changed from "1.3.5" to "1.3.6"
packages/core2-64-poky-linux/libxext: SRC_URI changed from
"https://www.x.org/releases//individual/lib/libXext-1.3.5.tar.xz; to
"https://www.x.org/releases//individual/lib/libXext-1.3.6.tar.xz;
packages/core2-64-poky-linux/libxext/libxext-dbg: PKGSIZE changed from 545592
to 545304 (-0%)
packages/core2-64-poky-linux/libxext/libxext-dbg: PKGV changed from 1.3.5
[default] to 1.3.6 [default]
packages/core2-64-poky-linux/libxext/libxext-dbg: PV changed from "1.3.5" to
"1.3.6"
packages/core2-64-poky-linux/libxext/libxext-dev: PKGSIZE changed from 55350 to
55438 (+0%)
packages/core2-64-poky-linux/libxext/libxext-dev: PKGV changed from 1.3.5
[default] to 1.3.6 [default]
packages/core2-64-poky-linux/libxext/libxext-dev: PV changed from "1.3.5" to
"1.3.6"
packages/core2-64-poky-linux/libxext/libxext-doc: PKGV changed from 1.3.5
[default] to 1.3.6 [default]
packages/core2-64-poky-linux/libxext/libxext-doc: PV changed from "1.3.5" to
"1.3.6"
packages/core2-64-poky-linux/libxext/libxext-locale: PKGV changed from 1.3.5
[default] to 1.3.6 [default]
packages/core2-64-poky-linux/libxext/libxext-locale: PV changed from "1.3.5" to
"1.3.6"
packages/core2-64-poky-linux/libxext/libxext-src: PKGSIZE changed from 240214
to 240335 (+0%)
packages/core2-64-poky-linux/libxext/libxext-src: PKGV changed from 1.3.5
[default] to 1.3.6 [default]
packages/core2-64-poky-linux/libxext/libxext-src: PV changed from "1.3.5" to
"1.3.6"
packages/core2-64-poky-linux/libxext/libxext-staticdev: PKGV changed from 1.3.5
[default] to 1.3.6 [default]
packages/core2-64-poky-linux/libxext/libxext-staticdev: PV changed from "1.3.5"
to "1.3.6"
packages/core2-64-poky-linux/libxext/libxext: PKGV changed from 1.3.5 [default]
to 1.3.6 [default]
packages/core2-64-poky-linux/libxext/libxext: PV changed from "1.3.5" to "1.3.6"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195650):
https://lists.openembedded.org/g/openembedded-core/message/195650
Mute This Topic: https://lists.openembedded.org/mt/104377545/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] ed: upgrading to 1.20.1 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ed* to *1.20.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-ed-upgrade-1.20-1.20.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
-- >8 --
>From ecda16fb2a196fb8d2d1255614bc01f2bd5aae8a Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:32:24 +
Subject: [PATCH] ed: upgrade 1.20 -> 1.20.1
---
meta/recipes-extended/ed/{ed_1.20.bb => ed_1.20.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/ed/{ed_1.20.bb => ed_1.20.1.bb} (93%)
diff --git a/meta/recipes-extended/ed/ed_1.20.bb
b/meta/recipes-extended/ed/ed_1.20.1.bb
similarity index 93%
rename from meta/recipes-extended/ed/ed_1.20.bb
rename to meta/recipes-extended/ed/ed_1.20.1.bb
index 07b04b..9ae53002c3 100644
--- a/meta/recipes-extended/ed/ed_1.20.bb
+++ b/meta/recipes-extended/ed/ed_1.20.1.bb
@@ -19,7 +19,7 @@ bindir = "${base_bindir}"
SRC_URI = "${GNU_MIRROR}/ed/${BP}.tar.lz"
UPSTREAM_CHECK_URI = "${GNU_MIRROR}/ed/"
-SRC_URI[sha256sum] =
"c6030defe6ae172f1687906d7354054c75a6a9130af319d4e73c50a91959c5a6"
+SRC_URI[sha256sum] =
"b1a463b297a141f9876c4b1fcd01477f645cded92168090e9a35db2af4babbca"
EXTRA_OEMAKE = "-e MAKEFLAGS="
--
2.42.0
packages/core2-64-poky-linux/ed/ed-dbg: PKGSIZE changed from 160840 to 158552
(-1%)
packages/core2-64-poky-linux/ed/ed-dbg: PKGV changed from 1.20 [default] to
1.20.1 [default]
packages/core2-64-poky-linux/ed/ed-dbg: PV changed from "1.20" to "1.20.1"
packages/core2-64-poky-linux/ed/ed-dev: PKGV changed from 1.20 [default] to
1.20.1 [default]
packages/core2-64-poky-linux/ed/ed-dev: PV changed from "1.20" to "1.20.1"
packages/core2-64-poky-linux/ed/ed-doc: PKGSIZE changed from 73783 to 73729
(-0%)
packages/core2-64-poky-linux/ed/ed-doc: PKGV changed from 1.20 [default] to
1.20.1 [default]
packages/core2-64-poky-linux/ed/ed-doc: PV changed from "1.20" to "1.20.1"
packages/core2-64-poky-linux/ed/ed-locale: PKGV changed from 1.20 [default] to
1.20.1 [default]
packages/core2-64-poky-linux/ed/ed-locale: PV changed from "1.20" to "1.20.1"
packages/core2-64-poky-linux/ed/ed-src: PKGSIZE changed from 114489 to 113135
(-1%)
packages/core2-64-poky-linux/ed/ed-src: PKGV changed from 1.20 [default] to
1.20.1 [default]
packages/core2-64-poky-linux/ed/ed-src: PV changed from "1.20" to "1.20.1"
packages/core2-64-poky-linux/ed/ed-staticdev: PKGV changed from 1.20 [default]
to 1.20.1 [default]
packages/core2-64-poky-linux/ed/ed-staticdev: PV changed from "1.20" to "1.20.1"
packages/core2-64-poky-linux/ed/ed: PKGV changed from 1.20 [default] to 1.20.1
[default]
packages/core2-64-poky-linux/ed/ed: PV changed from "1.20" to "1.20.1"
packages/core2-64-poky-linux/ed: PKGV changed from 1.20 [default] to 1.20.1
[default]
packages/core2-64-poky-linux/ed: SRC_URI changed from
"https://ftp.gnu.org/gnu/ed/ed-1.20.tar.lz; to
"https://ftp.gnu.org/gnu/ed/ed-1.20.1.tar.lz;
packages/core2-64-poky-linux/ed: PV changed from "1.20" to "1.20.1"
0001-ed-upgrade-1.20-1.20.1.patch
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195616):
https://lists.openembedded.org/g/openembedded-core/message/195616
Mute This Topic: https://lists.openembedded.org/mt/104377511/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] mesa: upgrading to 24.0.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mesa* to *24.0.1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe mesa failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-0def6ed6ff94e4545283e372a6af4601c5dc6bc0" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:0def6ed6ff94e4545283e372a6af4601c5dc6bc0" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-0def6ed6ff94e4545283e372a6af4601c5dc6bc0" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:0def6ed6ff94e4545283e372a6af4601c5dc6bc0" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% complete) done. 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 DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 4% |# | ETA: 0:00:04 Adding changed files: 8% |### | ETA: 0:00:03 Adding changed files: 12% || ETA: 0:00:02 Adding changed files: 16% |## | ETA: 0:00:02 Adding changed files: 20% |### | ETA: 0:00:02 Adding changed files: 25% |# | ETA: 0:00:02 Adding changed files: 29% |## | ETA: 0:00:02 Adding changed files: 33% || ETA: 0:00:02 Adding changed files: 37% |# | ETA: 0:00:01 Adding changed files: 41% |### | ETA: 0:00:01 Adding changed files: 45% || ETA: 0:00:01 Adding changed files: 50% |## | ETA: 0:00:01 Adding changed files: 54% |### | ETA: 0:00:01 Adding changed files: 58% |# | ETA: 0:00:01 Adding changed files: 62% |## | ETA: 0:00:01 Adding changed files: 66% || ETA: 0:00:01 Adding changed files: 70% |# | ETA: 0:00:00 Adding changed files: 75% |### | ETA: 0:00:00 Adding changed files: 79% || ETA: 0:00:00 Adding changed files: 83% |## | ETA: 0:00:00 Adding changed files: 87% |### | ETA: 0:00:00 Adding changed files: 91% |# | ETA: 0:00:00 Adding changed files: 95% |## | ETA: 0:00:00 Adding changed files: 100% || Time: 0:00:02 INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Fetching https://mesa.freedesktop.org/archive/mesa-24.0.1.tar.xz... INFO: Rebasing devtool onto e9aca2e06463bedd9d7738db08641ed7eb700c6b WARNING: Command 'git rebase e9aca2e06463bedd9d7738db08641ed7eb700c6b' failed:
[OE-core] [AUH] tzdata: upgrading to 2024a FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *tzdata* to *2024a* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-tzdata-upgrade-2023d-2024a.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
-- >8 --
>From 7e0f7ccbca4d1f85f7fc0fa5063aea207530875e Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:56:38 +
Subject: [PATCH] tzdata: upgrade 2023d -> 2024a
---
meta/recipes-extended/timezone/timezone.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-extended/timezone/timezone.inc
b/meta/recipes-extended/timezone/timezone.inc
index 2774e5e730..54a9219089 100644
--- a/meta/recipes-extended/timezone/timezone.inc
+++ b/meta/recipes-extended/timezone/timezone.inc
@@ -6,7 +6,7 @@ SECTION = "base"
LICENSE = "PD & BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
-PV = "2023d"
+PV = "2024a"
SRC_URI ="
http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode;subdir=tz
\
http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;subdir=tz
\
@@ -16,5 +16,5 @@ S = "${WORKDIR}/tz"
UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones;
-SRC_URI[tzcode.sha256sum] =
"e9a5f9e118886d2de92b62bb05510a28cc6c058d791c93bd6b84d3292c3c161e"
+SRC_URI[tzcode.sha256sum] =
"80072894adff5a458f1d143e16e4ca1d8b2a122c9c5399da482cb68cba6a1ff8"
SRC_URI[tzdata.sha256sum] =
"dbca21970b0a8b8c0ceceec1d7b91fa903be0f6eca5ae732b5329672232a08f3"
--
2.42.0
0001-tzdata-upgrade-2023d-2024a.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1859 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (912 cached, 2 parsed). 1857 targets, 35
skipped, 0 masked, 0 errors.
Removing 1 recipes from the allarch sysroot...done.
Removing 1 recipes from the qemux86_64 sysroot...done.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-10da8d65d44f1ceaf102c554873262b13d3ae452"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:10da8d65d44f1ceaf102c554873262b13d3ae452"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 75 Local 59 Mirrors 0 Missed 16 Current 142 (78% match,
92% complete)
done.
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 450 of 705
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/timezone/tzdata.bb:do_recipe_qa)
NOTE: Running task 451 of 705
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/timezone/tzcode-native.bb:do_recipe_qa)
NOTE: recipe tzcode-native-2024a-r0: task do_recipe_qa: Started
NOTE: recipe tzdata-2024a-r0: task do_recipe_qa: Started
NOTE: recipe tzcode-native-2024a-r0: task do_recipe_qa: Succeeded
NOTE: Task
/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/timezone/tzcode-native.bb:do_recipe_qa
unihash changed to
d9c5c551b309658b3d62f514d031007a97bfd2fa06f3bac63d0e1294a4602ccf
NOTE: recipe tzdata-2024a-r0: task do_recipe_qa: Succeeded
NOTE: Task
/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/timezone/tzdata.bb:do_recipe_qa
unihash changed to
2d69c41568c9028ab0e8e4dd3bbfa5c10aa517b6e53e4b82f2d1171aef71b408
NOTE: Setscene tasks completed
NOTE: Running task 675 of 705
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/timezone/tzdata.bb:do_fetch)
NOTE: Running task 676 of 705
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/timezone/tzcode-native.bb:do_fetch)
NOTE: recipe tzcode-native-2024a-r0: task do_fetch: Started
NOTE: recipe tzdata-2024a-r0: task do_fetch: Started
WARNING: tzcode-native-2024a-r0 do_fetch: Checksum mismatch for
[OE-core] [AUH] piglit: upgrading to b9374d2c59e665bf60950af898003ed17bf98370 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *piglit* to *b9374d2c59e665bf60950af898003ed17bf98370* has Succeeded. Next steps: - apply the patch: git am 0001-piglit-upgrade-to-latest-revision.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 -- >8 -- >From 9f89e8b52ed0e65998ca757129afa32dda02ef1a Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Thu, 15 Feb 2024 13:41:36 + Subject: [PATCH] piglit: upgrade to latest revision --- ...-tests-Fix-narrowing-errors-seen-with-clang.patch | 6 ++ ...tils-Include-libgen.h-on-musl-linux-systems.patch | 6 ++ ...ke-use-proper-WAYLAND_INCLUDE_DIRS-variable.patch | 8 +++- ...l-piglit-shader.c-do-not-hardcode-build-pat.patch | 12 +--- meta/recipes-graphics/piglit/piglit_git.bb | 2 +- 5 files changed, 13 insertions(+), 21 deletions(-) diff --git a/meta/recipes-graphics/piglit/piglit/0001-tests-Fix-narrowing-errors-seen-with-clang.patch b/meta/recipes-graphics/piglit/piglit/0001-tests-Fix-narrowing-errors-seen-with-clang.patch index b1bb00e052..9786247ae8 100644 --- a/meta/recipes-graphics/piglit/piglit/0001-tests-Fix-narrowing-errors-seen-with-clang.patch +++ b/meta/recipes-graphics/piglit/piglit/0001-tests-Fix-narrowing-errors-seen-with-clang.patch @@ -1,4 +1,4 @@ -From cd38c91e8c743bfc1841bcdd08e1ab18bf22f0e1 Mon Sep 17 00:00:00 2001 +From 69d9143e9e76101bf6d32636983277f0cb496ab5 Mon Sep 17 00:00:00 2001 From: Khem Raj Date: Wed, 3 May 2023 21:59:43 -0700 Subject: [PATCH] tests: Fix narrowing errors seen with clang @@ -9,6 +9,7 @@ zer list [-Wc++11-narrowing] Upstream-Status: Submitted [https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/807] Signed-off-by: Khem Raj + --- .../spec/ext_framebuffer_multisample/draw-buffers-common.cpp | 4 ++-- tests/util/piglit-test-pattern.cpp| 4 ++-- @@ -48,6 +49,3 @@ index 43d451d6a..52ee94457 100644 glClearBufferuiv(GL_COLOR, 0, clear_color); break; } --- -2.40.1 - diff --git a/meta/recipes-graphics/piglit/piglit/0001-utils-Include-libgen.h-on-musl-linux-systems.patch b/meta/recipes-graphics/piglit/piglit/0001-utils-Include-libgen.h-on-musl-linux-systems.patch index 35e919e552..66691ed9d4 100644 --- a/meta/recipes-graphics/piglit/piglit/0001-utils-Include-libgen.h-on-musl-linux-systems.patch +++ b/meta/recipes-graphics/piglit/piglit/0001-utils-Include-libgen.h-on-musl-linux-systems.patch @@ -1,4 +1,4 @@ -From 232a67b651ccb415b7d4d47584613359b7ebd920 Mon Sep 17 00:00:00 2001 +From 5fda54a757eefebc87bec21d70bd57645fb29eac Mon Sep 17 00:00:00 2001 From: Khem Raj Date: Tue, 13 Feb 2024 08:53:37 -0800 Subject: [PATCH] utils: Include libgen.h on musl/linux systems @@ -9,6 +9,7 @@ allow to include libgen.h on non-glibc based linux systems Upstream-Status: Submitted [https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/877] Signed-off-by: Khem Raj + --- tests/util/piglit-util.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) @@ -26,6 +27,3 @@ index 4d3606c70..fdfd903b3 100644 # include "libgen.h" // for basename #elif defined(_MSC_VER) --- -2.43.1 - diff --git a/meta/recipes-graphics/piglit/piglit/0002-cmake-use-proper-WAYLAND_INCLUDE_DIRS-variable.patch b/meta/recipes-graphics/piglit/piglit/0002-cmake-use-proper-WAYLAND_INCLUDE_DIRS-variable.patch index 5d6ec368ba..b50f095f3d 100644 --- a/meta/recipes-graphics/piglit/piglit/0002-cmake-use-proper-WAYLAND_INCLUDE_DIRS-variable.patch +++ b/meta/recipes-graphics/piglit/piglit/0002-cmake-use-proper-WAYLAND_INCLUDE_DIRS-variable.patch @@ -1,4 +1,4 @@ -From 3bf1beee1ddd19bc536ff2856e04ac269d43daa2 Mon Sep 17 00:00:00 2001 +From 56ebccb7431dd32774604e1097de38fbfdb38b20 Mon Sep 17 00:00:00 2001 From: Pascal Bach Date: Thu, 4 Oct 2018 14:43:17 +0200 Subject: [PATCH] cmake: use proper WAYLAND_INCLUDE_DIRS variable @@ -10,12 +10,13 @@ when cross compiling. Signed-off-by: Pascal Bach Upstream-Status: Submitted [pig...@lists.freedesktop.org] + --- tests/util/CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/util/CMakeLists.txt b/tests/util/CMakeLists.txt -index a5f080156..a303a9f58 100644 +index 1714ab41f..3b67aa7da
[OE-core] [AUH] vulkan-samples: upgrading to 04091a428b76f234d47b8ce72cb4f3693e2fbcd1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *04091a428b76f234d47b8ce72cb4f3693e2fbcd1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe vulkan-samples failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-0e1df9287d168ef55fe497e165c5ed88cd8839c8" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:0e1df9287d168ef55fe497e165c5ed88cd8839c8" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 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 04091a428b76f234d47b8ce72cb4f3693e2fbcd1 WARNING: Command 'git rebase 04091a428b76f234d47b8ce72cb4f3693e2fbcd1' failed: Failed to merge submodule third_party/spdlog CONFLICT (submodule): Merge conflict in third_party/spdlog Recursive merging with submodules currently only supports trivial cases. Please manually handle the merging of each conflicted submodule. This can be accomplished with the following steps: - go to submodule (third_party/spdlog), and either merge commit 9a531463 or update to an existing commit which has merged those changes - come back to superproject and run: git add third_party/spdlog to record the above merge or update - resolve any other conflicts in the superproject - commit the resulting index in the superproject You will need to resolve conflicts in order to complete the upgrade. INFO: Rebasing devtool onto f55f67fd3c5a9f9208ab9e646b02ff11917fa4ce INFO: Rebasing devtool onto 437e135dbd94eb65b45533d9ce8ee28b5bd37b6d INFO: Rebasing devtool onto 4861c3db1ca50eb5f5767d95d1cd1bacb98ac8a5 INFO: Rebasing devtool onto a6c48261d4fb62b232c46277acbcc3d14d5b7e14 INFO: Rebasing devtool onto 8f470597d625ae28758c16b4293dd42d63e8a83a INFO: Rebasing devtool onto fce2abd01ce21063bd25ba67c9318be83bf48813 INFO: Rebasing devtool onto 6d41bb9c557c5a0eec61ffba1f775dc5f717a8f7 INFO: Rebasing devtool onto 5a0c3d0b527bea96154998f29177f3b449cebd3a INFO: Rebasing devtool onto c23a19c26fa9cc778f755e76799f0cafdcb5a13b INFO: Rebasing devtool onto 6a38a0694b4d73d22c5d1e22f865d03545e808ea INFO: Rebasing devtool onto 5e3df1cf058074145c6bc71e3e7cfc4314796b5c INFO: Rebasing devtool onto 7e635fca68d014934b4af8a1cf874f63989352b7 WARNING: Command 'git rebase 7e635fca68d014934b4af8a1cf874f63989352b7' failed: Auto-merging include/spdlog/details/os.h CONFLICT (content): Merge conflict in include/spdlog/details/os.h You will need to resolve conflicts in order to complete the upgrade. INFO: Rebasing devtool onto 7512345f61e5f9b543ebb87df678f3fe7735587b INFO: Rebasing devtool onto 2c2908f50515dcd939f24be261c3ccbcd277bb49 INFO: Rebasing devtool onto c0d0251e2c7f2273a894aa1b125af9313a88eae4 INFO: Rebasing devtool onto f9921aefddee2437cc2e3303d3175bd8ef23e22c INFO: Rebasing devtool onto 623a5504a9eb9314d9c18ba36d64ef3208c215a1 INFO: Rebasing devtool onto 4f51aac14f65629dfe83702b806f740dbd7bd701 INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/vulkan-samples INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/vulkan-samples/vulkan-samples_git.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 (#195612): https://lists.openembedded.org/g/openembedded-core/message/195612 Mute This Topic: https://lists.openembedded.org/mt/104377507/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] xkbcomp: upgrading to 1.4.7 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xkbcomp* to *1.4.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xkbcomp-upgrade-1.4.6-1.4.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
-- >8 --
>From bc3e08fb71000586d950dd15549ca5e64ec12dbe Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:14:22 +
Subject: [PATCH] xkbcomp: upgrade 1.4.6 -> 1.4.7
---
.../xorg-app/{xkbcomp_1.4.6.bb => xkbcomp_1.4.7.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xorg-app/{xkbcomp_1.4.6.bb => xkbcomp_1.4.7.bb}
(86%)
diff --git a/meta/recipes-graphics/xorg-app/xkbcomp_1.4.6.bb
b/meta/recipes-graphics/xorg-app/xkbcomp_1.4.7.bb
similarity index 86%
rename from meta/recipes-graphics/xorg-app/xkbcomp_1.4.6.bb
rename to meta/recipes-graphics/xorg-app/xkbcomp_1.4.7.bb
index 44f462f523..f259f33dd8 100644
--- a/meta/recipes-graphics/xorg-app/xkbcomp_1.4.6.bb
+++ b/meta/recipes-graphics/xorg-app/xkbcomp_1.4.7.bb
@@ -16,4 +16,4 @@ BBCLASSEXTEND = "native"
EXTRA_OECONF += "--disable-selective-werror"
SRC_URI_EXT = "xz"
-SRC_URI[sha256sum] =
"fa50d611ef41e034487af7bd8d8c718df53dd18002f591cca16b0384afc58e98"
+SRC_URI[sha256sum] =
"0a288114e5f44e31987042c79aecff1ffad53a8154b8ec971c24a69a80f81f77"
--
2.42.0
packages/core2-64-poky-linux/xkbcomp: PV changed from "1.4.6" to "1.4.7"
packages/core2-64-poky-linux/xkbcomp: SRC_URI changed from
"https://www.x.org/releases//individual/app/xkbcomp-1.4.6.tar.xz; to
"https://www.x.org/releases//individual/app/xkbcomp-1.4.7.tar.xz;
packages/core2-64-poky-linux/xkbcomp: PKGV changed from 1.4.6 [default] to
1.4.7 [default]
packages/core2-64-poky-linux/xkbcomp/xkbcomp-dbg: PV changed from "1.4.6" to
"1.4.7"
packages/core2-64-poky-linux/xkbcomp/xkbcomp-dbg: PKGSIZE changed from 572512
to 564176 (-1%)
packages/core2-64-poky-linux/xkbcomp/xkbcomp-dbg: PKGV changed from 1.4.6
[default] to 1.4.7 [default]
packages/core2-64-poky-linux/xkbcomp/xkbcomp-dev: PV changed from "1.4.6" to
"1.4.7"
packages/core2-64-poky-linux/xkbcomp/xkbcomp-dev: PKGV changed from 1.4.6
[default] to 1.4.7 [default]
packages/core2-64-poky-linux/xkbcomp/xkbcomp-doc: PV changed from "1.4.6" to
"1.4.7"
packages/core2-64-poky-linux/xkbcomp/xkbcomp-doc: PKGV changed from 1.4.6
[default] to 1.4.7 [default]
packages/core2-64-poky-linux/xkbcomp/xkbcomp-locale: PV changed from "1.4.6" to
"1.4.7"
packages/core2-64-poky-linux/xkbcomp/xkbcomp-locale: PKGV changed from 1.4.6
[default] to 1.4.7 [default]
packages/core2-64-poky-linux/xkbcomp/xkbcomp-src: PV changed from "1.4.6" to
"1.4.7"
packages/core2-64-poky-linux/xkbcomp/xkbcomp-src: PKGSIZE changed from 702720
to 709044 (+1%)
packages/core2-64-poky-linux/xkbcomp/xkbcomp-src: PKGV changed from 1.4.6
[default] to 1.4.7 [default]
packages/core2-64-poky-linux/xkbcomp/xkbcomp-staticdev: PV changed from "1.4.6"
to "1.4.7"
packages/core2-64-poky-linux/xkbcomp/xkbcomp-staticdev: PKGV changed from 1.4.6
[default] to 1.4.7 [default]
packages/core2-64-poky-linux/xkbcomp/xkbcomp: PV changed from "1.4.6" to "1.4.7"
packages/core2-64-poky-linux/xkbcomp/xkbcomp: PKGSIZE changed from 216904 to
212800 (-2%)
packages/core2-64-poky-linux/xkbcomp/xkbcomp: PKGV changed from 1.4.6 [default]
to 1.4.7 [default]
0001-xkbcomp-upgrade-1.4.6-1.4.7.patch
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195662):
https://lists.openembedded.org/g/openembedded-core/message/195662
Mute This Topic: https://lists.openembedded.org/mt/104377557/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] go-helloworld: upgrading to 32022caedd6a177a7717aa8680cbe179e1045935 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-helloworld* to *32022caedd6a177a7717aa8680cbe179e1045935* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade go-helloworld -S 32022caedd6a177a7717aa8680cbe179e1045935 NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-f7c43ef513e7232ac77b0e4be16e650a71aa97d7" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:f7c43ef513e7232ac77b0e4be16e650a71aa97d7" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 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... ERROR: Execution of 'git checkout 32022caedd6a177a7717aa8680cbe179e1045935' failed with exit code 128: fatal: reference is not a tree: 32022caedd6a177a7717aa8680cbe179e1045935 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 (#195615): https://lists.openembedded.org/g/openembedded-core/message/195615 Mute This Topic: https://lists.openembedded.org/mt/104377510/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] libxvmc: upgrading to 1.0.14 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxvmc* to *1.0.14* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxvmc-upgrade-1.0.13-1.0.14.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
-- >8 --
>From 71e8029c69803a0bdda1ebd51fe00ae49ce6b9cc Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:25:55 +
Subject: [PATCH] libxvmc: upgrade 1.0.13 -> 1.0.14
---
.../xorg-lib/{libxvmc_1.0.13.bb => libxvmc_1.0.14.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xorg-lib/{libxvmc_1.0.13.bb => libxvmc_1.0.14.bb}
(85%)
diff --git a/meta/recipes-graphics/xorg-lib/libxvmc_1.0.13.bb
b/meta/recipes-graphics/xorg-lib/libxvmc_1.0.14.bb
similarity index 85%
rename from meta/recipes-graphics/xorg-lib/libxvmc_1.0.13.bb
rename to meta/recipes-graphics/xorg-lib/libxvmc_1.0.14.bb
index d6d009831a..af18afc62d 100644
--- a/meta/recipes-graphics/xorg-lib/libxvmc_1.0.13.bb
+++ b/meta/recipes-graphics/xorg-lib/libxvmc_1.0.14.bb
@@ -16,4 +16,4 @@ PE = "1"
XORG_PN = "libXvMC"
-SRC_URI[sha256sum] =
"0a9ebe6dea7888a747e5aca1b891d53cd7d3a5f141a9645f77d9b6a12cee657c"
+SRC_URI[sha256sum] =
"e4be9eb6b6bafdbbf81f47f7163047215376e45e2dc786d0ea6181c930725ed9"
--
2.42.0
packages/core2-64-poky-linux/libxvmc: PV changed from "1.0.13" to "1.0.14"
packages/core2-64-poky-linux/libxvmc: SRC_URI changed from
"https://www.x.org/releases//individual/lib/libXvMC-1.0.13.tar.xz; to
"https://www.x.org/releases//individual/lib/libXvMC-1.0.14.tar.xz;
packages/core2-64-poky-linux/libxvmc: PKGV changed from 1.0.13 [default] to
1.0.14 [default]
packages/core2-64-poky-linux/libxvmc/libxvmc-dbg: PKGSIZE changed from 107640
to 107024 (-1%)
packages/core2-64-poky-linux/libxvmc/libxvmc-dbg: PV changed from "1.0.13" to
"1.0.14"
packages/core2-64-poky-linux/libxvmc/libxvmc-dbg: PKGV changed from 1.0.13
[default] to 1.0.14 [default]
packages/core2-64-poky-linux/libxvmc/libxvmc-dev: PKGSIZE changed from 10306 to
12319 (+20%)
packages/core2-64-poky-linux/libxvmc/libxvmc-dev: PV changed from "1.0.13" to
"1.0.14"
packages/core2-64-poky-linux/libxvmc/libxvmc-dev: PKGV changed from 1.0.13
[default] to 1.0.14 [default]
packages/core2-64-poky-linux/libxvmc/libxvmc-doc: PV changed from "1.0.13" to
"1.0.14"
packages/core2-64-poky-linux/libxvmc/libxvmc-doc: PKGV changed from 1.0.13
[default] to 1.0.14 [default]
packages/core2-64-poky-linux/libxvmc/libxvmc-locale: PV changed from "1.0.13"
to "1.0.14"
packages/core2-64-poky-linux/libxvmc/libxvmc-locale: PKGV changed from 1.0.13
[default] to 1.0.14 [default]
packages/core2-64-poky-linux/libxvmc/libxvmc-src: PKGSIZE changed from 46269 to
51706 (+12%)
packages/core2-64-poky-linux/libxvmc/libxvmc-src: PV changed from "1.0.13" to
"1.0.14"
packages/core2-64-poky-linux/libxvmc/libxvmc-src: PKGV changed from 1.0.13
[default] to 1.0.14 [default]
packages/core2-64-poky-linux/libxvmc/libxvmc-staticdev: PV changed from
"1.0.13" to "1.0.14"
packages/core2-64-poky-linux/libxvmc/libxvmc-staticdev: PKGV changed from
1.0.13 [default] to 1.0.14 [default]
packages/core2-64-poky-linux/libxvmc/libxvmc: PV changed from "1.0.13" to
"1.0.14"
packages/core2-64-poky-linux/libxvmc/libxvmc: PKGV changed from 1.0.13
[default] to 1.0.14 [default]
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (0 cached, 914 parsed). 1858 targets, 46
skipped, 0 masked, 0 errors.
Removing 17 recipes from the core2-64 sysroot...done.
Removing 16 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux-musl"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-cdc5770d68a73f065718b6c9133285bb8087b912"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:cdc5770d68a73f065718b6c9133285bb8087b912"
Initialising tasks...NOTE: The
[OE-core] [AUH] libstd-rs: upgrading to 1.76.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.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libstd-rs failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1859 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 3 seconds Loading cache...done. Loaded 1859 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% complete) done. 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 DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% || ETA: 0:05:55 Adding changed files: 0% || ETA: 0:04:37 Adding changed files: 0% || ETA: 0:04:58 Adding changed files: 1% || ETA: 0:04:46 Adding changed files: 1% || ETA: 0:04:42 Adding changed files: 1% || ETA: 0:04:21 Adding changed files: 1% || ETA: 0:04:16 Adding changed files: 2% || ETA: 0:04:11 Adding changed files: 2% || ETA: 0:04:03 Adding changed files: 2% || ETA: 0:04:01 Adding changed files: 3% |# | ETA: 0:04:04 Adding changed files: 3% |# | ETA: 0:04:06 Adding changed files: 3% |# | ETA: 0:04:03 Adding changed files: 3% |# | ETA: 0:04:02 Adding changed files: 4% |# | ETA: 0:03:59 Adding changed files: 4% |# | ETA: 0:03:58 Adding changed files: 4% |# | ETA: 0:03:58 Adding changed files: 4% |# | ETA: 0:03:58 Adding changed files: 5% |# | ETA: 0:03:56 Adding changed files: 5% |# | ETA: 0:03:55 Adding changed files: 5% |## | ETA: 0:03:55 Adding changed files: 6% |## | ETA: 0:03:54 Adding changed files: 6% |## | ETA: 0:03:52 Adding changed files: 6% |## | ETA: 0:03:50 Adding changed files: 6% |## | ETA: 0:03:48 Adding changed files: 7% |## | ETA: 0:03:46 Adding changed files: 7% |## | ETA: 0:03:45 Adding changed files: 7% |## | ETA: 0:03:45 Adding changed files: 8% |##
[OE-core] [AUH] minicom: upgrading to 2.9 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *minicom* to *2.9* has
Succeeded.
Next steps:
- apply the patch: git am 0001-minicom-upgrade-2.8-2.9.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
-- >8 --
>From efe093f026a8c40bae31f7b17a318b066881fa93 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:45:08 +
Subject: [PATCH] minicom: upgrade 2.8 -> 2.9
---
...ix-minicom-h-v-return-value-is-not-0.patch | 33 ---
.../minicom/allow.to.disable.lockdev.patch| 30 -
.../{minicom_2.8.bb => minicom_2.9.bb}| 7 ++--
3 files changed, 2 insertions(+), 68 deletions(-)
delete mode 100644
meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
delete mode 100644
meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
rename meta/recipes-extended/minicom/{minicom_2.8.bb => minicom_2.9.bb} (80%)
diff --git
a/meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
b/meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
deleted file mode 100644
index 9e67126f3e..00
---
a/meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-Exit normally for help/verison options
-
-If -v or -h is used for the help/version information, it is a normal exit
situation,
-not an error condition. Sometimes these are used as a simple operation test of
the
-resulting binary so the exit code does matter.
-
-Signed-off-by: Richard Purdie
-Upstream-Status: Submitted
[https://salsa.debian.org/minicom-team/minicom/-/merge_requests/14]
- src/minicom.c |6 ++
- 1 file changed, 2 insertions(+), 4 deletions(-)
-
-Index: minicom-2.8/src/minicom.c
-===
minicom-2.8.orig/src/minicom.c
-+++ minicom-2.8/src/minicom.c
-@@ -1257,14 +1257,14 @@ int main(int argc, char **argv)
- "modify it under the terms of the GNU General Public
License\n"
- "as published by the Free Software Foundation; either
version\n"
- "2 of the License, or (at your option) any later
version.\n\n"));
-- exit(1);
-+ exit(0);
- break;
- case 's': /* setup mode */
- dosetup = 1;
- break;
- case 'h':
- helpthem();
-- exit(1);
-+ exit(0);
- break;
- case 'p': /* Pseudo terminal to use. */
- if (strncmp(optarg, "/dev/", 5) == 0)
diff --git
a/meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
b/meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
deleted file mode 100644
index 39dc5c0492..00
--- a/meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-configure: Allow lockdev to be disabled
-
-When the pkgconfig dependencies may be present, it is useful to be
-able to explictly disable the lockdev dependency. This adds such an
-option.
-
-Signed-off-by: Martin Jansa
-Signed-off-by: Richard Purdie
-
-Upstream-Status: Submitted
[https://salsa.debian.org/minicom-team/minicom/-/merge_requests/14]
-
-Index: minicom-2.8/configure.ac
-===
minicom-2.8.orig/configure.ac
-+++ minicom-2.8/configure.ac
-@@ -43,7 +43,13 @@ if test "x$enable_socket" = xyes; then
- fi
-
- PKG_PROG_PKG_CONFIG
--if test -n "$PKG_CONFIG"; then
-+
-+AC_ARG_ENABLE([lockdev],
-+AS_HELP_STRING([--enable-lockdev],
-+ [Enable lockdev support (def: enabled)]),
-+[], [enable_lockdev="yes"])
-+
-+if test -n "$PKG_CONFIG" && test "x$enable_lockdev" = xyes; then
- PKG_CHECK_MODULES([LOCKDEV], [lockdev],
AC_DEFINE([HAVE_LOCKDEV],[1],[Define if you have lockdev]),[:])
- fi
-
diff --git a/meta/recipes-extended/minicom/minicom_2.8.bb
b/meta/recipes-extended/minicom/minicom_2.9.bb
similarity index 80%
rename from meta/recipes-extended/minicom/minicom_2.8.bb
rename to meta/recipes-extended/minicom/minicom_2.9.bb
index 2640c6b057..907d5c79c9 100644
---
[OE-core] [AUH] libsecret: upgrading to 0.21.3 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsecret* to *0.21.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsecret-upgrade-0.21.2-0.21.3.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
-- >8 --
>From 8232cfe971ac0e2fad1fb336356022c818f1ebae Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 13:00:25 +
Subject: [PATCH] libsecret: upgrade 0.21.2 -> 0.21.3
---
.../libsecret/{libsecret_0.21.2.bb => libsecret_0.21.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-gnome/libsecret/{libsecret_0.21.2.bb =>
libsecret_0.21.3.bb} (91%)
diff --git a/meta/recipes-gnome/libsecret/libsecret_0.21.2.bb
b/meta/recipes-gnome/libsecret/libsecret_0.21.3.bb
similarity index 91%
rename from meta/recipes-gnome/libsecret/libsecret_0.21.2.bb
rename to meta/recipes-gnome/libsecret/libsecret_0.21.3.bb
index 2d8ea952c5..66c522021e 100644
--- a/meta/recipes-gnome/libsecret/libsecret_0.21.2.bb
+++ b/meta/recipes-gnome/libsecret/libsecret_0.21.3.bb
@@ -13,7 +13,7 @@ inherit gnomebase gi-docgen vala gobject-introspection
manpages
DEPENDS += "glib-2.0 libgcrypt gettext-native"
-SRC_URI[archive.sha256sum] =
"e4a341496a0815e64c8d3b8fabab33d7bae7efdeab77b843669731d5b181dcee"
+SRC_URI[archive.sha256sum] =
"9a3e2571f1048035d80238f52c8760125884a43baf8a580fedb7250c1ad0a9e7"
GTKDOC_MESON_OPTION = 'gtk_doc'
--
2.42.0
packages/core2-64-poky-linux/libsecret: SRC_URI changed from
"https://download.gnome.org/sources//libsecret/0.21/libsecret-0.21.2.tar.xz;name=archive;
to
"https://download.gnome.org/sources//libsecret/0.21/libsecret-0.21.3.tar.xz;name=archive;
packages/core2-64-poky-linux/libsecret: PV changed from "0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret: PKGV changed from 0.21.2 [default] to
0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-dbg: PKGSIZE changed from
1185368 to 1185240 (-0%)
packages/core2-64-poky-linux/libsecret/libsecret-dbg: PV changed from "0.21.2"
to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-dbg: PKGV changed from 0.21.2
[default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-dev: PV changed from "0.21.2"
to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-dev: PKGV changed from 0.21.2
[default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-doc: PV changed from "0.21.2"
to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-doc: PKGV changed from 0.21.2
[default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-ab: PV changed from
"0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-ab: PKGV changed from
0.21.2 [default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-an: PV changed from
"0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-an: PKGV changed from
0.21.2 [default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-ar: PV changed from
"0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-ar: PKGV changed from
0.21.2 [default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-as: PV changed from
"0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-as: PKGV changed from
0.21.2 [default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-be: PV changed from
"0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-be: PKGV changed from
0.21.2 [default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-bg: PV changed from
"0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-bg: PKGV changed from
0.21.2 [default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-bs: PV changed from
"0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-bs: PKGV changed from
0.21.2 [default] to 0.21.3 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-ca+valencia: PV changed
from "0.21.2" to "0.21.3"
packages/core2-64-poky-linux/libsecret/libsecret-locale-ca+valencia: PKGV
changed from 0.21.2 [default]
[OE-core] [AUH] rpm: upgrading to 4.19.1.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rpm* to *4.19.1.1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rpm failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 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 13b4521341781293c41ac898aa9c2d2f6bc1f21d WARNING: Command 'git rebase 13b4521341781293c41ac898aa9c2d2f6bc1f21d' failed: Auto-merging docs/CMakeLists.txt CONFLICT (content): Merge conflict in docs/CMakeLists.txt You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/rpm INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/rpm/rpm_4.19.1.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 (#195611): https://lists.openembedded.org/g/openembedded-core/message/195611 Mute This Topic: https://lists.openembedded.org/mt/104377506/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] texinfo: upgrading to 7.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *texinfo* to *7.1* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade texinfo -V 7.1 NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-10da8d65d44f1ceaf102c554873262b13d3ae452" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:10da8d65d44f1ceaf102c554873262b13d3ae452" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-10da8d65d44f1ceaf102c554873262b13d3ae452" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:10da8d65d44f1ceaf102c554873262b13d3ae452" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 1% || ETA: 0:00:09 Adding changed files: 3% |# | ETA: 0:00:06 Adding changed files: 5% |## | ETA: 0:00:05 Adding changed files: 7% |## | ETA: 0:00:04 Adding changed files: 9% |### | ETA: 0:00:04 Adding changed files: 11% || ETA: 0:00:04 Adding changed files: 13% || ETA: 0:00:04 Adding changed files: 14% |# | ETA: 0:00:04 Adding changed files: 16% |## | ETA: 0:00:03 Adding changed files: 18% |## | ETA: 0:00:03 Adding changed files: 20% |### | ETA: 0:00:03 Adding changed files: 22% || ETA: 0:00:03 INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Fetching https://ftp.gnu.org/gnu/texinfo/texinfo-7.1.tar.gz... ERROR: Execution of 'git add -f -A "tp/tests/customization/res_parser/sectioning_directions_split_chapter/First-node.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/Last-node-no-description.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/Second-node.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/Third-node-unnumbered.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/between-node.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/index.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/numbered-sub.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/numbered-sub2.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/numbered-sub3.html" "tp/tests/customization/res_parser/sectioning_directions_split_chapter/numbered.html" "tp/tests/customization/res_parser/sectioning_directio ns_split_chapter/sectioning.1"
[OE-core] [AUH] mc: upgrading to 4.8.31 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mc* to *4.8.31* has Succeeded.
Next steps:
- apply the patch: git am 0001-mc-upgrade-4.8.30-4.8.31.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
-- >8 --
>From a28fbca6ac2d7d448151d163d5ffc67a5993eacc Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:41:52 +
Subject: [PATCH] mc: upgrade 4.8.30 -> 4.8.31
---
meta/recipes-extended/mc/files/nomandate.patch | 4 ++--
meta/recipes-extended/mc/{mc_4.8.30.bb => mc_4.8.31.bb} | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-extended/mc/{mc_4.8.30.bb => mc_4.8.31.bb} (97%)
diff --git a/meta/recipes-extended/mc/files/nomandate.patch
b/meta/recipes-extended/mc/files/nomandate.patch
index 4ebaaa2fa7..aa88c6c3b6 100644
--- a/meta/recipes-extended/mc/files/nomandate.patch
+++ b/meta/recipes-extended/mc/files/nomandate.patch
@@ -1,4 +1,4 @@
-From 4482ed0b8bd506cc2590ceacfdada6cc34450796 Mon Sep 17 00:00:00 2001
+From 771edfd3d7922b9babb7e38830179b9cd0040957 Mon Sep 17 00:00:00 2001
From: Richard Purdie
Date: Tue, 4 Feb 2020 18:12:15 +
Subject: [PATCH] mc: Fix manpage date indeterminism
@@ -21,7 +21,7 @@ Signed-off-by: Richard Purdie
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/man/date-of-man-include.am b/doc/man/date-of-man-include.am
-index c6b1e69..165a796 100644
+index 96f9f10..d734c5d 100644
--- a/doc/man/date-of-man-include.am
+++ b/doc/man/date-of-man-include.am
@@ -1,5 +1,5 @@
diff --git a/meta/recipes-extended/mc/mc_4.8.30.bb
b/meta/recipes-extended/mc/mc_4.8.31.bb
similarity index 97%
rename from meta/recipes-extended/mc/mc_4.8.30.bb
rename to meta/recipes-extended/mc/mc_4.8.31.bb
index 258ac38e15..b6e5a1f98c 100644
--- a/meta/recipes-extended/mc/mc_4.8.30.bb
+++ b/meta/recipes-extended/mc/mc_4.8.31.bb
@@ -11,7 +11,7 @@ RRECOMMENDS:${PN} = "ncurses-terminfo"
SRC_URI = "http://www.midnight-commander.org/downloads/${BPN}-${PV}.tar.bz2 \
file://nomandate.patch \
"
-SRC_URI[sha256sum] =
"38171f22f889e3030ec9055463d3ecd7843984ab24e6497d8294d1c441a7ddb4"
+SRC_URI[sha256sum] =
"f42f4114ed42f6cf9995f1d896fa6c797ccb36dac57760dda8dd9f78ac462841"
inherit autotools gettext pkgconfig
--
2.42.0
0001-mc-upgrade-4.8.30-4.8.31.patch
Description: Binary data
packages/core2-64-poky-linux/mc: PKGV changed from 4.8.30 [default] to 4.8.31
[default]
packages/core2-64-poky-linux/mc: PV changed from "4.8.30" to "4.8.31"
packages/core2-64-poky-linux/mc: SRC_URI changed from
"http://www.midnight-commander.org/downloads/mc-4.8.30.tar.bz2
file://nomandate.patch" to
"http://www.midnight-commander.org/downloads/mc-4.8.31.tar.bz2
file://nomandate.patch"
packages/core2-64-poky-linux/mc/mc-dbg: PKGV changed from 4.8.30 [default] to
4.8.31 [default]
packages/core2-64-poky-linux/mc/mc-dbg: PV changed from "4.8.30" to "4.8.31"
packages/core2-64-poky-linux/mc/mc-dbg: PKGSIZE changed from 3960400 to 3963096
(+0%)
packages/core2-64-poky-linux/mc/mc-dev: PKGV changed from 4.8.30 [default] to
4.8.31 [default]
packages/core2-64-poky-linux/mc/mc-dev: PV changed from "4.8.30" to "4.8.31"
packages/core2-64-poky-linux/mc/mc-doc: PKGV changed from 4.8.30 [default] to
4.8.31 [default]
packages/core2-64-poky-linux/mc/mc-doc: PV changed from "4.8.30" to "4.8.31"
packages/core2-64-poky-linux/mc/mc-doc: PKGSIZE changed from 1083788 to 1083784
(-0%)
packages/core2-64-poky-linux/mc/mc-fish: PKGV changed from 4.8.30 [default] to
4.8.31 [default]
packages/core2-64-poky-linux/mc/mc-fish: PV changed from "4.8.30" to "4.8.31"
packages/core2-64-poky-linux/mc/mc-fish: FILELIST: removed all items
"/usr/libexec/mc/fish/ln /usr/libexec/mc/fish/unlink /usr/libexec/mc/fish/get
/usr/libexec/mc/fish/fexists /usr/libexec/mc/fish/mkdir
/usr/libexec/mc/fish/rmdir /usr/libexec/mc/fish/ls /usr/libexec/mc/fish/mv
/usr/libexec/mc/fish/hardlink /usr/libexec/mc/fish/append
/usr/libexec/mc/fish/chown /usr/libexec/mc/fish/info /usr/libexec/mc/fish/utime
/usr/libexec/mc/fish/README.fish /usr/libexec/mc/fish/send
/usr/libexec/mc/fish/chmod"
packages/core2-64-poky-linux/mc/mc-fish: PKGSIZE changed from 17132 to 0 (-100%)
packages/core2-64-poky-linux/mc/mc-helpers-perl: PKGV changed from
[OE-core] [AUH] gstreamer1.0-plugins-ugly: upgrading to 1.22.10 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-plugins-ugly* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-plugins-ugly-upgrade-1.22.9-1.22.10.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
-- >8 --
>From 492b9babd905ff987e9525003f0a7a6db19201d5 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 15:10:27 +
Subject: [PATCH] gstreamer1.0-plugins-ugly: upgrade 1.22.9 -> 1.22.10
---
...gins-ugly_1.22.9.bb => gstreamer1.0-plugins-ugly_1.22.10.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-ugly_1.22.9.bb
=> gstreamer1.0-plugins-ugly_1.22.10.bb} (94%)
diff --git
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-ugly_1.22.9.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-ugly_1.22.10.bb
similarity index 94%
rename from
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-ugly_1.22.9.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-ugly_1.22.10.bb
index 722f8e9fe3..7cbbf9fda0 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-ugly_1.22.9.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-ugly_1.22.10.bb
@@ -15,7 +15,7 @@ SRC_URI = " \
https://gstreamer.freedesktop.org/src/gst-plugins-ugly/gst-plugins-ugly-${PV}.tar.xz
\
"
-SRC_URI[sha256sum] =
"0bf685d66015a01dd3fc1671b64a1c8acb321dd9d4ab9e05a29ab19782aa6236"
+SRC_URI[sha256sum] =
"cc80a81a22c0b3b31ab7f1b8bf18dda23c72d2791b86cc6264923a68336329ea"
S = "${WORKDIR}/gst-plugins-ugly-${PV}"
--
2.42.0
0001-gstreamer1.0-plugins-ugly-upgrade-1.22.9-1.22.10.patch
Description: Binary data
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-a52dec:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-a52dec:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-apps:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-apps:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-asf:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-asf:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dbg:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dbg:
PKGSIZE changed from 1192040 to 1192080 (+0%)
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dbg:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dev:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dev:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-doc:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-doc:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dvdlpcmdec:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dvdlpcmdec:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dvdsub:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-dvdsub:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-plugins-ugly/gstreamer1.0-plugins-ugly-glib:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
[OE-core] [AUH] valgrind: upgrading to 3.22.0 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *valgrind* to *3.22.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-valgrind-upgrade-3.21.0-3.22.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
-- >8 --
>From 1d6ffc30eaba8929b1f1ec2a7b828b9b1cd2f6bf Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:30:09 +
Subject: [PATCH] valgrind: upgrade 3.21.0 -> 3.22.0
---
...ions-static-to-avoid-assembler-error.patch | 24 +-
...rn-a-valid-exit_code-from-vg_regtest.patch | 10 +-
.../0001-docs-Disable-manual-validation.patch | 10 +-
...opcode-not-supported-on-mips32-linux.patch | 18 +-
...etting-mcpu-to-cortex-a8-on-arm-arch.patch | 20 +-
...check-tests-Fix-timerfd-syscall-test.patch | 33 +-
...-vgtests-remove-fullpath-after-flags.patch | 10 +-
...eak_cmsg.stderr.exp-adjust-tmp-paths.patch | 8 +-
...inux-seg_override.c-add-missing-incl.patch | 30 --
...ame-_sifields-to-__si_fields-on-musl.patch | 10 +-
...-filter_xml_frames-do-not-filter-usr.patch | 10 +-
...ntext-APIs-are-not-available-on-musl.patch | 14 +-
...-include-directive-path-for-config.h.patch | 10 +-
...est-wrapper-to-support-PTEST-formats.patch | 6 +-
...020-Committing-changes-from-do_patch.patch | 332 ++
...t-for-PPC-instructions-mfatbu-mfatbl.patch | 26 +-
...n-for-targets-which-don-t-support-it.patch | 6 +-
.../valgrind/valgrind/fixed-perl-path.patch | 2 +-
.../valgrind/valgrind/s390x_vec_op_t.patch| 12 +-
...te-march-mcpu-mfpu-for-ARM-test-apps.patch | 10 +-
...-ld-XXX.so-strlen-intercept-optional.patch | 10 +-
...{valgrind_3.21.0.bb => valgrind_3.22.0.bb} | 4 +-
22 files changed, 445 insertions(+), 170 deletions(-)
delete mode 100644
meta/recipes-devtools/valgrind/valgrind/0001-none-tests-x86-linux-seg_override.c-add-missing-incl.patch
create mode 100644
meta/recipes-devtools/valgrind/valgrind/0020-Committing-changes-from-do_patch.patch
rename meta/recipes-devtools/valgrind/{valgrind_3.21.0.bb =>
valgrind_3.22.0.bb} (98%)
diff --git
a/meta/recipes-devtools/valgrind/valgrind/0001-Make-local-functions-static-to-avoid-assembler-error.patch
b/meta/recipes-devtools/valgrind/valgrind/0001-Make-local-functions-static-to-avoid-assembler-error.patch
index 8d2ca5733e..04acfba508 100644
---
a/meta/recipes-devtools/valgrind/valgrind/0001-Make-local-functions-static-to-avoid-assembler-error.patch
+++
b/meta/recipes-devtools/valgrind/valgrind/0001-Make-local-functions-static-to-avoid-assembler-error.patch
@@ -1,4 +1,4 @@
-From 2155c1b2cf00e744e280c493eb74bf457dfcc3b1 Mon Sep 17 00:00:00 2001
+From 5240aa8b254f18661ee0f0093cf215adef27005f Mon Sep 17 00:00:00 2001
From: Randy MacLeod
Date: Sun, 21 Oct 2018 15:09:31 -0400
Subject: [PATCH] Make local functions static to avoid assembler error
@@ -21,12 +21,13 @@ and more importantly also avoid an assembler error:
Upstream-Status: Submitted https://bugs.kde.org/show_bug.cgi?id=400164
Signed-off-by: Randy MacLeod
+
---
helgrind/tests/annotate_hbefore.c | 34 +++
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/helgrind/tests/annotate_hbefore.c
b/helgrind/tests/annotate_hbefore.c
-index e311714f7..f55514e45 100644
+index 259d3b6..8438701 100644
--- a/helgrind/tests/annotate_hbefore.c
+++ b/helgrind/tests/annotate_hbefore.c
@@ -24,7 +24,7 @@ typedef unsigned long int UWord;
@@ -101,7 +102,7 @@ index e311714f7..f55514e45 100644
{
UWord success;
UWord block[3] = { (UWord)addr, nyu, expected};
-@@ -256,7 +256,7 @@ UWord do_acasW ( UWord* addr, UWord expected, UWord nyu )
+@@ -285,7 +285,7 @@ UWord do_acasW ( UWord* addr, UWord expected, UWord nyu )
// mips64
/* return 1 if success, 0 if failure */
@@ -110,7 +111,7 @@ index e311714f7..f55514e45 100644
{
UWord success;
UWord block[3] = { (UWord)addr, nyu, expected};
-@@ -287,7 +287,7 @@ UWord do_acasW ( UWord* addr, UWord expected, UWord nyu )
+@@ -316,7 +316,7 @@ UWord do_acasW ( UWord* addr, UWord expected, UWord nyu )
#endif
@@ -119,7 +120,7 @@ index e311714f7..f55514e45 100644
{
while (1) {
UWord old = *w;
-@@ -301,7 +301,7 @@ void
[OE-core] [AUH] libpam: upgrading to 1.6.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libpam* to *1.6.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libpam failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-751ddabb138ced670a1c043db561c90a4bfc3c4b" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:751ddabb138ced670a1c043db561c90a4bfc3c4b" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-751ddabb138ced670a1c043db561c90a4bfc3c4b" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:751ddabb138ced670a1c043db561c90a4bfc3c4b" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% complete) done. 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 DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 21% |### | ETA: 0:00:00 Adding changed files: 42% |### | ETA: 0:00:00 Adding changed files: 64% |### | ETA: 0:00:00 Adding changed files: 85% |## | 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 https://github.com/linux-pam/linux-pam/releases/download/v1.6.0/Linux-PAM-1.6.0.tar.xz... INFO: Rebasing devtool onto eef6c56fbd3e798f0ffaabdc1d2e77aec9cddef5 WARNING: Command 'git rebase eef6c56fbd3e798f0ffaabdc1d2e77aec9cddef5' failed: Auto-merging examples/tty_conv.c CONFLICT (content): Merge conflict in examples/tty_conv.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/workspace/sources/libpam INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/libpam/libpam_1.6.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 (#195635): https://lists.openembedded.org/g/openembedded-core/message/195635 Mute This Topic: https://lists.openembedded.org/mt/104377530/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
