[OE-core] [PATCH v4] systemd-boot: Add recipe to compile native

2023-12-15 Thread Viswanath Kraleti
systemd-boot native recipe provides ukify tool to build
UKI images for systemd-boot

Signed-off-by: Viswanath Kraleti 
---
 .../systemd/systemd-boot-native_254.4.bb  | 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 meta/recipes-core/systemd/systemd-boot-native_254.4.bb

diff --git a/meta/recipes-core/systemd/systemd-boot-native_254.4.bb 
b/meta/recipes-core/systemd/systemd-boot-native_254.4.bb
new file mode 100644
index 00..73db59b14e
--- /dev/null
+++ b/meta/recipes-core/systemd/systemd-boot-native_254.4.bb
@@ -0,0 +1,15 @@
+require systemd.inc
+
+inherit native
+
+deltask do_configure
+deltask do_compile
+
+do_install () {
+   install -Dm 0755 ${S}/src/ukify/ukify.py ${D}${bindir}/ukify
+}
+addtask install after do_unpack
+
+PACKAGES = "${PN}"
+
+FILES:${PN} = "${bindir}/ukify"
-- 
2.25.1


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



Re: [OE-core][PATCH 1/2] bitbake.conf: Add runtimedir

2023-12-15 Thread Richard Purdie
On Fri, 2023-12-15 at 16:47 -0700, Joshua Watt wrote:
> On Fri, Dec 15, 2023 at 3:47 PM Richard Purdie
>  wrote:
> > 
> > On Fri, 2023-12-15 at 13:34 -0700, Joshua Watt wrote:
> > > Adds the path to the runtime state directory (/run). In particular,
> > > systemd units need to have the correct path to the runtime directory
> > > because RequiresMountsFor doesn't follow symbolic links. This means that
> > > if a unit calls out a directory in /var/run (a symbolic link to /run),
> > > it may actually start before /run is mounted. The fix is to have the
> > > unit specify a directory in /run instead.
> > > 
> > > Signed-off-by: Joshua Watt 
> > > ---
> > >  meta/conf/bitbake.conf | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > > index e7826e7af96..55166d01784 100644
> > > --- a/meta/conf/bitbake.conf
> > > +++ b/meta/conf/bitbake.conf
> > > @@ -31,6 +31,7 @@ export sysconfdir = "${base_prefix}/etc"
> > >  export servicedir = "${base_prefix}/srv"
> > >  export sharedstatedir = "${base_prefix}/com"
> > >  export localstatedir = "${base_prefix}/var"
> > > +export runtimedir = "${base_prefix}/run"
> > >  export datadir = "${prefix}/share"
> > >  export infodir = "${datadir}/info"
> > >  export mandir = "${datadir}/man"
> > 
> > Is there anything currently using that from the shell environment?
> 
> No, nothing is using it today.
> 
> > 
> > Most of this is historical and in many cases not necessary so I'm not
> > sure we want to add to it...
> 
> Ya fair. Are you saying we shouldn't export it, or we shouldn't add it
> at all. I'm fine with either way, the latter just means open-coding it
> as "/run" where necessary (e.g. the rpcbind patch)

I'm just saying not to export it. We have enough of a mess already in
the environment!

Cheers,

Richard

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



Re: [OE-core][PATCH 1/2] bitbake.conf: Add runtimedir

2023-12-15 Thread Joshua Watt
On Fri, Dec 15, 2023 at 3:47 PM Richard Purdie
 wrote:
>
> On Fri, 2023-12-15 at 13:34 -0700, Joshua Watt wrote:
> > Adds the path to the runtime state directory (/run). In particular,
> > systemd units need to have the correct path to the runtime directory
> > because RequiresMountsFor doesn't follow symbolic links. This means that
> > if a unit calls out a directory in /var/run (a symbolic link to /run),
> > it may actually start before /run is mounted. The fix is to have the
> > unit specify a directory in /run instead.
> >
> > Signed-off-by: Joshua Watt 
> > ---
> >  meta/conf/bitbake.conf | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index e7826e7af96..55166d01784 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -31,6 +31,7 @@ export sysconfdir = "${base_prefix}/etc"
> >  export servicedir = "${base_prefix}/srv"
> >  export sharedstatedir = "${base_prefix}/com"
> >  export localstatedir = "${base_prefix}/var"
> > +export runtimedir = "${base_prefix}/run"
> >  export datadir = "${prefix}/share"
> >  export infodir = "${datadir}/info"
> >  export mandir = "${datadir}/man"
>
> Is there anything currently using that from the shell environment?

No, nothing is using it today.

>
> Most of this is historical and in many cases not necessary so I'm not
> sure we want to add to it...

Ya fair. Are you saying we shouldn't export it, or we shouldn't add it
at all. I'm fine with either way, the latter just means open-coding it
as "/run" where necessary (e.g. the rpcbind patch)

>
> Cheers,
>
> Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192552): 
https://lists.openembedded.org/g/openembedded-core/message/192552
Mute This Topic: https://lists.openembedded.org/mt/103198396/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] wic: use E2FSPROGS_FAKE_TIME and hash_seed to generate reproducible ext4 images

2023-12-15 Thread Khem Raj
I think a space is needed at the end of the string. We get into string
concatenation forning different element

| ERROR: _exec_cmd: export
PATH=/mnt/b/yoe/master/build/tmp/work/imx8qm_var_som-yoe-linux/yoe-kiosk-image/1.0/recipe-sysroot-native/sbin:/mnt/b/yoe/master/build/tmp/work/imx8qm_var_som-yoe-linux/yoe-kiosk-image/1.0/recipe-sysroot-native/usr/sbin:/mnt/b/yoe/master/build/tmp/work/imx8qm_var_som-yoe-linux/yoe-kiosk-image/1.0/recipe-sysroot-native/usr/bin:/mnt/b/yoe/master/build/tmp/work/imx8qm_var_som-yoe-linux/yoe-kiosk-image/1.0/recipe-sysroot-native/usr/bin/aarch64-yoe-linux:/mnt/b/yoe/master/build/tmp/work/imx8qm_var_som-yoe-linux/yoe-kiosk-image/1.0/recipe-sysroot-native/bin:/mnt/b/yoe/master/build/tmp/hosttools:$PATH;export
E2FSPROGS_FAKE_TIME=1302044400;Nonemkfs.ext4 -F -i 8192 -E
hash_seed=a97814bc-a858-50e1-bb19-ddcf990c9d6e
/mnt/b/yoe/master/build/tmp/work/imx8qm_var_som-yoe-linux/yoe-kiosk-image/1.0/tmp-wic/rootfs_boot.2.ext4
-L boot -U fc518f34-5d93-4088-98a4-0ec0bff70335 -d
/mnt/b/yoe/master/build/tmp/work/imx8qm_var_som-yoe-linux/yoe-kiosk-image/1.0/tmp-wic/boot.2
returned '127' instead of 0
| output: /bin/sh: line 1: Nonemkfs.ext4: command not found


On Tue, Dec 12, 2023 at 5:56 AM Venkata Pyla
 wrote:
>
> From: venkata pyla 
>
> E2FSPROGS_FAKE_TIME: sets fixed times for the inodes in the file system.
> hash_seed: creates reproducible directory indexes in the file system.
>
> Reference commit in e2fsprogs: e1f7100643a46456be107b33098f6034b0835e6d
>
> Signed-off-by: venkata pyla 
> ---
>  scripts/lib/wic/partition.py | 11 +++
>  1 file changed, 11 insertions(+)
>
> diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic/partition.py
> index b1a2306dd1..8e2273ca2f 100644
> --- a/scripts/lib/wic/partition.py
> +++ b/scripts/lib/wic/partition.py
> @@ -284,6 +284,17 @@ class Partition():
>
>  extraopts = self.mkfs_extraopts or "-F -i 8192"
>
> +if os.getenv('SOURCE_DATE_EPOCH'):
> +sde_time = int(os.getenv('SOURCE_DATE_EPOCH'))
> +pseudo = "export E2FSPROGS_FAKE_TIME=%s;%s" % (sde_time, pseudo)
> +
> +# Set hash_seed to generate deterministic directory indexes
> +namespace = uuid.UUID("e7429877-e7b3-4a68-a5c9-2f2fdf33d460")
> +if self.fsuuid:
> +namespace = uuid.UUID(self.fsuuid)
> +hash_seed = str(uuid.uuid5(namespace, str(sde_time)))
> +extraopts += " -E hash_seed=%s" % hash_seed
> +
>  label_str = ""
>  if self.label:
>  label_str = "-L %s" % self.label
> --
> 2.20.1
>
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192551): 
https://lists.openembedded.org/g/openembedded-core/message/192551
Mute This Topic: https://lists.openembedded.org/mt/103129684/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] ipk: Switch to using zstd compression

2023-12-15 Thread Richard Purdie
On Fri, 2023-12-15 at 13:51 -0700, Joshua Watt wrote:
> 
> @@ -337,7 +335,7 @@ CONVERSION_CMD:lz4 = "lz4 -9 -z -l ${IMAGE_NAME}.${type} 
> ${IMAGE_NAME}.${type}.l
>  CONVERSION_CMD:lzo = "lzop -9 ${IMAGE_NAME}.${type}"
>  CONVERSION_CMD:zip = "zip ${ZIP_COMPRESSION_LEVEL} ${IMAGE_NAME}.${type}.zip 
> ${IMAGE_NAME}.${type}"
>  CONVERSION_CMD:7zip = "7za a -mx=${7ZIP_COMPRESSION_LEVEL} 
> -mm=${7ZIP_COMPRESSION_METHOD} ${IMAGE_NAME}.${type}.${7ZIP_EXTENSION} 
> ${IMAGE_NAME}.${type}"
> -CONVERSION_CMD:zst = "zstd -f -k -T0 -c ${ZSTD_COMPRESSION_LEVEL} 
> ${IMAGE_NAME}.${type} > ${IMAGE_NAME}.${type}.zst"
> +CONVERSION_CMD:zst = "zstd -f -k -c ${ZSTD_DEFAULTS} ${IMAGE_NAME}.${type} > 
> ${IMAGE_NAME}.${type}.zst"
>  CONVERSION_CMD:sum = "sumtool -i ${IMAGE_NAME}.${type} -o 
> ${IMAGE_NAME}.${type}.sum ${JFFS2_SUM_EXTRA_ARGS}"
>  CONVERSION_CMD:md5sum = "md5sum ${IMAGE_NAME}.${type} > 
> ${IMAGE_NAME}.${type}.md5sum"
>  CONVERSION_CMD:sha1sum = "sha1sum ${IMAGE_NAME}.${type} > 
> ${IMAGE_NAME}.${type}.sha1sum"
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 55166d01784..4b1fe28c85a 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -878,6 +878,10 @@ XZ_DEFAULTS[vardepsexclude] += "XZ_MEMLIMIT XZ_THREADS"
>  ZSTD_THREADS ?= "${@oe.utils.cpu_count(at_least=2)}"
>  ZSTD_THREADS[vardepvalue] = "1"
>  
> +ZSTD_COMPRESSION_LEVEL ?= "-3"
> +ZSTD_DEFAULTS ?= "--threads=${ZSTD_THREADS} ${ZSTD_COMPRESSION_LEVEL}"
> +ZSTD_DEFAULTS[vardepsexclude] = "ZSTD_COMPRESSION_LEVEL ZSTD_THREADS"
> +

Threads, sure but the compression level does change the output...

Cheers,

Richard

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



Re: [OE-core][PATCH 1/2] bitbake.conf: Add runtimedir

2023-12-15 Thread Richard Purdie
On Fri, 2023-12-15 at 13:34 -0700, Joshua Watt wrote:
> Adds the path to the runtime state directory (/run). In particular,
> systemd units need to have the correct path to the runtime directory
> because RequiresMountsFor doesn't follow symbolic links. This means that
> if a unit calls out a directory in /var/run (a symbolic link to /run),
> it may actually start before /run is mounted. The fix is to have the
> unit specify a directory in /run instead.
> 
> Signed-off-by: Joshua Watt 
> ---
>  meta/conf/bitbake.conf | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index e7826e7af96..55166d01784 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -31,6 +31,7 @@ export sysconfdir = "${base_prefix}/etc"
>  export servicedir = "${base_prefix}/srv"
>  export sharedstatedir = "${base_prefix}/com"
>  export localstatedir = "${base_prefix}/var"
> +export runtimedir = "${base_prefix}/run"
>  export datadir = "${prefix}/share"
>  export infodir = "${datadir}/info"
>  export mandir = "${datadir}/man"

Is there anything currently using that from the shell environment?

Most of this is historical and in many cases not necessary so I'm not
sure we want to add to it...

Cheers,

Richard

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



Re: [OE-core] [kirkstone][PATCH] externalsrc: Ensure SRCREV is processed before accessing SRC_URI

2023-12-15 Thread Yoann Congal
Le 14/12/2023 à 22:50, Yoann Congal a écrit :
> Le 14/12/2023 à 17:24, Steve Sakoman a écrit :
>> This patch resulted in oe-seftest failures on the autobuilder:
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6322
>>
>> A representative log:
>>
>> https://errors.yoctoproject.org/Errors/Details/746003/
> 
> Thanks Steve!
> 
> Good news, I can reproduce this locally and easily:
>   oe-selftest -r 
> devtool.DevtoolUpdateTests.test_devtool_update_recipe_local_files_subdir -T 
> machine -T toolchain-user -T toolchain-system -j 15
> 
> I've commented this on the bug: 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14918#c7
> 
> I'll look into this.

V2 sent => https://lists.openembedded.org/g/openembedded-core/message/192547
I've tested that it passes my bug reproducer AND all the previously failing 
self-tests (I did not test beyond that though)

>> Steve
>>
>> On Thu, Dec 7, 2023 at 12:33 PM Yoann Congal  wrote:
>>>
>>> Call bb.fetch.get_srcrev() before accessing SRC_URI. Without this new
>>> bb.fetch.get_srcrev() call, SRC_URI might be accessed before SRCREV had
>>> a chance to be processed.
>>>
>>> In master, this is fixed by 
>>> https://git.yoctoproject.org/poky/commit/?id=62afa02d01794376efab75623f42e7e08af08526
>>> However, this commit is not suited for backport since it is quite invasive.
>>> The part of the commit that fix the bug is:
>>> --- a/meta/classes/externalsrc.bbclass
>>> +++ b/meta/classes/externalsrc.bbclass
>>> @@ -63,6 +63,7 @@ python () {
>>>  else:
>>>  d.setVar('B', '${WORKDIR}/${BPN}-${PV}')
>>>
>>> +bb.fetch.get_hashvalue(d)
>>>  local_srcuri = []
>>>  fetch = bb.fetch2.Fetch((d.getVar('SRC_URI') or '').split(), d)
>>>  for url in fetch.urls:
>>>
>>> NB: bb.fetch.get_hashvalue() does not exist in kirkstone but is
>>> equivalent to bb.fetch.get_srcrev().
>>>
>>> Fixes [YOCTO #14918]
>>>
>>> Signed-off-by: Yoann Congal 
>>> Suggested-by: Chris Wyse 
>>> ---
>>> Richard, Steve: This is the commit we discussed at today's bug triage.
>>> ---
>>>  meta/classes/externalsrc.bbclass | 3 +++
>>>  1 file changed, 3 insertions(+)
>>>
>>> diff --git a/meta/classes/externalsrc.bbclass 
>>> b/meta/classes/externalsrc.bbclass
>>> index 97d7379d9f..eb6afca4ab 100644
>>> --- a/meta/classes/externalsrc.bbclass
>>> +++ b/meta/classes/externalsrc.bbclass
>>> @@ -62,6 +62,9 @@ python () {
>>>  else:
>>>  d.setVar('B', '${WORKDIR}/${BPN}-${PV}')
>>>
>>> +# Ensure SRCREV has been processed before accessing SRC_URI
>>> +bb.fetch.get_srcrev(d)
>>> +
>>>  local_srcuri = []
>>>  fetch = bb.fetch2.Fetch((d.getVar('SRC_URI') or '').split(), d)
>>>  for url in fetch.urls:
>>> --
>>> 2.30.2
>>>
> 

-- 
Yoann Congal
Smile ECS - Tech Expert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192548): 
https://lists.openembedded.org/g/openembedded-core/message/192548
Mute This Topic: https://lists.openembedded.org/mt/103044376/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 v2] externalsrc: Ensure SRCREV is processed before accessing SRC_URI

2023-12-15 Thread Yoann Congal
When SRCREV is used, call bb.fetch.get_srcrev() before accessing
SRC_URI. Without this new bb.fetch.get_srcrev() call, SRC_URI might be
accessed before SRCREV had a chance to be processed.

In master, this is fixed by 
https://git.yoctoproject.org/poky/commit/?id=62afa02d01794376efab75623f42e7e08af08526
However, this commit is not suited for backport since it is quite invasive.
The part of the commit that fix the bug is:
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -63,6 +63,7 @@ python () {
 else:
 d.setVar('B', '${WORKDIR}/${BPN}-${PV}')

+bb.fetch.get_hashvalue(d)
 local_srcuri = []
 fetch = bb.fetch2.Fetch((d.getVar('SRC_URI') or '').split(), d)
 for url in fetch.urls:

NB: bb.fetch.get_hashvalue() does not exist in kirkstone but is
equivalent to bb.fetch.get_srcrev().

Fixes [YOCTO #14918]

Signed-off-by: Yoann Congal 
Suggested-by: Chris Wyse 
---
v1->v2:
* Only call get_srcrev() if SRCREV is used (without it the call may
  throw an exception e.g with a file:// SRC_URI)
---
 meta/classes/externalsrc.bbclass | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/classes/externalsrc.bbclass b/meta/classes/externalsrc.bbclass
index 97d7379d9f0..a209730240b 100644
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -62,6 +62,10 @@ python () {
 else:
 d.setVar('B', '${WORKDIR}/${BPN}-${PV}')
 
+if d.getVar('SRCREV', "INVALID") != "INVALID":
+# Ensure SRCREV has been processed before accessing SRC_URI
+bb.fetch.get_srcrev(d)
+
 local_srcuri = []
 fetch = bb.fetch2.Fetch((d.getVar('SRC_URI') or '').split(), d)
 for url in fetch.urls:
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192547): 
https://lists.openembedded.org/g/openembedded-core/message/192547
Mute This Topic: https://lists.openembedded.org/mt/103199241/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] ipk: Switch to using zstd compression

2023-12-15 Thread Joshua Watt
Converts IPK package generation to use zstd instead of xz. zstd has a
much larger compression/speed tradeoff range allowing users to choose
what suits them best. In addition, it support parallel compression for
additional compression speed up.

A new variable called ZSTD_DEFAULTS is provided to set the defaults for
places that want to use zstd for compression; the zst image conversion
command is also modified to use this.

Finally, in order for this to function properly, opkg must include zstd
support, so it is enabled all the time with no PACKAGECONFIG to turn it
off.

Signed-off-by: Joshua Watt 
---
 meta/classes-global/package_ipk.bbclass | 2 +-
 meta/classes-recipe/image_types.bbclass | 4 +---
 meta/conf/bitbake.conf  | 4 
 meta/lib/oe/package_manager/ipk/__init__.py | 4 ++--
 meta/recipes-devtools/opkg/opkg_0.6.2.bb| 6 +++---
 5 files changed, 11 insertions(+), 9 deletions(-)

diff --git a/meta/classes-global/package_ipk.bbclass 
b/meta/classes-global/package_ipk.bbclass
index 71ffdd522ac..025dba49313 100644
--- a/meta/classes-global/package_ipk.bbclass
+++ b/meta/classes-global/package_ipk.bbclass
@@ -15,7 +15,7 @@ IPKGCONF_SDK_TARGET = "${WORKDIR}/opkg-sdk-target.conf"
 PKGWRITEDIRIPK = "${WORKDIR}/deploy-ipks"
 
 # Program to be used to build opkg packages
-OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}"'
+OPKGBUILDCMD ??= 'opkg-build -Z zstd -a "${ZSTD_DEFAULTS}"'
 
 OPKG_ARGS += "--force_postinstall --prefer-arch-to-version"
 OPKG_ARGS += "${@['', 
'--no-install-recommends'][d.getVar("NO_RECOMMENDATIONS") == "1"]}"
diff --git a/meta/classes-recipe/image_types.bbclass 
b/meta/classes-recipe/image_types.bbclass
index d615b41ed1e..3733bdfc20c 100644
--- a/meta/classes-recipe/image_types.bbclass
+++ b/meta/classes-recipe/image_types.bbclass
@@ -63,8 +63,6 @@ ZIP_COMPRESSION_LEVEL ?= "-9"
 7ZIP_COMPRESSION_METHOD ?= "BZip2"
 7ZIP_EXTENSION ?= "7z"
 
-ZSTD_COMPRESSION_LEVEL ?= "-3"
-
 JFFS2_SUM_EXTRA_ARGS ?= ""
 IMAGE_CMD:jffs2 = "mkfs.jffs2 --root=${IMAGE_ROOTFS} --faketime 
--output=${IMGDEPLOYDIR}/${IMAGE_NAME}.jffs2 ${EXTRA_IMAGECMD}"
 
@@ -337,7 +335,7 @@ CONVERSION_CMD:lz4 = "lz4 -9 -z -l ${IMAGE_NAME}.${type} 
${IMAGE_NAME}.${type}.l
 CONVERSION_CMD:lzo = "lzop -9 ${IMAGE_NAME}.${type}"
 CONVERSION_CMD:zip = "zip ${ZIP_COMPRESSION_LEVEL} ${IMAGE_NAME}.${type}.zip 
${IMAGE_NAME}.${type}"
 CONVERSION_CMD:7zip = "7za a -mx=${7ZIP_COMPRESSION_LEVEL} 
-mm=${7ZIP_COMPRESSION_METHOD} ${IMAGE_NAME}.${type}.${7ZIP_EXTENSION} 
${IMAGE_NAME}.${type}"
-CONVERSION_CMD:zst = "zstd -f -k -T0 -c ${ZSTD_COMPRESSION_LEVEL} 
${IMAGE_NAME}.${type} > ${IMAGE_NAME}.${type}.zst"
+CONVERSION_CMD:zst = "zstd -f -k -c ${ZSTD_DEFAULTS} ${IMAGE_NAME}.${type} > 
${IMAGE_NAME}.${type}.zst"
 CONVERSION_CMD:sum = "sumtool -i ${IMAGE_NAME}.${type} -o 
${IMAGE_NAME}.${type}.sum ${JFFS2_SUM_EXTRA_ARGS}"
 CONVERSION_CMD:md5sum = "md5sum ${IMAGE_NAME}.${type} > 
${IMAGE_NAME}.${type}.md5sum"
 CONVERSION_CMD:sha1sum = "sha1sum ${IMAGE_NAME}.${type} > 
${IMAGE_NAME}.${type}.sha1sum"
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 55166d01784..4b1fe28c85a 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -878,6 +878,10 @@ XZ_DEFAULTS[vardepsexclude] += "XZ_MEMLIMIT XZ_THREADS"
 ZSTD_THREADS ?= "${@oe.utils.cpu_count(at_least=2)}"
 ZSTD_THREADS[vardepvalue] = "1"
 
+ZSTD_COMPRESSION_LEVEL ?= "-3"
+ZSTD_DEFAULTS ?= "--threads=${ZSTD_THREADS} ${ZSTD_COMPRESSION_LEVEL}"
+ZSTD_DEFAULTS[vardepsexclude] = "ZSTD_COMPRESSION_LEVEL ZSTD_THREADS"
+
 # Limit the number of threads that OpenMP libraries will use. Otherwise they
 # may fallback to using all CPUs
 export OMP_NUM_THREADS = "${BB_NUMBER_THREADS}"
diff --git a/meta/lib/oe/package_manager/ipk/__init__.py 
b/meta/lib/oe/package_manager/ipk/__init__.py
index e6f9c08e2b6..8fcbad56aab 100644
--- a/meta/lib/oe/package_manager/ipk/__init__.py
+++ b/meta/lib/oe/package_manager/ipk/__init__.py
@@ -133,7 +133,7 @@ class OpkgDpkgPM(PackageManager):
 tmp_dir = tempfile.mkdtemp()
 current_dir = os.getcwd()
 os.chdir(tmp_dir)
-data_tar = 'data.tar.xz'
+data_tar = 'data.tar.zst'
 
 try:
 cmd = [ar_cmd, 'x', pkg_path]
@@ -505,6 +505,6 @@ class OpkgPM(OpkgDpkgPM):
  "trying to extract the package."  % pkg)
 
 tmp_dir = super(OpkgPM, self).extract(pkg, pkg_info)
-bb.utils.remove(os.path.join(tmp_dir, "data.tar.xz"))
+bb.utils.remove(os.path.join(tmp_dir, "data.tar.zst"))
 
 return tmp_dir
diff --git a/meta/recipes-devtools/opkg/opkg_0.6.2.bb 
b/meta/recipes-devtools/opkg/opkg_0.6.2.bb
index b2e675ae48b..71c0b44aed0 100644
--- a/meta/recipes-devtools/opkg/opkg_0.6.2.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.6.2.bb
@@ -8,7 +8,7 @@ LICENSE = "GPL-2.0-or-later"
 LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
 

[OE-core][PATCH 2/2] rpcbind: Specify state directory under /run

2023-12-15 Thread Joshua Watt
The state directory must be correctly specified as under /run because
RequiresMountsFor doesn't follow symbolic links which means the unit may
run before /run is mounted if the default of /var/run/rpcbind is kept

Signed-off-by: Joshua Watt 
---
 meta/recipes-extended/rpcbind/rpcbind_1.2.6.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/rpcbind/rpcbind_1.2.6.bb 
b/meta/recipes-extended/rpcbind/rpcbind_1.2.6.bb
index dd89726afc7..dbd4d32e0a0 100644
--- a/meta/recipes-extended/rpcbind/rpcbind_1.2.6.bb
+++ b/meta/recipes-extended/rpcbind/rpcbind_1.2.6.bb
@@ -40,7 +40,7 @@ PACKAGECONFIG[systemd] = 
"--with-systemdsystemunitdir=${systemd_system_unitdir}/
   systemd \
 "
 
-EXTRA_OECONF += " --enable-warmstarts --with-rpcuser=rpc"
+EXTRA_OECONF += " --enable-warmstarts --with-rpcuser=rpc 
--with-statedir=${runtimedir}/rpcbind"
 
 do_install:append () {
install -d ${D}${sysconfdir}/init.d
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192545): 
https://lists.openembedded.org/g/openembedded-core/message/192545
Mute This Topic: https://lists.openembedded.org/mt/103198397/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] bitbake.conf: Add runtimedir

2023-12-15 Thread Joshua Watt
Adds the path to the runtime state directory (/run). In particular,
systemd units need to have the correct path to the runtime directory
because RequiresMountsFor doesn't follow symbolic links. This means that
if a unit calls out a directory in /var/run (a symbolic link to /run),
it may actually start before /run is mounted. The fix is to have the
unit specify a directory in /run instead.

Signed-off-by: Joshua Watt 
---
 meta/conf/bitbake.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index e7826e7af96..55166d01784 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -31,6 +31,7 @@ export sysconfdir = "${base_prefix}/etc"
 export servicedir = "${base_prefix}/srv"
 export sharedstatedir = "${base_prefix}/com"
 export localstatedir = "${base_prefix}/var"
+export runtimedir = "${base_prefix}/run"
 export datadir = "${prefix}/share"
 export infodir = "${datadir}/info"
 export mandir = "${datadir}/man"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192544): 
https://lists.openembedded.org/g/openembedded-core/message/192544
Mute This Topic: https://lists.openembedded.org/mt/103198396/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] linux-yocto 6.6

2023-12-15 Thread Dmitry Baryshkov
On Thu, 14 Dec 2023 at 22:31, Bruce Ashfield  wrote:
>
> To avoid burning everyone out even more (plus Scarthgap m1 is going to
> build shortly), I'm not sending the new reference kernel updates until
> January.
>
> Even just the send of them and any AB runs will steal time and be a
> distraction over the week between Christmas and New Year.
>
> If you want to use them locally, you can find the queue that has been
> under test for a bit on my poky-contrib branch "zedd/kernel"

This sounds perfect, thanks a lot! (with the hope that we will see 6.6
in Scarthgap).

>
> Bruce
>
> On Tue, Dec 12, 2023 at 5:28 AM Dmitry Baryshkov  wrote:
> >
> > Hello,
> >
> > Granted that 6.5 is declared EOL, is there any timeline for the
> > linux-yocto 6.6 recipe?
> >
> > --
> > With best wishes
> > Dmitry
> >
> > 
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II



-- 
With best wishes
Dmitry

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



Re: [oe-core][PATCH 2/2] appstream: Upgrade 0.16.3 -> 1.0.0

2023-12-15 Thread Markus Volk
This update requires libadwaita 1.4.2 and also some backports for 
gnome-software


On Fri, Dec 15 2023 at 06:30:56 PM +01:00:00, Markus Volk 
 wrote:

- remove backport patch
- update 0001-remove-hardcoded-path.patch
- fix api-documentation

Version 1.0.0
~~
Released: 2023-11-11

Notes:
 * This version breaks API and bumps the SONAME of libappstream!
   Applications using AppStream will have to be ported to the new API.
   The 1.0 release is coinstallable with the stable 0.16.x series.

Features:
 * Autoformat C and C++ sources
 * Remove all deprecated symbols
 * Drop support for many deprecated AppStream XML features
 * Use GPtrArray to expose keywords list
 * Add length argument to raw metadata parsing functions
 * Add component array container class
 * Remove named values for display_length relations
 * Make AsPool only accept/return component boxes
 * Port all API away from per-entity locale overrides
 * Reduce appstream.conf to its essentials, make it work on stateless 
systems

 * Hide search engine details from public API
 * Wrap release entries in AsReleaseList container class
 * Make AsMetadata handle AsReleaseList objects
 * Refactor is_satisfied result into new RelationCheckResult class
 * Add a method to check all relations of a component and get the 
result
 * Add algorithm to score compatibility with a system, add chassis 
templates
 * ascli: Add new check-syscompat command to check chassis 
compatibility

 * Implement environment property for component screenshots
 * Autogenerate translatable DE and gui-environment-style C arrays
 * Expose more advanced markup conversion function, update function 
names

 * Allow BLAKE3 and SHA512 checksums for release artifacts
 * Stop supporting mailto: URLs in  tags
 * validator: Improve API and simplify it
 * validator: Parse XML in pedantic mode when validating
 * validator: Check screenshot environment property
 * validator: Only apply summary-has-dot-suffix check to untranslated 
strings

 * compose: Allow creating metadata with complete URLs and no base URL
 * spdx: Add API to retrieve a translated license name from an SPDX ID
 * qt: Switch to building with Qt6
 * qt: Make it possible to iterate ComponentBox
 * qt: Implement AppStream::ComponentBox::erase
 * qt: Allow concatenating two ComponentBoxes
 * qt: Allow loading Pool asynchronously
 * qt: Use ComponentBox/Releases in Qt bindings as well
 * qt: Add support for the new API to check relation satisfaction
 * qt: Maintenance and namespace fixes, use cPtr() to get C pointers 
everywhere

 * bundle: Add linglong as a new type of bundle
 * Add GUI environment IDs for macOS and Microsoft Windows
 * validator: Check if Release Description is inside description tag
 * validator: Add validation for content_rating
 * Add support for building on Win32
 * win32: change some file/path-related code for portability
 * Implement the developer element for unique developer IDs
 * Implement scaling factor for screenshots
 * component-box: Allow removal of components by-index
 * Implement support for external references and citations
 * Implement usertags for release data as well
 * Move ValueFlags to the context, instead of tieing them to 
components
 * pool: search: Add additional weight for exact substring matches on 
names

 * sysinfo: Add memory size detection support for macOS
 * Add support for Zstd for on-disk data compression
 * utils: Make tar unpacker independent of zstd binary presence
 * Drop Python2 provided tag support
 * data: Add ‘Endless’ to the list of desktops
 * Add NetBSD support

Specification:
 * Drop (most) deprecated information
 * docs: Clarify environment-based screenshot ordering
 * Add new  'snapshot' release kind
 * docs: Build all API documentation with gi-docgen
 * spec: Document the new "developer" element
 * spec: Document the "reference" tag for registry references
 * docs: Add example of YAML for references elements
 * Allow hyphens in the last segment of a component-ID
 * docs: Drop outdated information from l10n quickstart guide

Bugfixes:
 * meson: check for docbook xsl stylesheets
 * Fix tweaking of appstream.pc when building as subproject
 * Fix crash in asc_l10n_search_translations_qt()
 * qt: Make Qt6 dependency a system dependency.
 * meson: do not rely on an exe wrapper
 * meson: do not -I/usr/include when !stemmer
 * meson: Prevent building attempts with MSVC
 * meson: Use an SPDX license indentifier in project(license:)
 * Add meson overrides
 * compose: Set lower-cased CID for synthesized components again
 * compose: Set lower-cased CID in desktop-entry parse function
 * compose: Honor prefix in font search
 * compose: Select the correct default icon glyphs for fonts
 * Don't crash when non-YAML documents are read as YAML
 * Do not override default-priority when parsing multiple metadata 
files

 * Ensure stemmer always has the right locale and token-search works
 * Require a more recent libxmlb to avoid crashes
 * Rename component get_releases to 

[oe-core][PATCH 1/2] libadwaita: update 1.4.0 -> 1.4.2

2023-12-15 Thread Markus Volk
=
Version 1.4.2
=

- Really fix build with libappstream 1.0

=
Version 1.4.1
=

- Fix build with MSVC
- Fix build with libappstream 1.0
- AdwCarousel
  - Fix carousel scroll behavior with page reordering
- AdwComboRow
  - Fix focus when opening the popover
  - Set the correct state on the selected checkmark
- AdwNavigationView
  - Fix a warning message
- AdwTabOverview
  - Allow child focus on out animations
- AdwTabView
  - Keep view alive during ::page-detached
  - Fix crashes when using :pages
- Docs
  - Fix erroneous  use in breakpoints migration guide
- Translation updates
  - Russian
  - Serbian

Signed-off-by: Markus Volk 
---
 .../libadwaita/{libadwaita_1.4.0.bb => libadwaita_1.4.2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-gnome/libadwaita/{libadwaita_1.4.0.bb => 
libadwaita_1.4.2.bb} (88%)

diff --git a/meta/recipes-gnome/libadwaita/libadwaita_1.4.0.bb 
b/meta/recipes-gnome/libadwaita/libadwaita_1.4.2.bb
similarity index 88%
rename from meta/recipes-gnome/libadwaita/libadwaita_1.4.0.bb
rename to meta/recipes-gnome/libadwaita/libadwaita_1.4.2.bb
index cc05756805..edcfba54b6 100644
--- a/meta/recipes-gnome/libadwaita/libadwaita_1.4.0.bb
+++ b/meta/recipes-gnome/libadwaita/libadwaita_1.4.2.bb
@@ -11,7 +11,7 @@ DEPENDS = " \
 
 inherit gnomebase gobject-introspection gi-docgen vala features_check
 
-SRC_URI[archive.sha256sum] = 
"e51a098a54d43568218fc48fcf52e80e36f469b3ce912d8ce9c308a37e9f47c2"
+SRC_URI[archive.sha256sum] = 
"33fa16754e7370c841767298b3ff5f23003ee1d2515cc2ff255e65ef3d4e8713"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 REQUIRED_DISTRO_FEATURES = "opengl"
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192541): 
https://lists.openembedded.org/g/openembedded-core/message/192541
Mute This Topic: https://lists.openembedded.org/mt/103195008/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] appstream: Upgrade 0.16.3 -> 1.0.0

2023-12-15 Thread Markus Volk
- remove backport patch
- update 0001-remove-hardcoded-path.patch
- fix api-documentation

Version 1.0.0
~~
Released: 2023-11-11

Notes:
 * This version breaks API and bumps the SONAME of libappstream!
   Applications using AppStream will have to be ported to the new API.
   The 1.0 release is coinstallable with the stable 0.16.x series.

Features:
 * Autoformat C and C++ sources
 * Remove all deprecated symbols
 * Drop support for many deprecated AppStream XML features
 * Use GPtrArray to expose keywords list
 * Add length argument to raw metadata parsing functions
 * Add component array container class
 * Remove named values for display_length relations
 * Make AsPool only accept/return component boxes
 * Port all API away from per-entity locale overrides
 * Reduce appstream.conf to its essentials, make it work on stateless systems
 * Hide search engine details from public API
 * Wrap release entries in AsReleaseList container class
 * Make AsMetadata handle AsReleaseList objects
 * Refactor is_satisfied result into new RelationCheckResult class
 * Add a method to check all relations of a component and get the result
 * Add algorithm to score compatibility with a system, add chassis templates
 * ascli: Add new check-syscompat command to check chassis compatibility
 * Implement environment property for component screenshots
 * Autogenerate translatable DE and gui-environment-style C arrays
 * Expose more advanced markup conversion function, update function names
 * Allow BLAKE3 and SHA512 checksums for release artifacts
 * Stop supporting mailto: URLs in  tags
 * validator: Improve API and simplify it
 * validator: Parse XML in pedantic mode when validating
 * validator: Check screenshot environment property
 * validator: Only apply summary-has-dot-suffix check to untranslated strings
 * compose: Allow creating metadata with complete URLs and no base URL
 * spdx: Add API to retrieve a translated license name from an SPDX ID
 * qt: Switch to building with Qt6
 * qt: Make it possible to iterate ComponentBox
 * qt: Implement AppStream::ComponentBox::erase
 * qt: Allow concatenating two ComponentBoxes
 * qt: Allow loading Pool asynchronously
 * qt: Use ComponentBox/Releases in Qt bindings as well
 * qt: Add support for the new API to check relation satisfaction
 * qt: Maintenance and namespace fixes, use cPtr() to get C pointers everywhere
 * bundle: Add linglong as a new type of bundle
 * Add GUI environment IDs for macOS and Microsoft Windows
 * validator: Check if Release Description is inside description tag
 * validator: Add validation for content_rating
 * Add support for building on Win32
 * win32: change some file/path-related code for portability
 * Implement the developer element for unique developer IDs
 * Implement scaling factor for screenshots
 * component-box: Allow removal of components by-index
 * Implement support for external references and citations
 * Implement usertags for release data as well
 * Move ValueFlags to the context, instead of tieing them to components
 * pool: search: Add additional weight for exact substring matches on names
 * sysinfo: Add memory size detection support for macOS
 * Add support for Zstd for on-disk data compression
 * utils: Make tar unpacker independent of zstd binary presence
 * Drop Python2 provided tag support
 * data: Add ‘Endless’ to the list of desktops
 * Add NetBSD support

Specification:
 * Drop (most) deprecated information
 * docs: Clarify environment-based screenshot ordering
 * Add new  'snapshot' release kind
 * docs: Build all API documentation with gi-docgen
 * spec: Document the new "developer" element
 * spec: Document the "reference" tag for registry references
 * docs: Add example of YAML for references elements
 * Allow hyphens in the last segment of a component-ID
 * docs: Drop outdated information from l10n quickstart guide

Bugfixes:
 * meson: check for docbook xsl stylesheets
 * Fix tweaking of appstream.pc when building as subproject
 * Fix crash in asc_l10n_search_translations_qt()
 * qt: Make Qt6 dependency a system dependency.
 * meson: do not rely on an exe wrapper
 * meson: do not -I/usr/include when !stemmer
 * meson: Prevent building attempts with MSVC
 * meson: Use an SPDX license indentifier in project(license:)
 * Add meson overrides
 * compose: Set lower-cased CID for synthesized components again
 * compose: Set lower-cased CID in desktop-entry parse function
 * compose: Honor prefix in font search
 * compose: Select the correct default icon glyphs for fonts
 * Don't crash when non-YAML documents are read as YAML
 * Do not override default-priority when parsing multiple metadata files
 * Ensure stemmer always has the right locale and token-search works
 * Require a more recent libxmlb to avoid crashes
 * Rename component get_releases to indicate that releases may not be loaded 
from the web
 * Prevent string-id validation functions from matching source comments
 * Don't define _POSIX_C_SOURCE when building 

Re: [OE-core] [PATCH v2] ldconfig-native: Add usrmerge support

2023-12-15 Thread Khem Raj
On Fri, Dec 15, 2023 at 4:37 AM Johannes Pointner  wrote:
>
> On Wed, Dec 13, 2023 at 12:01 PM Ross Burton  wrote:
> >
> > On 6 Dec 2023, at 07:40, Johannes Pointner via lists.openembedded.org 
> >  wrote:
> > >
> > > From: Johannes Pointner 
> > >
> > > If DISTRO_FEATURE usrmerge is enabled, SLIBDIR is just a symlink to 
> > > LIBDIR.
> > > ldconfig-native uses hardcoded paths for SLIBDIR and LIBDIR that are fine 
> > > for
> > > the not usrmerge case. But if usrmerge is enabled ldconfig-native 
> > > generates a
> > > ld.so.cache, which is done in rootfs.py, that looks like this:
> > > 236 libs found in cache `/etc/ld.so.cache'
> > >   libzstd.so.1 (libc6) => /lib/libzstd.so.1
> > >   libz.so.1 (libc6) => /lib/libz.so.1
> > >   libxtables.so.12 (libc6) => /lib/libxtables.so.12
> > >   libxslt.so.1 (libc6) => /lib/libxslt.so.1
> > >   libxml2.so.2 (libc6) => /lib/libxml2.so.2
> > >
> > > This breaks for example the Qt QLibraryInfo paths if Qt is configured
> > > 'relocatable' and leads to the issue that the QtWebEngine can find the
> > > QtWebEngineProcess, Qt WebEngine resources,...
> > >
> > > Therefore don't let ldconfig-native parse SLIBDIR if it is a symlink.
> >
> > This still doesn’t explain *why* ldconfig is broken, why the workaround is 
> > a yocto-specific fix in ldconfig and not a general fix that other distros 
> > have, and why this isn’t a problem with Qt.
> As I wrote above ldconfig-native is broken for the usrmerge case
> because it uses hardcoded paths which are correct for the "not
> usrmerge case" but not for the "usrmerge case".
> Other distros as also the yocto ldconfig for the target system is
> configured at build time with the correct paths and works fine.
> This is an issue for Qt because it tries to determine the library
> locations using dladdr and this leads to incorrect paths that in my
> case broke QtWebEngine.

This is good explanation in general. It would be good to explain a bit
on how QT uses the native version of QT to manipulate paths
for QTWebengine.

> >
> > Ross
> >
> >
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192539): 
https://lists.openembedded.org/g/openembedded-core/message/192539
Mute This Topic: https://lists.openembedded.org/mt/103009101/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] rust: Upgrade 1.71.1 -> 1.74.1

2023-12-15 Thread Khem Raj
On Fri, Dec 15, 2023 at 4:41 AM Alex Kiernan  wrote:
>
> On Thu, Dec 14, 2023 at 10:28 AM Ross Burton  wrote:
> >
> > On 13 Dec 2023, at 14:06, Richard Purdie via lists.openembedded.org 
> >  wrote:
> > > I've run this with this patch included:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4082
> >
> > Same failure:
> >
> > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20231213-s13b67oz/packages/diff-html/
> >
> > Ross
>
> Thanks both.
>
> It does look like its just filename churn, but I cannot find where
> those names actually get generated :| Suspect this will be a report
> upstream and hope someone helps.
>

I think its the cmdline options passed to compiler-builtins crate. So
looking closely at this crates build log can reveal the problem. If
somewhere we have builds
done in two different folders I can take a look


> --
> Alex Kiernan
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192538): 
https://lists.openembedded.org/g/openembedded-core/message/192538
Mute This Topic: https://lists.openembedded.org/mt/103146651/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] create-spdx-2.2: combine spdx can try to write before dir creation

2023-12-15 Thread Joshua Watt
LGTM, Thanks

Reviewed-By: Joshua Watt 

On Fri, Dec 15, 2023 at 10:11 AM Jeremy Puhlman via
lists.openembedded.org 
wrote:
>
> From: "Jeremy A. Puhlman" 
>
> On occasion a file is attmpeded to be opened prior to the
> creation of the spdx_workdir. Create the directory before
> the open, just in case.
>
> File: '/build/layers/poky/meta/classes/create-spdx-2.2.bbclass', lineno: 
> 1081, function: combine_spdx
>  1077:)
>  1078:
>  1079:image_spdx_path = spdx_workdir / (rootfs_name + ".spdx.json")
>  1080:
>  *** 1081:with image_spdx_path.open("wb") as f:
>  1082:doc.to_json(f, sort_keys=True, indent=get_json_indent(d))
>
> Signed-off-by: Jeremy A. Puhlman 
> ---
>  meta/classes/create-spdx-2.2.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/create-spdx-2.2.bbclass 
> b/meta/classes/create-spdx-2.2.bbclass
> index b0aef80db1..486efadba9 100644
> --- a/meta/classes/create-spdx-2.2.bbclass
> +++ b/meta/classes/create-spdx-2.2.bbclass
> @@ -1075,7 +1075,7 @@ def combine_spdx(d, rootfs_name, rootfs_deploydir, 
> rootfs_spdxid, packages, spdx
>  "%s:%s" % (runtime_ref.externalDocumentId, runtime_doc.SPDXID),
>  comment="Runtime dependencies for %s" % name
>  )
> -
> +bb.utils.mkdirhier(spdx_workdir)
>  image_spdx_path = spdx_workdir / (rootfs_name + ".spdx.json")
>
>  with image_spdx_path.open("wb") as f:
> --
> 2.35.2
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192537): 
https://lists.openembedded.org/g/openembedded-core/message/192537
Mute This Topic: https://lists.openembedded.org/mt/103194653/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] create-spdx-2.2: combine spdx can try to write before dir creation

2023-12-15 Thread Jeremy Puhlman via lists.openembedded.org
From: "Jeremy A. Puhlman" 

On occasion a file is attmpeded to be opened prior to the
creation of the spdx_workdir. Create the directory before
the open, just in case.

File: '/build/layers/poky/meta/classes/create-spdx-2.2.bbclass', lineno: 1081, 
function: combine_spdx
 1077:)
 1078:
 1079:image_spdx_path = spdx_workdir / (rootfs_name + ".spdx.json")
 1080:
 *** 1081:with image_spdx_path.open("wb") as f:
 1082:doc.to_json(f, sort_keys=True, indent=get_json_indent(d))

Signed-off-by: Jeremy A. Puhlman 
---
 meta/classes/create-spdx-2.2.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/create-spdx-2.2.bbclass 
b/meta/classes/create-spdx-2.2.bbclass
index b0aef80db1..486efadba9 100644
--- a/meta/classes/create-spdx-2.2.bbclass
+++ b/meta/classes/create-spdx-2.2.bbclass
@@ -1075,7 +1075,7 @@ def combine_spdx(d, rootfs_name, rootfs_deploydir, 
rootfs_spdxid, packages, spdx
 "%s:%s" % (runtime_ref.externalDocumentId, runtime_doc.SPDXID),
 comment="Runtime dependencies for %s" % name
 )
-
+bb.utils.mkdirhier(spdx_workdir)
 image_spdx_path = spdx_workdir / (rootfs_name + ".spdx.json")
 
 with image_spdx_path.open("wb") as f:
-- 
2.35.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192536): 
https://lists.openembedded.org/g/openembedded-core/message/192536
Mute This Topic: https://lists.openembedded.org/mt/103194653/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/9] bitbake/runqueue: initialize RunQueueExecute before printdiff rather than after

2023-12-15 Thread Richard Purdie
On Fri, 2023-12-15 at 17:49 +0100, Alexander Kanavin wrote:
> On Fri, 15 Dec 2023 at 17:04, Richard Purdie
>  wrote:
> 
> > > Meanwhile I'd like to implement what I mentioned in note (1) in patch
> > > 4/9, as it's a real regression that I realized only today as I was
> > > preparing the patchset for submission and now it's bothering me :)
> > 
> > Yes, it is and I do agree we need to fix that.
> 
> I just completed the fixing. It all works wonderfully in local builds,
> but who knows what situations AB will be able to come up with :) It's
> a bit crowded on the AB right now to start the tests there, so here
> are the patches:
> https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/fix-printdiff
> (I run the tests with a special contrib/kanavin/ branch of
> autobuilder-helper that only runs the three needed selftests, and not
> the whole gigantic set)

Sounds good. I think we are getting to the bottom of some of the
underlying issues which is good and longer term should help usability a
lot.

> I also reverted the gnu-config tweak in that branch as it should be no
> longer necessary.

I was torn on that. I can drop from -next too.

> I'll cherry-pick the bitbake patch before doing any further tests, but
> it's now Friday evening, so anxiously watching ongoing selftests is
> perhaps not the best idea.

Fair enough! I've run that patch through local only testing so far, as
you say, the AB has a lot going on.

I've been torn on waiting for these or building M1 but I'm aiming for
just the CDN fix since this may or may not take a while to settle on
the autobuilder and I don't think we need any more pressure. The
failures are driving Alexandre a bit crazy in swatbot so getting things
sorted is important.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192535): 
https://lists.openembedded.org/g/openembedded-core/message/192535
Mute This Topic: https://lists.openembedded.org/mt/103169696/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/9] bitbake/runqueue: initialize RunQueueExecute before printdiff rather than after

2023-12-15 Thread Alexander Kanavin
On Fri, 15 Dec 2023 at 17:04, Richard Purdie
 wrote:

> > Meanwhile I'd like to implement what I mentioned in note (1) in patch
> > 4/9, as it's a real regression that I realized only today as I was
> > preparing the patchset for submission and now it's bothering me :)
>
> Yes, it is and I do agree we need to fix that.

I just completed the fixing. It all works wonderfully in local builds,
but who knows what situations AB will be able to come up with :) It's
a bit crowded on the AB right now to start the tests there, so here
are the patches:
https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/fix-printdiff
(I run the tests with a special contrib/kanavin/ branch of
autobuilder-helper that only runs the three needed selftests, and not
the whole gigantic set)

I also reverted the gnu-config tweak in that branch as it should be no
longer necessary.

I'll cherry-pick the bitbake patch before doing any further tests, but
it's now Friday evening, so anxiously watching ongoing selftests is
perhaps not the best idea.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192534): 
https://lists.openembedded.org/g/openembedded-core/message/192534
Mute This Topic: https://lists.openembedded.org/mt/103169696/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/9] bitbake/runqueue: initialize RunQueueExecute before printdiff rather than after

2023-12-15 Thread Richard Purdie
On Thu, 2023-12-14 at 18:28 +0100, Alexander Kanavin wrote:
> On Thu, 14 Dec 2023 at 15:39, Richard Purdie
>  wrote:
> 
> > I not entirely happy about this since start_worker() executes processes
> > and isn't trivial. The code is careful enough to tear them down too at
> > exit but it is all a bit of a waste of time.
> > 
> > I had wondered if we can create RunQueueExecute() without the workers
> > but as the code stands, it does poke things into them in a small
> > isolated section. I think this code flow should be tweaked to stop
> > RunQueueExecute needing the workers to be started and that would be a
> > decent cleanup of the code anyway.
> > 
> > I can take a look at that if it helps since I think I've been moving
> > towards that refactor for a while anyway?
> 
> Yes please. I haven't noticed any regression in printdiff performance,
> other than a couple of additional lines printed, but if you can make a
> better patch, that'd be welcome.

Patch on the bitbake list for this which removes more code than
it adds. We had already set everything up to do this :)

> Meanwhile I'd like to implement what I mentioned in note (1) in patch
> 4/9, as it's a real regression that I realized only today as I was
> preparing the patchset for submission and now it's bothering me :)

Yes, it is and I do agree we need to fix that.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192533): 
https://lists.openembedded.org/g/openembedded-core/message/192533
Mute This Topic: https://lists.openembedded.org/mt/103169696/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] tcl: skip event tests in run-ptest

2023-12-15 Thread Ross Burton
From: Ross Burton 

The event test suite is full of timing-sensitive test cases, so skip
them too.

[ YOCTO #15321 ]

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/tcltk/tcl/run-ptest | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/tcltk/tcl/run-ptest 
b/meta/recipes-devtools/tcltk/tcl/run-ptest
index 51e1e4aa7b7..6f017a6cb3d 100644
--- a/meta/recipes-devtools/tcltk/tcl/run-ptest
+++ b/meta/recipes-devtools/tcltk/tcl/run-ptest
@@ -5,8 +5,8 @@ export TZ="Europe/London"
 export TCL_LIBRARY=library
 
 # Some tests are overly strict with timings and fail on loaded systems.
-# See bugs #14825 #14882 #15081.
-SKIPPED_TESTS='cmdMZ-6.6 exit-1.* socket-* socket_inet-*'
+# See bugs #14825 #14882 #15081 #15321.
+SKIPPED_TESTS='cmdMZ-6.6 event-* exit-1.* socket-* socket_inet-*'
 
 for i in `ls tests/*.test | awk -F/ '{print $2}'`; do
 ./tcltest tests/all.tcl -file $i -skip "$SKIPPED_TESTS" >$i.log 2>&1
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192532): 
https://lists.openembedded.org/g/openembedded-core/message/192532
Mute This Topic: https://lists.openembedded.org/mt/103192468/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] gpgme: upgrading to 1.23.2 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

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

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

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

Regards,
The Upgrade Helper

-- >8 --
>From e19caefccbc864ab41ca8d9b90d511643898a825 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 13:42:53 +
Subject: [PATCH] gpgme: upgrade 1.23.1 -> 1.23.2

---
 ...ild-Make-gpgme.m4-use-gpgrt-config-with-.pc.patch |  2 +-
 .../0001-autogen.sh-remove-unknown-in-version.patch  | 10 --
 .../recipes-support/gpgme/gpgme/0001-pkgconfig.patch |  8 
 ...001-posix-io.c-Use-off_t-instead-of-off64_t.patch |  3 ++-
 .../0001-use-closefrom-on-linux-and-glibc-2.34.patch | 10 --
 ...g-python-gpg-error-config-should-not-be-use.patch |  2 +-
 .../0003-Correctly-install-python-modules.patch  | 12 +---
 .../gpgme/gpgme/0004-python-import.patch | 10 --
 ...fig-skip-all-lib-or-usr-lib-directories-in-.patch | 12 +---
 .../gpgme/gpgme/0006-fix-build-path-issue.patch  | 12 +---
 .../gpgme/0008-do-not-auto-check-var-PYTHON.patch|  6 +++---
 .../gpgme/{gpgme_1.23.1.bb => gpgme_1.23.2.bb}   |  2 +-
 12 files changed, 39 insertions(+), 50 deletions(-)
 rename meta/recipes-support/gpgme/{gpgme_1.23.1.bb => gpgme_1.23.2.bb} (97%)

diff --git 
a/meta/recipes-support/gpgme/gpgme/0001-Revert-build-Make-gpgme.m4-use-gpgrt-config-with-.pc.patch
 
b/meta/recipes-support/gpgme/gpgme/0001-Revert-build-Make-gpgme.m4-use-gpgrt-config-with-.pc.patch
index 8ed39280ca..de7248024e 100644
--- 
a/meta/recipes-support/gpgme/gpgme/0001-Revert-build-Make-gpgme.m4-use-gpgrt-config-with-.pc.patch
+++ 
b/meta/recipes-support/gpgme/gpgme/0001-Revert-build-Make-gpgme.m4-use-gpgrt-config-with-.pc.patch
@@ -1,4 +1,4 @@
-From ee1421f7a7a9f31400ba992a5be52b88d20170c9 Mon Sep 17 00:00:00 2001
+From 900b489305cf8565bee05bf9181a43a528937cfa Mon Sep 17 00:00:00 2001
 From: Hongxu Jia 
 Date: Fri, 10 May 2019 14:18:04 +0800
 Subject: [PATCH] Revert "build: Make gpgme.m4 use gpgrt-config with *.pc."
diff --git 
a/meta/recipes-support/gpgme/gpgme/0001-autogen.sh-remove-unknown-in-version.patch
 
b/meta/recipes-support/gpgme/gpgme/0001-autogen.sh-remove-unknown-in-version.patch
index 81af86e7b2..ff649a689b 100644
--- 
a/meta/recipes-support/gpgme/gpgme/0001-autogen.sh-remove-unknown-in-version.patch
+++ 
b/meta/recipes-support/gpgme/gpgme/0001-autogen.sh-remove-unknown-in-version.patch
@@ -1,4 +1,4 @@
-From 46f346dff73122caffe62eda84596a3a3bec859e Mon Sep 17 00:00:00 2001
+From bbeb1297cdfce53496af6b81f1b34a92042dd07e Mon Sep 17 00:00:00 2001
 From: Chen Qi 
 Date: Tue, 28 Feb 2023 13:43:51 +0800
 Subject: [PATCH] autogen.sh: remove '-unknown' in version
@@ -12,15 +12,16 @@ Remove the '-unknown' suffix to fix this issue.
 Upstream-Status: Submitted 
[https://lists.gnupg.org/pipermail/gnupg-devel/2023-February/035293.html]
 
 Signed-off-by: Chen Qi 
+
 ---
  autogen.sh | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/autogen.sh b/autogen.sh
-index 9b36158..d5cccd2 100755
+index 4e1665b..a55326d 100755
 --- a/autogen.sh
 +++ b/autogen.sh
-@@ -266,7 +266,7 @@ if [ "$myhost" = "find-version" ]; then
+@@ -269,7 +269,7 @@ if [ "$myhost" = "find-version" ]; then
  else
ingit=no
beta=yes
@@ -29,6 +30,3 @@ index 9b36158..d5cccd2 100755
rev="000"
rvd="0"
  fi
--- 
-2.17.1
-
diff --git a/meta/recipes-support/gpgme/gpgme/0001-pkgconfig.patch 
b/meta/recipes-support/gpgme/gpgme/0001-pkgconfig.patch
index 738b23cd58..b6d738e7e0 100644
--- a/meta/recipes-support/gpgme/gpgme/0001-pkgconfig.patch
+++ b/meta/recipes-support/gpgme/gpgme/0001-pkgconfig.patch
@@ -1,4 +1,4 @@
-From f8221238d51066b7a1a5f2917cce2791876ea8b0 Mon Sep 17 00:00:00 2001
+From 52b2a07dcff94467e01728583b62ecfb01fce46c Mon Sep 17 00:00:00 2001
 From: Richard Purdie 
 Date: Fri, 10 May 2019 14:23:55 +0800
 Subject: [PATCH] pkgconfig
@@ -26,10 +26,10 @@ Signed-off-by: Wang Mingyu 
  create mode 100644 src/gpgme-pthread.pc.in
 
 diff --git a/configure.ac b/configure.ac
-index d1b9aca..9c4f97c 100644
+index ae4c7da..df892c9 100644
 --- a/configure.ac
 +++ b/configure.ac
-@@ -1043,6 +1043,7 @@ 

[OE-core] [AUH] xserver-xorg: upgrading to 21.1.10 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xserver-xorg* to *21.1.10* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-xserver-xorg-upgrade-21.1.9-21.1.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 d079943892d6bbbc8f61d6e418950ede88233508 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 11:23:15 +
Subject: [PATCH] xserver-xorg: upgrade 21.1.9 -> 21.1.10

---
 ...001-Avoid-duplicate-definitions-of-IOPortBase.patch |  2 +-
 ...Bus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch | 10 --
 ...{xserver-xorg_21.1.9.bb => xserver-xorg_21.1.10.bb} |  2 +-
 3 files changed, 6 insertions(+), 8 deletions(-)
 rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_21.1.9.bb => 
xserver-xorg_21.1.10.bb} (92%)

diff --git 
a/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-Avoid-duplicate-definitions-of-IOPortBase.patch
 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-Avoid-duplicate-definitions-of-IOPortBase.patch
index 11d5546537..9622e9688c 100644
--- 
a/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-Avoid-duplicate-definitions-of-IOPortBase.patch
+++ 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-Avoid-duplicate-definitions-of-IOPortBase.patch
@@ -1,4 +1,4 @@
-From ce3b8a230a3805c9b557c1f106795675bd034860 Mon Sep 17 00:00:00 2001
+From df49b7d602572b82e18e25cb875cc93ac498d682 Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Mon, 17 Aug 2020 10:50:51 -0700
 Subject: [PATCH] Avoid duplicate definitions of IOPortBase
diff --git 
a/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch
 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch
index d05eec5bb9..7fdc58d5d6 100644
--- 
a/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch
+++ 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg/0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch
@@ -1,4 +1,4 @@
-From d77cdc5e1eee26821ab98c947abea53fb7b18fe5 Mon Sep 17 00:00:00 2001
+From 9bbf92826d27d16e71a12630e6e37482b79fc3d6 Mon Sep 17 00:00:00 2001
 From: California Sullivan 
 Date: Fri, 16 Mar 2018 17:23:11 -0700
 Subject: [PATCH] xf86pciBus.c: use Intel ddx only for pre-gen4 hardware
@@ -15,15 +15,16 @@ Upstream-Status: Pending [Debian/Fedora patch
 
https://src.fedoraproject.org/rpms/xorg-x11-server/c/ee515e44b07e37689abf48cf2fffb41578f3bc1d]
 
 Signed-off-by: California Sullivan 
+
 ---
  hw/xfree86/common/xf86pciBus.c | 18 +-
  1 file changed, 17 insertions(+), 1 deletion(-)
 
 diff --git a/hw/xfree86/common/xf86pciBus.c b/hw/xfree86/common/xf86pciBus.c
-index e61ae0cd4..d70c99197 100644
+index aeeed8b..db705bf 100644
 --- a/hw/xfree86/common/xf86pciBus.c
 +++ b/hw/xfree86/common/xf86pciBus.c
-@@ -1173,7 +1173,23 @@ xf86VideoPtrToDriverList(struct pci_device *dev,
+@@ -1174,7 +1174,23 @@ xf86VideoPtrToDriverList(struct pci_device *dev, 
XF86MatchedDrivers *md)
case 0x0bef:
/* Use fbdev/vesa driver on Oaktrail, Medfield, CDV */
break;
@@ -48,6 +49,3 @@ index e61ae0cd4..d70c99197 100644
driverList[0] = "intel";
break;
  }
--- 
-2.14.3
-
diff --git a/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.9.bb 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.10.bb
similarity index 92%
rename from meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.9.bb
rename to meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.10.bb
index 43c06181e3..0a180950f5 100644
--- a/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.9.bb
+++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.10.bb
@@ -3,7 +3,7 @@ require xserver-xorg.inc
 SRC_URI += 
"file://0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch \
file://0001-Avoid-duplicate-definitions-of-IOPortBase.patch \
"
-SRC_URI[sha256sum] = 
"ff697be2011b4c4966b7806929e51b7a08e9d33800d505305d26d9ccde4b533a"
+SRC_URI[sha256sum] = 
"ceb0b3a2efc57ac3ccf388d3dc88b97615068639fb284d469689ae3d105611d0"
 
 # These extensions are now 

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

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-252-253.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 ad2cebf05c9da489ae3019b963d2b92064746b6d Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 13:35:52 +
Subject: [PATCH] diffoscope: upgrade 252 -> 253

---
 .../diffoscope/{diffoscope_252.bb => diffoscope_253.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/diffoscope/{diffoscope_252.bb => 
diffoscope_253.bb} (93%)

diff --git a/meta/recipes-support/diffoscope/diffoscope_252.bb 
b/meta/recipes-support/diffoscope/diffoscope_253.bb
similarity index 93%
rename from meta/recipes-support/diffoscope/diffoscope_252.bb
rename to meta/recipes-support/diffoscope/diffoscope_253.bb
index 86dc85df83..a1fc63efc3 100644
--- a/meta/recipes-support/diffoscope/diffoscope_252.bb
+++ b/meta/recipes-support/diffoscope/diffoscope_253.bb
@@ -12,7 +12,7 @@ PYPI_PACKAGE = "diffoscope"
 
 inherit pypi setuptools3
 
-SRC_URI[sha256sum] = 
"e268384fa484f3dd8a936da626e6ef1b231dcb286d09a360f37548637f8dd46d"
+SRC_URI[sha256sum] = 
"ca3d826b691f4998d6de28a016b3555d56a7283b97ad92944ce643ea6e7eb614"
 
 RDEPENDS:${PN} += "\
 binutils \
-- 
2.42.0

NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (0 cached, 911 parsed). 1843 targets, 49 
skipped, 0 masked, 0 errors.
Removing 99 recipes from the core2-64 sysroot...done.
Removing 126 recipes from the qemux86_64 sysroot...done.

Summary: There was 1 ERROR message, returning a non-zero exit code.
ERROR: Nothing PROVIDES 'diffoscope'
diffoscope was skipped: incompatible with host x86_64-poky-linux-musl (not in 
COMPATIBLE_HOST)
diffoscope was skipped: incompatible with host x86_64-poky-linux-musl (not in 
COMPATIBLE_HOST)
packages/core2-64-poky-linux/diffoscope/diffoscope-dbg: PKGV changed from 252 
[default] to 253 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-dbg: PV changed from "252" 
to "253"
packages/core2-64-poky-linux/diffoscope/diffoscope-dev: PKGV changed from 252 
[default] to 253 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-dev: PV changed from "252" 
to "253"
packages/core2-64-poky-linux/diffoscope/diffoscope-doc: PKGV changed from 252 
[default] to 253 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-doc: PV changed from "252" 
to "253"
packages/core2-64-poky-linux/diffoscope/diffoscope-locale: PKGV changed from 
252 [default] to 253 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-locale: PV changed from 
"252" to "253"
packages/core2-64-poky-linux/diffoscope/diffoscope-src: PKGV changed from 252 
[default] to 253 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-src: PV changed from "252" 
to "253"
packages/core2-64-poky-linux/diffoscope/diffoscope-staticdev: PKGV changed from 
252 [default] to 253 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope-staticdev: PV changed from 
"252" to "253"
packages/core2-64-poky-linux/diffoscope/diffoscope: FILELIST: directory renamed 
/usr/lib/python3.11/site-packages/diffoscope-252.dist-info -> 
/usr/lib/python3.11/site-packages/diffoscope-253.dist-info, added 
"/usr/lib/python3.11/site-packages/diffoscope/comparators/7z.py 
/usr/lib/python3.11/site-packages/diffoscope/comparators/__pycache__/7z.cpython-311.pyc"
packages/core2-64-poky-linux/diffoscope/diffoscope: PKGV changed from 252 
[default] to 253 [default]
packages/core2-64-poky-linux/diffoscope/diffoscope: PV changed from "252" to 
"253"
packages/core2-64-poky-linux/diffoscope/diffoscope: PKGSIZE changed from 
1414083 to 1421975 (+1%)
packages/core2-64-poky-linux/diffoscope: PKGV changed from 252 [default] to 253 
[default]
packages/core2-64-poky-linux/diffoscope: PV changed from "252" to "253"
packages/core2-64-poky-linux/diffoscope: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/d/diffoscope/diffoscope-252.tar.gz;downloadfilename=diffoscope-252.tar.gz;
 to 

[OE-core] [AUH] libusb1: upgrading to 1.0.27 FAILED

2023-12-15 Thread Auto Upgrade Helper
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 (devtool error).

Detailed error information:

The following devtool command failed:  upgrade libusb1 -V 1.0.27
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-e812cf88ac9806465d77b5f6de99aaf478e59bb7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:e812cf88ac9806465d77b5f6de99aaf478e59bb7"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
Loading cache...done.
Loaded 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-e812cf88ac9806465d77b5f6de99aaf478e59bb7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:e812cf88ac9806465d77b5f6de99aaf478e59bb7"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% 
complete)
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.tar.bz2,
 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: 3 seconds
NOTE: The errors for this build are stored in 
/home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20231215135233.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_20231215135233.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: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.tar.bz2...
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-5i9ni1a4/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-5i9ni1a4/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-5i9ni1a4/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipe
 
tool-5i9ni1a4/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-5i9ni1a4/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-5i9ni1a4/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 -O 
/srv/autobuilder/autobuilder.yocto.io/current_sources/libusb-1.0.27.tar.bz2.tmp 
-P 

[OE-core] [AUH] icu: upgrading to 74-2 FAILED

2023-12-15 Thread Auto Upgrade Helper
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 1842 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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-f317cbe3a6fbab875b29434ab1ba49b08ad29cd5"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:f317cbe3a6fbab875b29434ab1ba49b08ad29cd5"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-f317cbe3a6fbab875b29434ab1ba49b08ad29cd5"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:f317cbe3a6fbab875b29434ab1ba49b08ad29cd5"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% 
complete)
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: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files: 100% || Time: 0:00:00

INFO: Extracting current version source...
INFO: 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 7924a94e431e82a6ea45bdeda0b07fe69b1d97f9
INFO: Rebasing devtool-override-class-target onto 
7924a94e431e82a6ea45bdeda0b07fe69b1d97f9
Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 349, in 

ret = main()
  ^^
  File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 336, 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 (#192515): 
https://lists.openembedded.org/g/openembedded-core/message/192515
Mute This Topic: https://lists.openembedded.org/mt/103190929/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] bmap-tools: upgrading to 3.7 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

The following devtool command failed:  upgrade bmap-tools -V 3.7 -S 
d84a6fd202fe246a0bc19ed2082e41bcdd75fb13
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1843 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-4c333a3b8e1903dea546d53dab52e83980355633"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:4c333a3b8e1903dea546d53dab52e83980355633"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto d84a6fd202fe246a0bc19ed2082e41bcdd75fb13
Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 349, in 

ret = main()
  ^^
  File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 336, 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/bmap-tools/COPYING'


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 (#192513): 
https://lists.openembedded.org/g/openembedded-core/message/192513
Mute This Topic: https://lists.openembedded.org/mt/103190927/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] enchant2: upgrading to 2.6.4 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-enchant2-upgrade-2.6.2-2.6.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 6760617256f0ba4e513295d38eb0bea9d0642f5c Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 13:38:12 +
Subject: [PATCH] enchant2: upgrade 2.6.2 -> 2.6.4

---
 .../enchant/{enchant2_2.6.2.bb => enchant2_2.6.4.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/enchant/{enchant2_2.6.2.bb => enchant2_2.6.4.bb} 
(92%)

diff --git a/meta/recipes-support/enchant/enchant2_2.6.2.bb 
b/meta/recipes-support/enchant/enchant2_2.6.4.bb
similarity index 92%
rename from meta/recipes-support/enchant/enchant2_2.6.2.bb
rename to meta/recipes-support/enchant/enchant2_2.6.4.bb
index 38d3245d20..76be283f0c 100644
--- a/meta/recipes-support/enchant/enchant2_2.6.2.bb
+++ b/meta/recipes-support/enchant/enchant2_2.6.4.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] = 
"6686a728e56e760f8dee09a22f0fb53b46ee9dbe7d64cf9e5bb35a658bff7e1d"
+SRC_URI[sha256sum] = 
"833b4d5600dbe9ac867e543aac6a7a40ad145351495ca41223d4499d3ddbbd2c"
 
 GITHUB_BASE_URI = "https://github.com/AbiWord/enchant/releases;
 
-- 
2.42.0



0001-enchant2-upgrade-2.6.2-2.6.4.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1843 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (910 cached, 1 parsed). 1842 targets, 38 
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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-af7b11ad31f0b6c3c3193c8e6638e0bb5e835633"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:af7b11ad31f0b6c3c3193c8e6638e0bb5e835633"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 158 Local 146 Mirrors 0 Missed 12 Current 315 (92% 
match, 97% complete)
NOTE: Executing Tasks
NOTE: Running setscene task 329 of 473 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/glib-2.0/glib-2.0_2.78.1.bb:do_create_spdx_setscene)
NOTE: Running setscene task 330 of 473 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/aspell/aspell_0.60.8.bb:do_create_spdx_setscene)
NOTE: recipe aspell-0.60.8-r0: task do_create_spdx_setscene: Started
NOTE: recipe glib-2.0-1_2.78.1-r0: task do_create_spdx_setscene: Started
NOTE: Running task 934 of 1359 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/enchant/enchant2_2.6.4.bb:do_recipe_qa)
NOTE: recipe aspell-0.60.8-r0: task do_create_spdx_setscene: Succeeded
NOTE: recipe glib-2.0-1_2.78.1-r0: task do_create_spdx_setscene: Succeeded
NOTE: Running setscene task 442 of 473 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/libtool/libtool-cross_2.4.7.bb:do_create_spdx_setscene)
NOTE: Running setscene task 449 of 473 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/libtool/libtool-cross_2.4.7.bb:do_populate_sysroot_setscene)
NOTE: recipe enchant2-2.6.4-r0: task do_recipe_qa: Started
NOTE: recipe libtool-cross-2.4.7-r0: task do_populate_sysroot_setscene: Started
NOTE: recipe libtool-cross-2.4.7-r0: task do_create_spdx_setscene: Started
NOTE: recipe libtool-cross-2.4.7-r0: task do_create_spdx_setscene: Succeeded
NOTE: Running setscene task 451 of 473 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/gcc/gcc-runtime_13.2.bb:do_create_spdx_setscene)
NOTE: recipe enchant2-2.6.4-r0: task 

[OE-core] [AUH] linux-firmware: upgrading to 20231211 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 
0001-linux-firmware-upgrade-20231030-20231211.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 dacda6bcc2d439c18a69d6e83c08a4e8a2f25251 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 11:30:28 +
Subject: [PATCH] linux-firmware: upgrade 20231030 -> 20231211

---
 ...20231030.bb => linux-firmware_20231211.bb} | 508 +-
 1 file changed, 506 insertions(+), 2 deletions(-)
 rename meta/recipes-kernel/linux-firmware/{linux-firmware_20231030.bb => 
linux-firmware_20231211.bb} (79%)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
similarity index 79%
rename from meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
rename to meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
index 6667f00612..39d1cd27f8 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
@@ -1,3 +1,507 @@
+# 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:
+#
+# --- WHENCE
+# +++ WHENCE
+# @@ -536,14 +536,14 @@
+#  
+#  File: cxgb4/t4fw-1.14.4.0.bin
+#  File: cxgb4/t4fw-1.15.37.0.bin
+# -File: cxgb4/t4fw-1.27.4.0.bin
+# -Link: cxgb4/t4fw.bin -> t4fw-1.27.4.0.bin
+# +File: cxgb4/t4fw-1.27.5.0.bin
+# +Link: cxgb4/t4fw.bin -> t4fw-1.27.5.0.bin
+#  File: cxgb4/t5fw-1.14.4.0.bin
+#  File: cxgb4/t5fw-1.15.37.0.bin
+# -File: cxgb4/t5fw-1.27.4.0.bin
+# -Link: cxgb4/t5fw.bin -> t5fw-1.27.4.0.bin
+# -File: cxgb4/t6fw-1.27.4.0.bin
+# -Link: cxgb4/t6fw.bin -> t6fw-1.27.4.0.bin
+# +File: cxgb4/t5fw-1.27.5.0.bin
+# +Link: cxgb4/t5fw.bin -> t5fw-1.27.5.0.bin
+# +File: cxgb4/t6fw-1.27.5.0.bin
+# +Link: cxgb4/t6fw.bin -> t6fw-1.27.5.0.bin
+#  File: cxgb4/aq1202_fw.cld
+#  File: cxgb4/bcm8483.bin
+#  File: cxgb4/configs/t4-config-default.txt
+# @@ -1017,22 +1017,22 @@
+#  Version: 74.a5e9588b.0
+#  
+#  File: iwlwifi-cc-a0-77.ucode
+# -Version: 74.bd067429.0
+# +Version: 74.ad46c98b.0
+#  
+#  File: iwlwifi-Qu-b0-hr-b0-77.ucode
+# -Version: 74.bd067429.0
+# +Version: 74.ad46c98b.0
+#  
+#  File: iwlwifi-Qu-b0-jf-b0-77.ucode
+# -Version: 74.bd067429.0
+# +Version: 74.ad46c98b.0
+#  
+#  File: iwlwifi-Qu-c0-hr-b0-77.ucode
+# -Version: 74.bd067429.0
+# +Version: 74.ad46c98b.0
+#  
+#  File: iwlwifi-Qu-c0-jf-b0-77.ucode
+# -Version: 74.bd067429.0
+# +Version: 74.ad46c98b.0
+#  
+#  File: iwlwifi-QuZ-a0-hr-b0-77.ucode
+# -Version: 74.bd06742.0
+# +Version: 74.ad46c98b.0
+#  
+#  File: iwlwifi-QuZ-a0-jf-b0-77.ucode
+#  Version: 74.206b0184.0
+# @@ -1055,6 +1055,9 @@
+#  File: iwlwifi-ty-a0-gf-a0-84.ucode
+#  Version: 81.8e5c544c.0
+#  
+# +File: iwlwifi-ty-a0-gf-a0-86.ucode
+# +Version: 83.fb5c9aeb.0
+# +
+#  File: iwlwifi-so-a0-gf4-a0-77.ucode
+#  Version: 74.f92b5fed.0
+#  
+# @@ -1073,6 +1076,9 @@
+#  File: iwlwifi-so-a0-gf4-a0-84.ucode
+#  Version: 81.8e5c544c.0
+#  
+# +File: iwlwifi-so-a0-gf4-a0-86.ucode
+# +Version: 83.fb5c9aeb.0
+# +
+#  File: iwlwifi-so-a0-gf-a0-77.ucode
+#  Version: 74.f92b5fed.0
+#  
+# @@ -1091,6 +1097,9 @@
+#  File: iwlwifi-so-a0-gf-a0-84.ucode
+#  Version: 81.8e5c544c.0
+#  
+# +File: iwlwifi-so-a0-gf-a0-86.ucode
+# +Version: 83.fb5c9aeb.0
+# +
+#  File: iwlwifi-so-a0-hr-b0-77.ucode
+#  Version: 74.f92b5fed.0
+#  
+# @@ -1106,6 +1115,9 @@
+#  File: iwlwifi-so-a0-hr-b0-84.ucode
+#  Version: 81.8e5c544c.0
+#  
+# +File: iwlwifi-so-a0-hr-b0-86.ucode
+# +Version: 83.fb5c9aeb.0
+# +
+#  File: iwlwifi-so-a0-jf-b0-77.ucode
+#  Version: 74.f92b5fed.0
+#  
+# @@ -1114,20 +1126,32 @@
+#  File: iwlwifi-gl-c0-fm-c0-83.ucode
+#  Version: 80.d24e06ed.0
+#  
+# +File: iwlwifi-gl-c0-fm-c0-86.ucode
+# +Version: 83.fb5c9aeb.0
+# +
+#  File: iwlwifi-gl-c0-fm-c0.pnvm
+#  
+#  

[OE-core] [AUH] puzzles: upgrading to 08365fb260ae6e32442dd9f196e65d13facb4b33 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *puzzles* to 
*08365fb260ae6e32442dd9f196e65d13facb4b33* 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 f97b3ec94d75b6346dba39dacbe454603b82416e Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 11:38:03 +
Subject: [PATCH] puzzles: upgrade to latest revision

---
 meta/recipes-sato/puzzles/puzzles_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-sato/puzzles/puzzles_git.bb 
b/meta/recipes-sato/puzzles/puzzles_git.bb
index d0a9af7cb6..ab4b2394b8 100644
--- a/meta/recipes-sato/puzzles/puzzles_git.bb
+++ b/meta/recipes-sato/puzzles/puzzles_git.bb
@@ -10,7 +10,7 @@ REQUIRED_DISTRO_FEATURES = "x11"
 SRC_URI = "git://git.tartarus.org/simon/puzzles.git;branch=main;protocol=https"
 
 UPSTREAM_CHECK_COMMITS = "1"
-SRCREV = "96d65e852cea8a95001fa70e3ec2996d4ea5e2b4"
+SRCREV = "08365fb260ae6e32442dd9f196e65d13facb4b33"
 PE = "2"
 PV = "0.0+git"
 
-- 
2.42.0



0001-puzzles-upgrade-to-latest-revision.patch
Description: Binary data
packages/core2-64-poky-linux/puzzles/puzzles-dbg: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-dbg: PKGSIZE changed from 19529816 
to 19530448 (+0%)
packages/core2-64-poky-linux/puzzles/puzzles-dev: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-doc: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-locale: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-src: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-src: PKGSIZE changed from 3837866 
to 3838531 (+0%)
packages/core2-64-poky-linux/puzzles/puzzles-staticdev: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-dbg: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-dev: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-doc: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-locale: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-src: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles-staticdev: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260
packages/core2-64-poky-linux/puzzles/puzzles: PKGV changed from 
0.0+git0+96d65e852c to 0.0+git0+08365fb260

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192508): 
https://lists.openembedded.org/g/openembedded-core/message/192508
Mute This Topic: https://lists.openembedded.org/mt/103190922/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

2023-12-15 Thread Auto Upgrade Helper
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 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cf470c5b663c79fa6d930dcbe6a37b93674afb59"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cf470c5b663c79fa6d930dcbe6a37b93674afb59"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 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 (#192506): 
https://lists.openembedded.org/g/openembedded-core/message/192506
Mute This Topic: https://lists.openembedded.org/mt/103190920/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] appstream: upgrading to 1.0.0 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe appstream failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-4c333a3b8e1903dea546d53dab52e83980355633"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:4c333a3b8e1903dea546d53dab52e83980355633"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-4c333a3b8e1903dea546d53dab52e83980355633"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:4c333a3b8e1903dea546d53dab52e83980355633"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:  25% |#   | ETA:  0:00:00
Adding changed files:  50% |##  | ETA:  0:00:00
Adding changed files:  75% |### | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://www.freedesktop.org/software/appstream/releases/AppStream-1.0.0.tar.xz...
INFO: Rebasing devtool onto b3d48922a762edcf1de2aae9aabc18fe7d8a9c0d
WARNING: Command 'git rebase b3d48922a762edcf1de2aae9aabc18fe7d8a9c0d' failed:
Auto-merging meson.build
CONFLICT (content): Merge conflict in meson.build

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



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

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192509): 
https://lists.openembedded.org/g/openembedded-core/message/192509
Mute This Topic: https://lists.openembedded.org/mt/103190923/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] libxrandr: upgrading to 1.5.4 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-libxrandr-upgrade-1.5.3-1.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 7dacdfd7baca7608ed7a3921ddeebfad03fcdbb1 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 11:17:24 +
Subject: [PATCH] libxrandr: upgrade 1.5.3 -> 1.5.4

---
 .../xorg-lib/{libxrandr_1.5.3.bb => libxrandr_1.5.4.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/xorg-lib/{libxrandr_1.5.3.bb => 
libxrandr_1.5.4.bb} (87%)

diff --git a/meta/recipes-graphics/xorg-lib/libxrandr_1.5.3.bb 
b/meta/recipes-graphics/xorg-lib/libxrandr_1.5.4.bb
similarity index 87%
rename from meta/recipes-graphics/xorg-lib/libxrandr_1.5.3.bb
rename to meta/recipes-graphics/xorg-lib/libxrandr_1.5.4.bb
index 98572bd969..3e2825b916 100644
--- a/meta/recipes-graphics/xorg-lib/libxrandr_1.5.3.bb
+++ b/meta/recipes-graphics/xorg-lib/libxrandr_1.5.4.bb
@@ -19,4 +19,4 @@ XORG_PN = "libXrandr"
 
 BBCLASSEXTEND = "native nativesdk"
 
-SRC_URI[sha256sum] = 
"897639014a78e1497704d669c5dd5682d721931a4452c89a7ba62676064eb428"
+SRC_URI[sha256sum] = 
"1ad5b065375f4a85915aa60611cc6407c060492a214d7f9daf214be752c3b4d3"
-- 
2.42.0



0001-libxrandr-upgrade-1.5.3-1.5.4.patch
Description: Binary data
packages/core2-64-poky-linux/libxrandr: SRC_URI changed from 
"https://www.x.org/releases//individual/lib/libXrandr-1.5.3.tar.xz; to 
"https://www.x.org/releases//individual/lib/libXrandr-1.5.4.tar.xz;
packages/core2-64-poky-linux/libxrandr: PV changed from "1.5.3" to "1.5.4"
packages/core2-64-poky-linux/libxrandr: PKGV changed from 1.5.3 [default] to 
1.5.4 [default]
packages/core2-64-poky-linux/libxrandr/libxrandr-dbg: PV changed from "1.5.3" 
to "1.5.4"
packages/core2-64-poky-linux/libxrandr/libxrandr-dbg: PKGV changed from 1.5.3 
[default] to 1.5.4 [default]
packages/core2-64-poky-linux/libxrandr/libxrandr-dbg: PKGSIZE changed from 
351152 to 351112 (-0%)
packages/core2-64-poky-linux/libxrandr/libxrandr-dev: PV changed from "1.5.3" 
to "1.5.4"
packages/core2-64-poky-linux/libxrandr/libxrandr-dev: PKGV changed from 1.5.3 
[default] to 1.5.4 [default]
packages/core2-64-poky-linux/libxrandr/libxrandr-doc: PV changed from "1.5.3" 
to "1.5.4"
packages/core2-64-poky-linux/libxrandr/libxrandr-doc: PKGV changed from 1.5.3 
[default] to 1.5.4 [default]
packages/core2-64-poky-linux/libxrandr/libxrandr-locale: PV changed from 
"1.5.3" to "1.5.4"
packages/core2-64-poky-linux/libxrandr/libxrandr-locale: PKGV changed from 
1.5.3 [default] to 1.5.4 [default]
packages/core2-64-poky-linux/libxrandr/libxrandr-src: PV changed from "1.5.3" 
to "1.5.4"
packages/core2-64-poky-linux/libxrandr/libxrandr-src: PKGV changed from 1.5.3 
[default] to 1.5.4 [default]
packages/core2-64-poky-linux/libxrandr/libxrandr-src: PKGSIZE changed from 
116726 to 116731 (+0%)
packages/core2-64-poky-linux/libxrandr/libxrandr-staticdev: PV changed from 
"1.5.3" to "1.5.4"
packages/core2-64-poky-linux/libxrandr/libxrandr-staticdev: PKGV changed from 
1.5.3 [default] to 1.5.4 [default]
packages/core2-64-poky-linux/libxrandr/libxrandr: PV changed from "1.5.3" to 
"1.5.4"
packages/core2-64-poky-linux/libxrandr/libxrandr: PKGV changed from 1.5.3 
[default] to 1.5.4 [default]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192504): 
https://lists.openembedded.org/g/openembedded-core/message/192504
Mute This Topic: https://lists.openembedded.org/mt/103190918/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] piglit: upgrading to 8c88708145af4f75a3a2eaf8fd08d649acc02fcc SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to 
*8c88708145af4f75a3a2eaf8fd08d649acc02fcc* 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 9be10e42f2e11f2eec0b2f3cb02a5670b0d3 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 11:09:12 +
Subject: [PATCH] piglit: upgrade to latest revision

---
 ...-tests-Fix-narrowing-errors-seen-with-clang.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 +-
 4 files changed, 11 insertions(+), 17 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..4a49765705 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 f9bc7cb367fb66dce481eb6ca87268caa9111093 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/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..f0d8ef0f26 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 4da179631e045ea49f7d8fbdd50d45212457d033 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 100644
 --- a/tests/util/CMakeLists.txt
 +++ b/tests/util/CMakeLists.txt
 @@ -97,7 +97,7 @@ if(PIGLIT_USE_WAFFLE)
@@ -27,6 +28,3 @@ index a5f080156..a303a9f58 100644
)
endif()
if(PIGLIT_HAS_X11)
--- 
-2.11.0
-
diff --git 
a/meta/recipes-graphics/piglit/piglit/0003-tests-util-piglit-shader.c-do-not-hardcode-build-pat.patch
 
b/meta/recipes-graphics/piglit/piglit/0003-tests-util-piglit-shader.c-do-not-hardcode-build-pat.patch
index 16c7c5c803..baccf7a11a 100644
--- 
a/meta/recipes-graphics/piglit/piglit/0003-tests-util-piglit-shader.c-do-not-hardcode-build-pat.patch
+++ 
b/meta/recipes-graphics/piglit/piglit/0003-tests-util-piglit-shader.c-do-not-hardcode-build-pat.patch
@@ -1,19 +1,20 @@
-From 1c67250308a92d4991ed05d9d240090ab84accae Mon Sep 17 00:00:00 2001
+From 4cda2607d85ae74b2c71fdeb8a464e2c44366f89 Mon Sep 17 00:00:00 2001
 From: Alexander Kanavin 
 Date: Tue, 10 Nov 2020 17:13:50 +
-Subject: [PATCH 2/2] tests/util/piglit-shader.c: do not hardcode build path
- into target binary
+Subject: [PATCH] tests/util/piglit-shader.c: do not hardcode build path into
+ target binary
 
 This helps reproducibilty.
 
 Upstream-Status: Inappropriate [oe-core 

[OE-core] [AUH] stress-ng: upgrading to 0.17.03 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.17.03* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.17.01-0.17.03.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 cca7ec4caf053178f6806e71d87adeb466377aa3 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 09:45:10 +
Subject: [PATCH] stress-ng: upgrade 0.17.01 -> 0.17.03

---
 .../stress-ng/{stress-ng_0.17.01.bb => stress-ng_0.17.03.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/stress-ng/{stress-ng_0.17.01.bb => 
stress-ng_0.17.03.bb} (94%)

diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.17.01.bb 
b/meta/recipes-extended/stress-ng/stress-ng_0.17.03.bb
similarity index 94%
rename from meta/recipes-extended/stress-ng/stress-ng_0.17.01.bb
rename to meta/recipes-extended/stress-ng/stress-ng_0.17.03.bb
index b6fd96d857..0da5294f31 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.17.01.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.17.03.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 SRC_URI = 
"git://github.com/ColinIanKing/stress-ng.git;protocol=https;branch=master \
"
-SRCREV = "c9669b041eff5905da191974ba0102208a59e04e"
+SRCREV = "8c39f5a2d9b199189456f414afd9e536dae69d1b"
 S = "${WORKDIR}/git"
 
 DEPENDS = "coreutils-native libbsd"
-- 
2.42.0



0001-stress-ng-upgrade-0.17.01-0.17.03.patch
Description: Binary data
packages/core2-64-poky-linux/stress-ng: PKGV changed from 0.17.01 [default] to 
0.17.03 [default]
packages/core2-64-poky-linux/stress-ng: PV changed from "0.17.01" to "0.17.03"
packages/core2-64-poky-linux/stress-ng/stress-ng-bash-completion: PV changed 
from "0.17.01" to "0.17.03"
packages/core2-64-poky-linux/stress-ng/stress-ng-bash-completion: PKGV changed 
from 0.17.01 [default] to 0.17.03 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-dbg: PKGSIZE changed from 
17604528 to 18461696 (+5%)
packages/core2-64-poky-linux/stress-ng/stress-ng-dbg: PV changed from "0.17.01" 
to "0.17.03"
packages/core2-64-poky-linux/stress-ng/stress-ng-dbg: PKGV changed from 0.17.01 
[default] to 0.17.03 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-dev: PV changed from "0.17.01" 
to "0.17.03"
packages/core2-64-poky-linux/stress-ng/stress-ng-dev: PKGV changed from 0.17.01 
[default] to 0.17.03 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-doc: PKGSIZE changed from 
80266 to 80754 (+1%)
packages/core2-64-poky-linux/stress-ng/stress-ng-doc: PV changed from "0.17.01" 
to "0.17.03"
packages/core2-64-poky-linux/stress-ng/stress-ng-doc: PKGV changed from 0.17.01 
[default] to 0.17.03 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-locale: PV changed from 
"0.17.01" to "0.17.03"
packages/core2-64-poky-linux/stress-ng/stress-ng-locale: PKGV changed from 
0.17.01 [default] to 0.17.03 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-src: PKGSIZE changed from 
5005500 to 5056491 (+1%)
packages/core2-64-poky-linux/stress-ng/stress-ng-src: PV changed from "0.17.01" 
to "0.17.03"
packages/core2-64-poky-linux/stress-ng/stress-ng-src: FILELIST: removed 
"/usr/src/debug/stress-ng/0.17.01/stress-oom-pipe.c 
/usr/src/debug/stress-ng/0.17.01/stress-judy.c 
/usr/src/debug/stress-ng/0.17.01/stress-spawn.c 
/usr/src/debug/stress-ng/0.17.01/stress-sigbus.c 
/usr/src/debug/stress-ng/0.17.01/stress-memrate.c 
/usr/src/debug/stress-ng/0.17.01/stress-metamix.c 
/usr/src/debug/stress-ng/0.17.01/stress-iomix.c 
/usr/src/debug/stress-ng/0.17.01/stress-matrix-3d.c 
/usr/src/debug/stress-ng/0.17.01/stress-inotify.c 
/usr/src/debug/stress-ng/0.17.01/stress-null.c 
/usr/src/debug/stress-ng/0.17.01/stress-fpunch.c 
/usr/src/debug/stress-ng/0.17.01/core-io-priority.c 
/usr/src/debug/stress-ng/0.17.01/stress-ptrace.c 
/usr/src/debug/stress-ng/0.17.01/stress-tsc.c 
/usr/src/debug/stress-ng/0.17.01/stress-daemon.c 
/usr/src/debug/stress-ng/0.17.01/core-io-priority.h 
/usr/src/debug/stress-ng/0.17.01/stress-io-uring.c 
/usr/src/debug/stress-ng/0.17.01/stress-trig.c 
/usr/src/debug/stress-ng/0.17.01/stres
 s-funcret.c /usr/src/debug/stress-ng/0.17.01/stress-cpu-online.c 

[OE-core] [AUH] texinfo: upgrading to 7.1 FAILED

2023-12-15 Thread Auto Upgrade Helper
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 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cc1c6d47bb0d16052246dbb7cfe1299d6344c7e8"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cc1c6d47bb0d16052246dbb7cfe1299d6344c7e8"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
Loading cache...done.
Loaded 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cc1c6d47bb0d16052246dbb7cfe1299d6344c7e8"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cc1c6d47bb0d16052246dbb7cfe1299d6344c7e8"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% 
complete)
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: 3 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:03
Adding changed files:  14% |#   | ETA:  0:00:03
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" 
"tp/tests/customization/res_parser/sectioning_directions_split_chapter/sectioning.2"
 

[OE-core] [AUH] libva-utils: upgrading to 2.20.1 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libva-utils* to *2.20.1* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-libva-utils-upgrade-2.20.0-2.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 f6ae04e26b6bee10947fe7423b143fa61aa99d7a Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 10:34:46 +
Subject: [PATCH] libva-utils: upgrade 2.20.0 -> 2.20.1

---
 .../libva/{libva-utils_2.20.0.bb => libva-utils_2.20.1.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/libva/{libva-utils_2.20.0.bb => 
libva-utils_2.20.1.bb} (95%)

diff --git a/meta/recipes-graphics/libva/libva-utils_2.20.0.bb 
b/meta/recipes-graphics/libva/libva-utils_2.20.1.bb
similarity index 95%
rename from meta/recipes-graphics/libva/libva-utils_2.20.0.bb
rename to meta/recipes-graphics/libva/libva-utils_2.20.1.bb
index 2e1fd09406..3bce9a1e32 100644
--- a/meta/recipes-graphics/libva/libva-utils_2.20.0.bb
+++ b/meta/recipes-graphics/libva/libva-utils_2.20.1.bb
@@ -15,7 +15,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b148fc8adf19dc9aec17cf9cd29a9a5e"
 
 SRC_URI = 
"git://github.com/intel/libva-utils.git;branch=v2.20-branch;protocol=https"
-SRCREV = "0c8373e62af3e4d9a3831334c5402ad255797e67"
+SRCREV = "2ad888bb463dc9bfb3deb512ec9faf78f1d3bfa8"
 S = "${WORKDIR}/git"
 
 UPSTREAM_CHECK_GITTAGREGEX = "(?P(\d+(\.\d+)+))$"
-- 
2.42.0

packages/core2-64-poky-linux/libva-utils: PKGV changed from 2.20.0 [default] to 
2.20.1 [default]
packages/core2-64-poky-linux/libva-utils: PV changed from "2.20.0" to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils-dbg: PV changed from 
"2.20.0" to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils-dbg: PKGSIZE changed from 
3195512 to 3200032 (+0%)
packages/core2-64-poky-linux/libva-utils/libva-utils-dbg: PKGV changed from 
2.20.0 [default] to 2.20.1 [default]
packages/core2-64-poky-linux/libva-utils/libva-utils-dev: PV changed from 
"2.20.0" to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils-dev: PKGV changed from 
2.20.0 [default] to 2.20.1 [default]
packages/core2-64-poky-linux/libva-utils/libva-utils-doc: PV changed from 
"2.20.0" to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils-doc: PKGV changed from 
2.20.0 [default] to 2.20.1 [default]
packages/core2-64-poky-linux/libva-utils/libva-utils-locale: PV changed from 
"2.20.0" to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils-locale: PKGV changed from 
2.20.0 [default] to 2.20.1 [default]
packages/core2-64-poky-linux/libva-utils/libva-utils-src: PV changed from 
"2.20.0" to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils-src: PKGSIZE changed from 
4446652 to 4447827 (+0%)
packages/core2-64-poky-linux/libva-utils/libva-utils-src: PKGV changed from 
2.20.0 [default] to 2.20.1 [default]
packages/core2-64-poky-linux/libva-utils/libva-utils-staticdev: PV changed from 
"2.20.0" to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils-staticdev: PKGV changed 
from 2.20.0 [default] to 2.20.1 [default]
packages/core2-64-poky-linux/libva-utils/libva-utils: PV changed from "2.20.0" 
to "2.20.1"
packages/core2-64-poky-linux/libva-utils/libva-utils: PKGV changed from 2.20.0 
[default] to 2.20.1 [default]


0001-libva-utils-upgrade-2.20.0-2.20.1.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192497): 
https://lists.openembedded.org/g/openembedded-core/message/192497
Mute This Topic: https://lists.openembedded.org/mt/103190911/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] weston: upgrading to 13.0.0 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



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

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

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

Regards,
The Upgrade Helper

-- >8 --
>From 4cb15e5704cb09a4691bf271d31809a52b438fba Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 11:14:26 +
Subject: [PATCH] weston: upgrade 12.0.2 -> 13.0.0

---
 .../wayland/{weston_12.0.2.bb => weston_13.0.0.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/wayland/{weston_12.0.2.bb => weston_13.0.0.bb} 
(98%)

diff --git a/meta/recipes-graphics/wayland/weston_12.0.2.bb 
b/meta/recipes-graphics/wayland/weston_13.0.0.bb
similarity index 98%
rename from meta/recipes-graphics/wayland/weston_12.0.2.bb
rename to meta/recipes-graphics/wayland/weston_13.0.0.bb
index 5a179e6770..69638035fb 100644
--- a/meta/recipes-graphics/wayland/weston_12.0.2.bb
+++ b/meta/recipes-graphics/wayland/weston_13.0.0.bb
@@ -13,7 +13,7 @@ SRC_URI = 
"https://gitlab.freedesktop.org/wayland/weston/-/releases/${PV}/downlo
file://systemd-notify.weston-start \
"
 
-SRC_URI[sha256sum] = 
"eb686a7cf00992a23b17f192fca9a887313e92c346ee35d8575196983d656b4a"
+SRC_URI[sha256sum] = 
"52ff1d4aa2394a2e416c85a338b627ce97fa71d43eb762fd4aaf145d36fc795a"
 
 UPSTREAM_CHECK_URI = "https://wayland.freedesktop.org/releases.html;
 UPSTREAM_CHECK_REGEX = "weston-(?P\d+\.\d+\.(?!9\d+)\d+)"
-- 
2.42.0



0001-weston-upgrade-12.0.2-13.0.0.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1843 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (910 cached, 1 parsed). 1842 targets, 38 
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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cf470c5b663c79fa6d930dcbe6a37b93674afb59"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cf470c5b663c79fa6d930dcbe6a37b93674afb59"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 402 Local 391 Mirrors 0 Missed 11 Current 757 (97% 
match, 99% complete)
NOTE: Executing Tasks
NOTE: Running setscene task 850 of 1159 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/wayland/weston_13.0.0.bb:do_recipe_qa_setscene)
NOTE: recipe weston-13.0.0-r0: task do_recipe_qa_setscene: Started
NOTE: recipe weston-13.0.0-r0: task do_recipe_qa_setscene: Succeeded
NOTE: Setscene tasks completed
NOTE: Running task 2757 of 3150 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/wayland/weston_13.0.0.bb:do_fetch)
NOTE: Running task 2902 of 3150 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/wayland/weston_13.0.0.bb:do_write_config)
NOTE: recipe weston-13.0.0-r0: task do_fetch: Started
NOTE: recipe weston-13.0.0-r0: task do_fetch: Succeeded
NOTE: Running task 3129 of 3150 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/wayland/weston_13.0.0.bb:do_unpack)
NOTE: Running task 3130 of 3150 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/wayland/weston_13.0.0.bb:do_prepare_recipe_sysroot)
NOTE: recipe weston-13.0.0-r0: task do_write_config: Started
NOTE: recipe weston-13.0.0-r0: task do_write_config: Succeeded
NOTE: recipe weston-13.0.0-r0: task do_unpack: Started
NOTE: recipe weston-13.0.0-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe weston-13.0.0-r0: task do_unpack: Succeeded
NOTE: Running task 3131 of 3150 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-graphics/wayland/weston_13.0.0.bb:do_patch)
NOTE: Running task 3132 of 3150 

[OE-core] [AUH] cairo: upgrading to 1.18.0 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe cairo failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-31414c872fd6be7a75dc039f946d79fc7a362e5a"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:31414c872fd6be7a75dc039f946d79fc7a362e5a"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-31414c872fd6be7a75dc039f946d79fc7a362e5a"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:31414c872fd6be7a75dc039f946d79fc7a362e5a"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   6% |##  | ETA:  0:00:02
Adding changed files:  13% || ETA:  0:00:01
Adding changed files:  20% |### | ETA:  0:00:01
Adding changed files:  26% |#   | ETA:  0:00:01
Adding changed files:  33% || ETA:  0:00:00
Adding changed files:  40% |##  | ETA:  0:00:00
Adding changed files:  46% || ETA:  0:00:00
Adding changed files:  53% |### | ETA:  0:00:00
Adding changed files:  60% |#   | ETA:  0:00:00
Adding changed files:  66% || ETA:  0:00:00
Adding changed files:  73% |##  | ETA:  0:00:00
Adding changed files:  80% || ETA:  0:00:00
Adding changed files:  86% |### | ETA:  0:00:00
Adding changed files:  93% |#   | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:01
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching http://cairographics.org/releases/cairo-1.18.0.tar.xz...
INFO: Rebasing devtool onto c54da499abc3df7d4b925403b0885a1ed57868e3
WARNING: Command 'git rebase c54da499abc3df7d4b925403b0885a1ed57868e3' failed:
Auto-merging src/cairo-arc.c
CONFLICT (content): Merge conflict in src/cairo-arc.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/cairo
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/cairo/cairo_1.18.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 (#192494): 
https://lists.openembedded.org/g/openembedded-core/message/192494
Mute 

[OE-core] [AUH] libsecret: upgrading to 0.21.2 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-libsecret-upgrade-0.21.1-0.21.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 3a31bf1adc800d3b9c404f6e4d1970c97d14bd00 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 10:26:52 +
Subject: [PATCH] libsecret: upgrade 0.21.1 -> 0.21.2

---
 .../libsecret/{libsecret_0.21.1.bb => libsecret_0.21.2.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-gnome/libsecret/{libsecret_0.21.1.bb => 
libsecret_0.21.2.bb} (91%)

diff --git a/meta/recipes-gnome/libsecret/libsecret_0.21.1.bb 
b/meta/recipes-gnome/libsecret/libsecret_0.21.2.bb
similarity index 91%
rename from meta/recipes-gnome/libsecret/libsecret_0.21.1.bb
rename to meta/recipes-gnome/libsecret/libsecret_0.21.2.bb
index f762d7c343..2d8ea952c5 100644
--- a/meta/recipes-gnome/libsecret/libsecret_0.21.1.bb
+++ b/meta/recipes-gnome/libsecret/libsecret_0.21.2.bb
@@ -13,7 +13,7 @@ inherit gnomebase gi-docgen vala gobject-introspection 
manpages
 
 DEPENDS += "glib-2.0 libgcrypt gettext-native"
 
-SRC_URI[archive.sha256sum] = 
"674f51323a5f74e4cb7e3277da68b5afddd333eca25bc9fd2d820a92972f90b1"
+SRC_URI[archive.sha256sum] = 
"e4a341496a0815e64c8d3b8fabab33d7bae7efdeab77b843669731d5b181dcee"
 
 GTKDOC_MESON_OPTION = 'gtk_doc'
 
-- 
2.42.0



0001-libsecret-upgrade-0.21.1-0.21.2.patch
Description: Binary data
packages/core2-64-poky-linux/libsecret: PKGV changed from 0.21.1 [default] to 
0.21.2 [default]
packages/core2-64-poky-linux/libsecret: PV changed from "0.21.1" to "0.21.2"
packages/core2-64-poky-linux/libsecret: SRC_URI changed from 
"https://download.gnome.org/sources//libsecret/0.21/libsecret-0.21.1.tar.xz;name=archive;
 to 
"https://download.gnome.org/sources//libsecret/0.21/libsecret-0.21.2.tar.xz;name=archive;
packages/core2-64-poky-linux/libsecret/libsecret-dbg: PKGV changed from 0.21.1 
[default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-dbg: PV changed from "0.21.1" 
to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-dbg: PKGSIZE changed from 
1175720 to 1185384 (+1%)
packages/core2-64-poky-linux/libsecret/libsecret-dev: PKGV changed from 0.21.1 
[default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-dev: PV changed from "0.21.1" 
to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-dev: PKGSIZE changed from 
669619 to 673348 (+1%)
packages/core2-64-poky-linux/libsecret/libsecret-doc: PKGV changed from 0.21.1 
[default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-doc: PV changed from "0.21.1" 
to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-locale-ab: PKGV changed from 
0.21.1 [default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-ab: PV changed from 
"0.21.1" to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-locale-an: PKGV changed from 
0.21.1 [default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-an: PV changed from 
"0.21.1" to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-locale-ar: PKGV changed from 
0.21.1 [default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-ar: PV changed from 
"0.21.1" to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-locale-as: PKGV changed from 
0.21.1 [default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-as: PV changed from 
"0.21.1" to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-locale-be: PKGV changed from 
0.21.1 [default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-be: PV changed from 
"0.21.1" to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-locale-bg: PKGV changed from 
0.21.1 [default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-bg: PV changed from 
"0.21.1" to "0.21.2"
packages/core2-64-poky-linux/libsecret/libsecret-locale-bs: PKGV changed from 
0.21.1 [default] to 0.21.2 [default]
packages/core2-64-poky-linux/libsecret/libsecret-locale-bs: PV changed from 
"0.21.1" to "0.21.2"

[OE-core] [AUH] kmscube: upgrading to 96d63eb59e34c647cda1cbb489265f8c536ae055 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-kmscube-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 cb04c5d698d62e3002432c371e4489f5c7e6f9fd Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 10:31:05 +
Subject: [PATCH] kmscube: upgrade to latest revision

---
 meta/recipes-graphics/kmscube/kmscube_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/kmscube/kmscube_git.bb 
b/meta/recipes-graphics/kmscube/kmscube_git.bb
index 4cdc0f06bb..aab582281a 100644
--- a/meta/recipes-graphics/kmscube/kmscube_git.bb
+++ b/meta/recipes-graphics/kmscube/kmscube_git.bb
@@ -10,7 +10,7 @@ DEPENDS = "virtual/libgles3 virtual/libgles2 virtual/egl 
libdrm virtual/libgbm"
 
 LIC_FILES_CHKSUM = 
"file://kmscube.c;beginline=1;endline=23;md5=8b309d4ee67b7315ff7381270dd631fb"
 
-SRCREV = "ea6c5d1eeefbfb0a1c27ab74a6e4621f1d9adf4c"
+SRCREV = "96d63eb59e34c647cda1cbb489265f8c536ae055"
 SRC_URI = 
"git://gitlab.freedesktop.org/mesa/kmscube;branch=master;protocol=https"
 
 UPSTREAM_CHECK_COMMITS = "1"
-- 
2.42.0

packages/core2-64-poky-linux/kmscube/kmscube-dbg: PKGSIZE changed from 320496 
to 351120 (+10%)
packages/core2-64-poky-linux/kmscube/kmscube-src: FILELIST: added 
"/usr/src/debug/kmscube/git/cube-gears.c"
packages/core2-64-poky-linux/kmscube/kmscube-src: PKGSIZE changed from 4583630 
to 4610159 (+1%)
packages/core2-64-poky-linux/kmscube/kmscube: PKGSIZE changed from 1565256 to 
1585736 (+1%)


0001-kmscube-upgrade-to-latest-revision.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192499): 
https://lists.openembedded.org/g/openembedded-core/message/192499
Mute This Topic: https://lists.openembedded.org/mt/103190913/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] vala: upgrading to 0.56.14 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-vala-upgrade-0.56.13-0.56.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 c884ece976694441b1e314ba7ec0c94908fdfc27 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 09:30:02 +
Subject: [PATCH] vala: upgrade 0.56.13 -> 0.56.14

---
 meta/recipes-devtools/vala/{vala_0.56.13.bb => vala_0.56.14.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/vala/{vala_0.56.13.bb => vala_0.56.14.bb} (18%)

diff --git a/meta/recipes-devtools/vala/vala_0.56.13.bb 
b/meta/recipes-devtools/vala/vala_0.56.14.bb
similarity index 18%
rename from meta/recipes-devtools/vala/vala_0.56.13.bb
rename to meta/recipes-devtools/vala/vala_0.56.14.bb
index 0d43ac59a0..3240214bf8 100644
--- a/meta/recipes-devtools/vala/vala_0.56.13.bb
+++ b/meta/recipes-devtools/vala/vala_0.56.14.bb
@@ -1,3 +1,3 @@
 require ${BPN}.inc
 
-SRC_URI[sha256sum] = 
"4988223036c7e1e4874c476d0de8bd9cbe500ee25ef19a76e560dc0b6d56ae07"
+SRC_URI[sha256sum] = 
"9382c268ca9bdc02aaedc8152a9818bf3935273041f629c56de410e360a3f557"
-- 
2.42.0



0001-vala-upgrade-0.56.13-0.56.14.patch
Description: Binary data
packages/core2-64-poky-linux/vala: PV changed from "0.56.13" to "0.56.14"
packages/core2-64-poky-linux/vala: PKGV changed from 0.56.13 [default] to 
0.56.14 [default]
packages/core2-64-poky-linux/vala: SRC_URI changed from 
"http://ftp.gnome.org/pub/GNOME/sources/vala/0.56/vala-0.56.13.tar.xz; to 
"http://ftp.gnome.org/pub/GNOME/sources/vala/0.56/vala-0.56.14.tar.xz;
packages/core2-64-poky-linux/vala/vala-dbg: PV changed from "0.56.13" to 
"0.56.14"
packages/core2-64-poky-linux/vala/vala-dbg: PKGSIZE changed from 18890736 to 
18896200 (+0%)
packages/core2-64-poky-linux/vala/vala-dbg: PKGV changed from 0.56.13 [default] 
to 0.56.14 [default]
packages/core2-64-poky-linux/vala/vala-dev: PV changed from "0.56.13" to 
"0.56.14"
packages/core2-64-poky-linux/vala/vala-dev: PKGV changed from 0.56.13 [default] 
to 0.56.14 [default]
packages/core2-64-poky-linux/vala/vala-doc: PV changed from "0.56.13" to 
"0.56.14"
packages/core2-64-poky-linux/vala/vala-doc: PKGSIZE changed from 10313 to 10319 
(+0%)
packages/core2-64-poky-linux/vala/vala-doc: PKGV changed from 0.56.13 [default] 
to 0.56.14 [default]
packages/core2-64-poky-linux/vala/vala-locale: PV changed from "0.56.13" to 
"0.56.14"
packages/core2-64-poky-linux/vala/vala-locale: PKGV changed from 0.56.13 
[default] to 0.56.14 [default]
packages/core2-64-poky-linux/vala/vala-src: PV changed from "0.56.13" to 
"0.56.14"
packages/core2-64-poky-linux/vala/vala-src: PKGSIZE changed from 15804520 to 
15810014 (+0%)
packages/core2-64-poky-linux/vala/vala-src: PKGV changed from 0.56.13 [default] 
to 0.56.14 [default]
packages/core2-64-poky-linux/vala/vala-staticdev: PV changed from "0.56.13" to 
"0.56.14"
packages/core2-64-poky-linux/vala/vala-staticdev: PKGV changed from 0.56.13 
[default] to 0.56.14 [default]
packages/core2-64-poky-linux/vala/vala: PV changed from "0.56.13" to "0.56.14"
packages/core2-64-poky-linux/vala/vala: PKGSIZE changed from 12324414 to 
12344976 (+0%)
packages/core2-64-poky-linux/vala/vala: PKGV changed from 0.56.13 [default] to 
0.56.14 [default]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192490): 
https://lists.openembedded.org/g/openembedded-core/message/192490
Mute This Topic: https://lists.openembedded.org/mt/103190904/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-samples: upgrading to 2be6f826269be1731cf9f8631b4f4d97364164f8 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to 
*2be6f826269be1731cf9f8631b4f4d97364164f8* has Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe vulkan-samples failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cf470c5b663c79fa6d930dcbe6a37b93674afb59"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cf470c5b663c79fa6d930dcbe6a37b93674afb59"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto 2be6f826269be1731cf9f8631b4f4d97364164f8
WARNING: Command 'git rebase 2be6f826269be1731cf9f8631b4f4d97364164f8' 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 81ac86e9
   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 (#192498): 
https://lists.openembedded.org/g/openembedded-core/message/192498
Mute This Topic: https://lists.openembedded.org/mt/103190912/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] lsof: upgrading to 4.99.0 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-lsof-upgrade-4.98.0-4.99.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 7509a0425b09a524c28d90e9e6c8f83d24e8e68d Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 09:38:55 +
Subject: [PATCH] lsof: upgrade 4.98.0 -> 4.99.0

---
 .../lsof/files/remove-host-information.patch| 17 +
 .../lsof/{lsof_4.98.0.bb => lsof_4.99.0.bb} |  2 +-
 2 files changed, 14 insertions(+), 5 deletions(-)
 rename meta/recipes-extended/lsof/{lsof_4.98.0.bb => lsof_4.99.0.bb} (96%)

diff --git a/meta/recipes-extended/lsof/files/remove-host-information.patch 
b/meta/recipes-extended/lsof/files/remove-host-information.patch
index fb90366ffa..f01db7de24 100644
--- a/meta/recipes-extended/lsof/files/remove-host-information.patch
+++ b/meta/recipes-extended/lsof/files/remove-host-information.patch
@@ -1,3 +1,8 @@
+From d6548f6ff5a7ebeba07c93135ddf934da20daee8 Mon Sep 17 00:00:00 2001
+From: Ross Burton 
+Date: Wed, 30 Aug 2017 15:05:16 +0800
+Subject: [PATCH] lsof: remove host information from version.h
+
 lsof doesn't embed the username or hostname in the build if SOURCE_DATE_EPOCH 
is
 defined, but this still embeds build paths.  Delete all of the host details to
 ensure that no host information is leaked into the binary.
@@ -5,10 +10,14 @@ ensure that no host information is leaked into the binary.
 Upstream-Status: Inappropriate
 Signed-off-by: Ross Burton 
 
-diff --git a/dialects/linux/Makefile b/dialects/linux/Makefile
-index 176a4c2..ef5a633 100644
 a/dialects/linux/Makefile
-+++ b/dialects/linux/Makefile
+---
+ lib/dialects/linux/Makefile | 69 ++---
+ 1 file changed, 11 insertions(+), 58 deletions(-)
+
+diff --git a/lib/dialects/linux/Makefile b/lib/dialects/linux/Makefile
+index f8adaa6..7a79ca7 100644
+--- a/lib/dialects/linux/Makefile
 b/lib/dialects/linux/Makefile
 @@ -83,64 +83,17 @@ ${LIB}: FRC
  version.h:FRC
@echo Constructing version.h
diff --git a/meta/recipes-extended/lsof/lsof_4.98.0.bb 
b/meta/recipes-extended/lsof/lsof_4.99.0.bb
similarity index 96%
rename from meta/recipes-extended/lsof/lsof_4.98.0.bb
rename to meta/recipes-extended/lsof/lsof_4.99.0.bb
index 835ce3b8df..e4b187745d 100644
--- a/meta/recipes-extended/lsof/lsof_4.98.0.bb
+++ b/meta/recipes-extended/lsof/lsof_4.99.0.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=a48ac97a8550eff12395a2c0d6151510"
 
 SRC_URI = "git://github.com/lsof-org/lsof;branch=master;protocol=https \
file://remove-host-information.patch"
-SRCREV = "546eb1c9910e7c137fdff551683c35a736021e05"
+SRCREV = "2015d742527ebdded8c5694edcf3ac2a01ce76ab"
 
 S = "${WORKDIR}/git"
 
-- 
2.42.0



0001-lsof-upgrade-4.98.0-4.99.0.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (910 cached, 1 parsed). 1842 targets, 38 
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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-5fad32ccb600ac11c33feba97b57efb4dd3b07dd"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:5fad32ccb600ac11c33feba97b57efb4dd3b07dd"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 101 Local 90 Mirrors 0 Missed 11 Current 197 (89% match, 
96% complete)
NOTE: Executing Tasks
NOTE: Running setscene task 205 of 298 

[OE-core] [AUH] gawk: upgrading to 5.3.0 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-gawk-upgrade-5.2.2-5.3.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 37e9d664057b848fb3ff6a0560584d6145586a9d Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 09:36:33 +
Subject: [PATCH] gawk: upgrade 5.2.2 -> 5.3.0

---
 meta/recipes-extended/gawk/{gawk_5.2.2.bb => gawk_5.3.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/gawk/{gawk_5.2.2.bb => gawk_5.3.0.bb} (97%)

diff --git a/meta/recipes-extended/gawk/gawk_5.2.2.bb 
b/meta/recipes-extended/gawk/gawk_5.3.0.bb
similarity index 97%
rename from meta/recipes-extended/gawk/gawk_5.2.2.bb
rename to meta/recipes-extended/gawk/gawk_5.3.0.bb
index 3c18b6911a..3d652da6e5 100644
--- a/meta/recipes-extended/gawk/gawk_5.2.2.bb
+++ b/meta/recipes-extended/gawk/gawk_5.3.0.bb
@@ -19,7 +19,7 @@ SRC_URI = "${GNU_MIRROR}/gawk/gawk-${PV}.tar.gz \
file://run-ptest \
"
 
-SRC_URI[sha256sum] = 
"945aef7ccff101f20b22a10802bc005e994ab2b8ea3e724cc1a197c62f41f650"
+SRC_URI[sha256sum] = 
"378f8864ec21cfceaa048f7e1869ac9b4597b449087caf1eb55e440d30273336"
 
 inherit autotools gettext texinfo update-alternatives
 
-- 
2.42.0



0001-gawk-upgrade-5.2.2-5.3.0.patch
Description: Binary data
packages/core2-64-poky-linux/gawk/gawk-dbg: PKGV changed from 5.2.2 [default] 
to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-dbg: PKGSIZE changed from 2538304 to 
2552080 (+1%)
packages/core2-64-poky-linux/gawk/gawk-dbg: PV changed from "5.2.2" to "5.3.0"
packages/core2-64-poky-linux/gawk/gawk-dev: PKGV changed from 5.2.2 [default] 
to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-dev: PKGSIZE changed from 42070 to 42138 
(+0%)
packages/core2-64-poky-linux/gawk/gawk-dev: PV changed from "5.2.2" to "5.3.0"
packages/core2-64-poky-linux/gawk/gawk-doc: PKGV changed from 5.2.2 [default] 
to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-doc: PKGSIZE changed from 2338623 to 
2352307 (+1%)
packages/core2-64-poky-linux/gawk/gawk-doc: PV changed from "5.2.2" to "5.3.0"
packages/core2-64-poky-linux/gawk/gawk-gawkbug: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-gawkbug: PV changed from "5.2.2" to 
"5.3.0"
packages/core2-64-poky-linux/gawk/gawk-locale-bg: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-locale-bg: PKGSIZE changed from 124398 
to 125283 (+1%)
packages/core2-64-poky-linux/gawk/gawk-locale-bg: PV changed from "5.2.2" to 
"5.3.0"
packages/core2-64-poky-linux/gawk/gawk-locale-ca: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-locale-ca: PKGSIZE changed from 51283 to 
51046 (-0%)
packages/core2-64-poky-linux/gawk/gawk-locale-ca: PV changed from "5.2.2" to 
"5.3.0"
packages/core2-64-poky-linux/gawk/gawk-locale-da: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-locale-da: PKGSIZE changed from 36122 to 
36004 (-0%)
packages/core2-64-poky-linux/gawk/gawk-locale-da: PV changed from "5.2.2" to 
"5.3.0"
packages/core2-64-poky-linux/gawk/gawk-locale-de: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-locale-de: PKGSIZE changed from 96121 to 
96695 (+1%)
packages/core2-64-poky-linux/gawk/gawk-locale-de: PV changed from "5.2.2" to 
"5.3.0"
packages/core2-64-poky-linux/gawk/gawk-locale-es: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-locale-es: PKGSIZE changed from 94596 to 
95192 (+1%)
packages/core2-64-poky-linux/gawk/gawk-locale-es: PV changed from "5.2.2" to 
"5.3.0"
packages/core2-64-poky-linux/gawk/gawk-locale-fi: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-locale-fi: PKGSIZE changed from 56651 to 
56396 (-0%)
packages/core2-64-poky-linux/gawk/gawk-locale-fi: PV changed from "5.2.2" to 
"5.3.0"
packages/core2-64-poky-linux/gawk/gawk-locale-fr: PKGV changed from 5.2.2 
[default] to 5.3.0 [default]
packages/core2-64-poky-linux/gawk/gawk-locale-fr: PKGSIZE changed from 96365 to 
96983 

[OE-core] [AUH] systemd-bootchart: upgrading to 235 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe systemd-bootchart failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1846 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
INFO: Extracting current version source...
INFO: SRC_URI contains some conditional appends/prepends - will create branches 
to represent these
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto 8ab9680a1bd5eb8fe7a7dcc44897af7ee41e56e7
WARNING: Command 'git rebase 8ab9680a1bd5eb8fe7a7dcc44897af7ee41e56e7' failed:
Auto-merging src/architecture.h
CONFLICT (content): Merge conflict in src/architecture.h

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

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/systemd-bootchart
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/systemd-bootchart/systemd-bootchart_235.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 (#192491): 
https://lists.openembedded.org/g/openembedded-core/message/192491
Mute This Topic: https://lists.openembedded.org/mt/103190905/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] valgrind: upgrading to 3.22.0 FAILED

2023-12-15 Thread Auto Upgrade Helper
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 5af8f8263601c7f12264583dbd486f5f8ed43037 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 09:32:38 +
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..7592ce5e47 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 c0c6f7b87023a2136b0e04fd589853638ec4bbf6 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] ovmf: upgrading to edk2-stable202311 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 
0001-ovmf-upgrade-edk2-stable202308-edk2-stable202311.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 f41b84d6846d5a10625732a154f2312b0eef613e Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 06:05:54 +
Subject: [PATCH] ovmf: upgrade edk2-stable202308 -> edk2-stable202311

---
 ...ovmf-update-path-to-native-BaseTools.patch | 10 ++-
 ...ile-adjust-to-build-in-under-bitbake.patch |  6 +-
 .../ovmf/ovmf/0003-debug-prefix-map.patch | 24 ---
 .../ovmf/ovmf/0004-reproducible.patch | 18 +++---
 ...005-Committing-changes-from-do_patch.patch | 64 +++
 meta/recipes-core/ovmf/ovmf_git.bb|  5 +-
 6 files changed, 92 insertions(+), 35 deletions(-)
 create mode 100644 
meta/recipes-core/ovmf/ovmf/0005-Committing-changes-from-do_patch.patch

diff --git 
a/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch 
b/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch
index 490d9e8046..0620cb5649 100644
--- 
a/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch
+++ 
b/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch
@@ -1,7 +1,7 @@
-From d8df6b6433351763e1db791dd84d432983d2b249 Mon Sep 17 00:00:00 2001
+From 8b90b9f928bd1b806a87d9713d78d3423bec0fbd Mon Sep 17 00:00:00 2001
 From: Ricardo Neri 
 Date: Thu, 9 Jun 2016 02:23:01 -0700
-Subject: [PATCH 1/4] ovmf: update path to native BaseTools
+Subject: [PATCH] ovmf: update path to native BaseTools
 
 BaseTools is a set of utilities to build EDK-based firmware. These utilities
 are used during the build process. Thus, they need to be built natively.
@@ -11,12 +11,13 @@ with the appropriate location before building.
 
 Signed-off-by: Ricardo Neri 
 Upstream-Status: Inappropriate [oe-core cross compile specific]
+
 ---
  OvmfPkg/build.sh | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/OvmfPkg/build.sh b/OvmfPkg/build.sh
-index b0334fb76e..094f86f096 100755
+index 279f0d099a..285f061bf4 100755
 --- a/OvmfPkg/build.sh
 +++ b/OvmfPkg/build.sh
 @@ -24,7 +24,7 @@ then
@@ -28,6 +29,3 @@ index b0334fb76e..094f86f096 100755
echo $EDK_TOOLS_PATH
source edksetup.sh BaseTools
  else
--- 
-2.30.2
-
diff --git 
a/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
 
b/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
index eeedc9e20f..b6c19c1ad5 100644
--- 
a/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
+++ 
b/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
@@ -1,4 +1,4 @@
-From ac9df4fb92965f1f95a5bdbde5f2f86d0c569711 Mon Sep 17 00:00:00 2001
+From b139c8863bf52ed0956bcab148bd1d27d6fb90dd Mon Sep 17 00:00:00 2001
 From: Ricardo Neri 
 Date: Fri, 26 Jul 2019 17:34:26 -0400
 Subject: [PATCH] BaseTools: makefile: adjust to build in under bitbake
@@ -13,6 +13,7 @@ to fight against how upstream wants to configure the build.
 
 Signed-off-by: Ricardo Neri 
 Upstream-Status: Inappropriate [needs to be converted to in-recipe fixups]
+
 ---
  BaseTools/Source/C/Makefiles/header.makefile | 15 +++
  1 file changed, 7 insertions(+), 8 deletions(-)
@@ -64,6 +65,3 @@ index d369908a09..22c670f316 100644
  ifeq ($(HOST_ARCH), IA32)
  #
  # Snow Leopard  is a 32-bit and 64-bit environment. uname -m returns i386, 
but gcc defaults
--- 
-2.30.2
-
diff --git a/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch 
b/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch
index c0c763c1cf..4680061482 100644
--- a/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch
+++ b/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch
@@ -1,7 +1,7 @@
-From 03e536b20d0b72cf078052f6748de8df3836625c Mon Sep 17 00:00:00 2001
+From 454469c0f8dced4e25d7828214b4e8b68c80b650 Mon Sep 17 00:00:00 2001
 From: Alexander Kanavin 
 Date: Mon, 14 Jun 2021 19:56:28 +0200
-Subject: [PATCH 3/4] debug prefix map

[OE-core] [AUH] shadow: upgrading to 4.14.2 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe shadow failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cba4f033a2e6938cb7535b739557f4d49c342ff4"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cba4f033a2e6938cb7535b739557f4d49c342ff4"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
Loading cache...done.
Loaded 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cba4f033a2e6938cb7535b739557f4d49c342ff4"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cba4f033a2e6938cb7535b739557f4d49c342ff4"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% 
complete)
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: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:  13% || ETA:  0:00:00
Adding changed files:  26% |#   | ETA:  0:00:00
Adding changed files:  39% |##  | ETA:  0:00:00
Adding changed files:  52% |##  | ETA:  0:00:00
Adding changed files:  65% |### | ETA:  0:00:00
Adding changed files:  78% || ETA:  0:00:00
Adding changed files:  91% || ETA:  0:00:00
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/shadow-maint/shadow/releases/download/4.14.2/shadow-4.14.2.tar.gz...
INFO: Rebasing devtool onto 0722440aab5508c1acf0e027b22d97d4468708bd
WARNING: Command 'git rebase 0722440aab5508c1acf0e027b22d97d4468708bd' failed:
Auto-merging src/login.c
CONFLICT (content): Merge conflict in src/login.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Rebasing devtool-override-class-native onto 
0722440aab5508c1acf0e027b22d97d4468708bd
WARNING: Command 'git rebase 0722440aab5508c1acf0e027b22d97d4468708bd' failed:
Auto-merging src/login.c
CONFLICT (content): Merge conflict in src/login.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Rebasing devtool-override-class-nativesdk onto 
0722440aab5508c1acf0e027b22d97d4468708bd
WARNING: Command 'git rebase 0722440aab5508c1acf0e027b22d97d4468708bd' failed:
Auto-merging src/login.c
CONFLICT (content): Merge conflict in src/login.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Rebasing devtool-override-class-target onto 
0722440aab5508c1acf0e027b22d97d4468708bd
WARNING: Command 'git rebase 0722440aab5508c1acf0e027b22d97d4468708bd' failed:
Auto-merging src/login.c
CONFLICT (content): Merge conflict in src/login.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded 

[OE-core] [AUH] rust: upgrading to 1.74.1 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe rust failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1845 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1845 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 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:07:27
Adding changed files:   0% || ETA:  0:05:18
Adding changed files:   0% || ETA:  0:04:33
Adding changed files:   0% || ETA:  0:04:17
Adding changed files:   0% || ETA:  0:04:02
Adding changed files:   1% || ETA:  0:03:51
Adding changed files:   1% || ETA:  0:03:45
Adding changed files:   1% || ETA:  0:03:38
Adding changed files:   1% || ETA:  0:03:35
Adding changed files:   1% || ETA:  0:03:34
Adding changed files:   1% || ETA:  0:03:32
Adding changed files:   2% || ETA:  0:03:29
Adding changed files:   2% || ETA:  0:03:27
Adding changed files:   2% || ETA:  0:03:25
Adding changed files:   2% || ETA:  0:03:23
Adding changed files:   2% || ETA:  0:03:21
Adding changed files:   2% |#   | ETA:  0:03:19
Adding changed files:   3% |#   | ETA:  0:03:19
Adding changed files:   3% |#   | ETA:  0:03:18
Adding changed files:   3% |#   | ETA:  0:03:17
Adding changed files:   3% |#   | ETA:  0:03:16
Adding changed files:   3% |#   | ETA:  0:03:15
Adding changed files:   3% |#   | ETA:  0:03:13
Adding changed files:   4% |#   | ETA:  0:03:13
Adding changed files:   4% |#   | ETA:  0:03:13
Adding changed files:   4% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:10
Adding changed files:   4% |#   | ETA:  0:03:09
Adding changed files:   4% |# 

[OE-core] [AUH] go-helloworld: upgrading to 1d6d2400d4027025cb8edc86a139c9c581d672f7 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-helloworld* to 
*1d6d2400d4027025cb8edc86a139c9c581d672f7* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade go-helloworld -S 
1d6d2400d4027025cb8edc86a139c9c581d672f7
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-5fad32ccb600ac11c33feba97b57efb4dd3b07dd"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:5fad32ccb600ac11c33feba97b57efb4dd3b07dd"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
ERROR: Execution of 'git checkout 1d6d2400d4027025cb8edc86a139c9c581d672f7' 
failed with exit code 128:
fatal: reference is not a tree: 1d6d2400d4027025cb8edc86a139c9c581d672f7



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 (#192487): 
https://lists.openembedded.org/g/openembedded-core/message/192487
Mute This Topic: https://lists.openembedded.org/mt/103190901/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] cargo: upgrading to 1.74.1 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe cargo failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 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:07:05
Adding changed files:   0% || ETA:  0:04:58
Adding changed files:   0% || ETA:  0:04:18
Adding changed files:   0% || ETA:  0:04:06
Adding changed files:   0% || ETA:  0:03:54
Adding changed files:   1% || ETA:  0:03:45
Adding changed files:   1% || ETA:  0:03:40
Adding changed files:   1% || ETA:  0:03:34
Adding changed files:   1% || ETA:  0:03:31
Adding changed files:   1% || ETA:  0:03:31
Adding changed files:   1% || ETA:  0:03:30
Adding changed files:   2% || ETA:  0:03:28
Adding changed files:   2% || ETA:  0:03:25
Adding changed files:   2% || ETA:  0:03:24
Adding changed files:   2% || ETA:  0:03:22
Adding changed files:   2% || ETA:  0:03:20
Adding changed files:   2% |#   | ETA:  0:03:18
Adding changed files:   3% |#   | ETA:  0:03:17
Adding changed files:   3% |#   | ETA:  0:03:17
Adding changed files:   3% |#   | ETA:  0:03:16
Adding changed files:   3% |#   | ETA:  0:03:15
Adding changed files:   3% |#   | ETA:  0:03:13
Adding changed files:   3% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:11
Adding changed files:   4% |#   | ETA:  0:03:09
Adding changed files:   4% |#   | ETA:  0:03:08
Adding changed files:   4% |#   

[OE-core] [AUH] repo: upgrading to 2.40 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-repo-upgrade-2.39-2.40.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 df547f0aa122c8666d926e5d966231fe16a96f54 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 08:44:23 +
Subject: [PATCH] repo: upgrade 2.39 -> 2.40

---
 meta/recipes-devtools/repo/repo/0001-python3-shebang.patch | 7 +++
 meta/recipes-devtools/repo/{repo_2.39.bb => repo_2.40.bb}  | 2 +-
 2 files changed, 4 insertions(+), 5 deletions(-)
 rename meta/recipes-devtools/repo/{repo_2.39.bb => repo_2.40.bb} (95%)

diff --git a/meta/recipes-devtools/repo/repo/0001-python3-shebang.patch 
b/meta/recipes-devtools/repo/repo/0001-python3-shebang.patch
index fba89a32d8..45a94ed258 100644
--- a/meta/recipes-devtools/repo/repo/0001-python3-shebang.patch
+++ b/meta/recipes-devtools/repo/repo/0001-python3-shebang.patch
@@ -1,4 +1,4 @@
-From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 2001
+From 67dac528bdc065c16cb19c2e6c1f80703e52fd52 Mon Sep 17 00:00:00 2001
 From: Jasper Orschulko 
 Date: Tue, 14 Sep 2021 16:46:51 +0200
 Subject: [PATCH] python3 shebang
@@ -8,12 +8,13 @@ python to python3.
 
 Upstream-Status: Inappropriate [configuration]
 Signed-off-by: Jasper Orschulko 
+
 ---
  repo | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/repo b/repo
-index b13e34c..205e0e5 100755
+index 2dd9dd9..f5a4041 100755
 --- a/repo
 +++ b/repo
 @@ -1,4 +1,4 @@
@@ -22,5 +23,3 @@ index b13e34c..205e0e5 100755
  #
  # Copyright (C) 2008 The Android Open Source Project
  #
---
-2.33.0
diff --git a/meta/recipes-devtools/repo/repo_2.39.bb 
b/meta/recipes-devtools/repo/repo_2.40.bb
similarity index 95%
rename from meta/recipes-devtools/repo/repo_2.39.bb
rename to meta/recipes-devtools/repo/repo_2.40.bb
index a0633a5cbb..e749ee1b76 100644
--- a/meta/recipes-devtools/repo/repo_2.39.bb
+++ b/meta/recipes-devtools/repo/repo_2.40.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
 SRC_URI = 
"git://gerrit.googlesource.com/git-repo.git;protocol=https;branch=main \
file://0001-python3-shebang.patch \
"
-SRCREV = "b99272c601bc5f466c3cfc782bb852c2c967ad27"
+SRCREV = "4c80921d22c20a28d531c9e3e8a0ce4433c6509d"
 
 MIRRORS += "git://gerrit.googlesource.com/git-repo.git 
git://github.com/GerritCodeReview/git-repo.git"
 
-- 
2.42.0

packages/core2-64-poky-linux/repo: PV changed from "2.39" to "2.40"
packages/core2-64-poky-linux/repo: PKGV changed from 2.39 [default] to 2.40 
[default]
packages/core2-64-poky-linux/repo/repo-dbg: PV changed from "2.39" to "2.40"
packages/core2-64-poky-linux/repo/repo-dbg: PKGV changed from 2.39 [default] to 
2.40 [default]
packages/core2-64-poky-linux/repo/repo-dev: PV changed from "2.39" to "2.40"
packages/core2-64-poky-linux/repo/repo-dev: PKGV changed from 2.39 [default] to 
2.40 [default]
packages/core2-64-poky-linux/repo/repo-doc: PV changed from "2.39" to "2.40"
packages/core2-64-poky-linux/repo/repo-doc: PKGV changed from 2.39 [default] to 
2.40 [default]
packages/core2-64-poky-linux/repo/repo-locale: PV changed from "2.39" to "2.40"
packages/core2-64-poky-linux/repo/repo-locale: PKGV changed from 2.39 [default] 
to 2.40 [default]
packages/core2-64-poky-linux/repo/repo-src: PV changed from "2.39" to "2.40"
packages/core2-64-poky-linux/repo/repo-src: PKGV changed from 2.39 [default] to 
2.40 [default]
packages/core2-64-poky-linux/repo/repo-staticdev: PV changed from "2.39" to 
"2.40"
packages/core2-64-poky-linux/repo/repo-staticdev: PKGV changed from 2.39 
[default] to 2.40 [default]
packages/core2-64-poky-linux/repo/repo: PKGSIZE changed from 48604 to 48178 
(-1%)
packages/core2-64-poky-linux/repo/repo: PV changed from "2.39" to "2.40"
packages/core2-64-poky-linux/repo/repo: PKGV changed from 2.39 [default] to 
2.40 [default]


0001-repo-upgrade-2.39-2.40.patch
Description: Binary data

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

[OE-core] [AUH] rpm: upgrading to 4.19.1 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe rpm failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto 98b301ebb44fb5cabb56fc24bc3aaa437c47c038
WARNING: Command 'git rebase 98b301ebb44fb5cabb56fc24bc3aaa437c47c038' failed:
Auto-merging python/header-py.c
CONFLICT (content): Merge conflict in python/header-py.c
Auto-merging python/rpmds-py.c
CONFLICT (content): Merge conflict in python/rpmds-py.c
CONFLICT (modify/delete): python/rpmfi-py.c deleted in HEAD and modified in 
84cda9af2 (Add bunch of deprecation/obsoletion warnings to python bindings).  
Version 84cda9af2 (Add bunch of deprecation/obsoletion warnings to python 
bindings) of python/rpmfi-py.c left in tree.
Auto-merging python/rpmmodule.c
CONFLICT (content): Merge conflict in python/rpmmodule.c
Auto-merging python/rpmts-py.c
CONFLICT (content): Merge conflict in python/rpmts-py.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/rpm
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/rpm/rpm_4.19.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 (#192480): 
https://lists.openembedded.org/g/openembedded-core/message/192480
Mute This Topic: https://lists.openembedded.org/mt/103190894/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



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

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe rust-llvm failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1844 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1844 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 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:07:16
Adding changed files:   0% || ETA:  0:05:04
Adding changed files:   0% || ETA:  0:04:22
Adding changed files:   0% || ETA:  0:04:09
Adding changed files:   0% || ETA:  0:03:57
Adding changed files:   1% || ETA:  0:03:48
Adding changed files:   1% || ETA:  0:03:43
Adding changed files:   1% || ETA:  0:03:37
Adding changed files:   1% || ETA:  0:03:34
Adding changed files:   1% || ETA:  0:03:33
Adding changed files:   1% || ETA:  0:03:32
Adding changed files:   2% || ETA:  0:03:29
Adding changed files:   2% || ETA:  0:03:27
Adding changed files:   2% || ETA:  0:03:27
Adding changed files:   2% || ETA:  0:03:24
Adding changed files:   2% || ETA:  0:03:23
Adding changed files:   2% |#   | ETA:  0:03:21
Adding changed files:   3% |#   | ETA:  0:03:20
Adding changed files:   3% |#   | ETA:  0:03:19
Adding changed files:   3% |#   | ETA:  0:03:18
Adding changed files:   3% |#   | ETA:  0:03:17
Adding changed files:   3% |#   | ETA:  0:03:16
Adding changed files:   3% |#   | ETA:  0:03:15
Adding changed files:   4% |#   | ETA:  0:03:14
Adding changed files:   4% |#   | ETA:  0:03:14
Adding changed files:   4% |#   | ETA:  0:03:13
Adding changed files:   4% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:11
Adding changed files:   4% |#   

[OE-core] [AUH] qemu: upgrading to 8.1.3 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-qemu-upgrade-8.1.2-8.1.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 2f84e0edbe372f23089ed8cd1fbdfcee7fc33d33 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 08:41:39 +
Subject: [PATCH] qemu: upgrade 8.1.2 -> 8.1.3

---
 meta/recipes-devtools/qemu/qemu.inc   |  2 +-
 ...n-environment-space-to-boot-loader-q.patch | 12 ++--
 ...ce-use-of-lfs64-related-functions-an.patch | 60 +--
 .../0003-apic-fixup-fallthrough-to-PIC.patch  | 14 ++---
 ...dd-pkg-config-handling-for-libgcrypt.patch | 12 ++--
 ...mu-Do-not-include-file-if-not-exists.patch | 12 ++--
 ...er-space-mmap-tweaks-to-address-musl.patch | 15 +++--
 .../qemu/0007-qemu-Determinism-fixes.patch| 14 ++---
 ...d-use-relative-path-to-refer-to-file.patch | 12 ++--
 ...and-MAP_SHARED_VALIDATE-on-needed-li.patch | 12 ++--
 ...t-against-buggy-or-malicious-guest-d.patch | 21 +++
 meta/recipes-devtools/qemu/qemu/cross.patch   | 16 ++---
 .../qemu/qemu/fixedmeson.patch| 17 --
 meta/recipes-devtools/qemu/qemu/fixmips.patch | 21 +--
 .../qemu/{qemu_8.1.2.bb => qemu_8.1.3.bb} |  0
 15 files changed, 129 insertions(+), 111 deletions(-)
 rename meta/recipes-devtools/qemu/{qemu_8.1.2.bb => qemu_8.1.3.bb} (100%)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 5ab2cb83b4..d6a3cf47b9 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -37,7 +37,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
 
-SRC_URI[sha256sum] = 
"541526a764576eb494d2ff5ec46aeb253e62ea29035d1c23c0a8af4e6cd4f087"
+SRC_URI[sha256sum] = 
"43cc176804105586f74f90398f34e9f85787dff400d3b640d81f7779fbe265bb"
 
 SRC_URI:append:class-target = " file://cross.patch"
 SRC_URI:append:class-nativesdk = " file://cross.patch"
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-qemu-Add-addition-environment-space-to-boot-loader-q.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-qemu-Add-addition-environment-space-to-boot-loader-q.patch
index c65508017d..3d3086b4b3 100644
--- 
a/meta/recipes-devtools/qemu/qemu/0001-qemu-Add-addition-environment-space-to-boot-loader-q.patch
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-qemu-Add-addition-environment-space-to-boot-loader-q.patch
@@ -1,7 +1,7 @@
-From de64af82950a6908f9407dfc92b83c17e2af3eab Mon Sep 17 00:00:00 2001
+From bee9d0ff821e5124364caf5c528068e03a757cb8 Mon Sep 17 00:00:00 2001
 From: Jason Wessel 
 Date: Fri, 28 Mar 2014 17:42:43 +0800
-Subject: [PATCH 01/12] qemu: Add addition environment space to boot loader
+Subject: [PATCH] qemu: Add addition environment space to boot loader
  qemu-system-mips
 
 Upstream-Status: Inappropriate - OE uses deep paths
@@ -18,10 +18,10 @@ Signed-off-by: Roy Li 
  hw/mips/malta.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
-Index: qemu-8.0.0/hw/mips/malta.c
-===
 qemu-8.0.0.orig/hw/mips/malta.c
-+++ qemu-8.0.0/hw/mips/malta.c
+diff --git a/hw/mips/malta.c b/hw/mips/malta.c
+index f9618fa5f..dd2dd35e5 100644
+--- a/hw/mips/malta.c
 b/hw/mips/malta.c
 @@ -64,7 +64,7 @@
  #define ENVP_PADDR  0x2000
  #define ENVP_VADDR  cpu_mips_phys_to_kseg0(NULL, ENVP_PADDR)
diff --git 
a/meta/recipes-devtools/qemu/qemu/0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch
 
b/meta/recipes-devtools/qemu/qemu/0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch
index ceae67be64..dca7a239c8 100644
--- 
a/meta/recipes-devtools/qemu/qemu/0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch
+++ 
b/meta/recipes-devtools/qemu/qemu/0002-linux-user-Replace-use-of-lfs64-related-functions-an.patch
@@ -1,8 +1,7 @@
-From 71f14902256e3c3529710b713e1ea43100bf4c40 Mon Sep 17 00:00:00 2001
+From d242e9b872231285ab3f1ed5c26406ef055012e3 Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Sat, 17 Dec 2022 08:37:46 -0800
-Subject: [PATCH 2/2] linux-user: Replace 

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

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe libstd-rs failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1843 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1843 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-3bb688de751df35afebb89f057ea1eace62d"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:3bb688de751df35afebb89f057ea1eace62d"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 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:07:08
Adding changed files:   0% || ETA:  0:05:04
Adding changed files:   0% || ETA:  0:04:24
Adding changed files:   0% || ETA:  0:04:10
Adding changed files:   0% || ETA:  0:03:58
Adding changed files:   1% || ETA:  0:03:49
Adding changed files:   1% || ETA:  0:03:44
Adding changed files:   1% || ETA:  0:03:37
Adding changed files:   1% || ETA:  0:03:34
Adding changed files:   1% || ETA:  0:03:33
Adding changed files:   1% || ETA:  0:03:31
Adding changed files:   2% || ETA:  0:03:28
Adding changed files:   2% || ETA:  0:03:26
Adding changed files:   2% || ETA:  0:03:25
Adding changed files:   2% || ETA:  0:03:23
Adding changed files:   2% || ETA:  0:03:21
Adding changed files:   2% |#   | ETA:  0:03:19
Adding changed files:   3% |#   | ETA:  0:03:18
Adding changed files:   3% |#   | ETA:  0:03:17
Adding changed files:   3% |#   | ETA:  0:03:16
Adding changed files:   3% |#   | ETA:  0:03:15
Adding changed files:   3% |#   | ETA:  0:03:14
Adding changed files:   3% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:12
Adding changed files:   4% |#   | ETA:  0:03:11
Adding changed files:   4% |#   | ETA:  0:03:10
Adding changed files:   4% |#   | ETA:  0:03:08
Adding changed files:   4% |#   

[OE-core] [AUH] python3: upgrading to 3.12.1 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

The following devtool command failed:  upgrade python3 -V 3.12.1
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-5d58d8048040feffda703385a7726b6e274897a8"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:5d58d8048040feffda703385a7726b6e274897a8"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-5d58d8048040feffda703385a7726b6e274897a8"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:5d58d8048040feffda703385a7726b6e274897a8"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   3% |#   | ETA:  0:00:05
Adding changed files:   7% |##  | ETA:  0:00:03
Adding changed files:  11% |### | ETA:  0:00:02
Adding changed files:  14% |#   | ETA:  0:00:02
Adding changed files:  18% |##  | ETA:  0:00:02
Adding changed files:  22% |### | ETA:  0:00:02
Adding changed files:  25% |#   | ETA:  0:00:02
Adding changed files:  29% |##  | ETA:  0:00:01
Adding changed files:  33% |### | ETA:  0:00:01
Adding changed files:  36% |#   | ETA:  0:00:01
Adding changed files:  40% |##  | ETA:  0:00:01
Adding changed files:  44% |### | ETA:  0:00:01
Adding changed files:  47% |#   | ETA:  0:00:01
Adding changed files:  51% |##  | ETA:  0:00:01
Adding changed files:  55% |### | ETA:  0:00:01
Adding changed files:  58% |#   | ETA:  0:00:01
Adding changed files:  62% |##  | ETA:  0:00:00
Adding changed files:  66% |### | ETA:  0:00:00
Adding changed files:  69% |#   | ETA:  0:00:00
Adding changed files:  73% |##  | ETA:  0:00:00
Adding changed files:  77% |### | ETA:  0:00:00
Adding changed files:  81% |#   | ETA:  0:00:00
Adding changed files:  84% |##  | ETA:  0:00:00
Adding changed files:  88% |### | ETA:  0:00:00
Adding changed files:  92% |#   | ETA:  0:00:00
Adding changed files:  95% |##  | ETA:  0:00:00
Adding changed files:  99% |### | ETA:  0:00:00
Adding changed files: 100% 

[OE-core] [AUH] python3-hatchling: upgrading to 1.20.0 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.18.0-1.20.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 d1eb21a56816de5838bb7501706631ae3983bd96 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 07:50:34 +
Subject: [PATCH] python3-hatchling: upgrade 1.18.0 -> 1.20.0

---
 ...{python3-hatchling_1.18.0.bb => python3-hatchling_1.20.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-hatchling_1.18.0.bb => 
python3-hatchling_1.20.0.bb} (85%)

diff --git a/meta/recipes-devtools/python/python3-hatchling_1.18.0.bb 
b/meta/recipes-devtools/python/python3-hatchling_1.20.0.bb
similarity index 85%
rename from meta/recipes-devtools/python/python3-hatchling_1.18.0.bb
rename to meta/recipes-devtools/python/python3-hatchling_1.20.0.bb
index c94e49dab3..6c1db9b801 100644
--- a/meta/recipes-devtools/python/python3-hatchling_1.18.0.bb
+++ b/meta/recipes-devtools/python/python3-hatchling_1.20.0.bb
@@ -8,7 +8,7 @@ inherit pypi python_hatchling
 DEPENDS += "python3-pluggy-native python3-pathspec-native 
python3-packaging-native python3-editables-native 
python3-trove-classifiers-native"
 DEPENDS:remove:class-native = "python3-hatchling-native"
 
-SRC_URI[sha256sum] = 
"50e99c3110ce0afc3f7bdbadff1c71c17758e476731c27607940cfa6686489ca"
+SRC_URI[sha256sum] = 
"0e0893cbe3d5f9275fc0e5b629087fc23b17abd7065e4db0a310e0a0237bc945"
 
 do_compile:prepend() {
 export PYTHONPATH=src
-- 
2.42.0

packages/core2-64-poky-linux/python3-hatchling: PV changed from "1.18.0" to 
"1.20.0"
packages/core2-64-poky-linux/python3-hatchling: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/h/hatchling/hatchling-1.18.0.tar.gz;downloadfilename=hatchling-1.18.0.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/h/hatchling/hatchling-1.20.0.tar.gz;downloadfilename=hatchling-1.20.0.tar.gz;
packages/core2-64-poky-linux/python3-hatchling: PKGV changed from 1.18.0 
[default] to 1.20.0 [default]
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-dbg: PV 
changed from "1.18.0" to "1.20.0"
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-dbg: PKGV 
changed from 1.18.0 [default] to 1.20.0 [default]
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-dev: PV 
changed from "1.18.0" to "1.20.0"
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-dev: PKGV 
changed from 1.18.0 [default] to 1.20.0 [default]
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-doc: PV 
changed from "1.18.0" to "1.20.0"
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-doc: PKGV 
changed from 1.18.0 [default] to 1.20.0 [default]
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-locale: PV 
changed from "1.18.0" to "1.20.0"
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-locale: PKGV 
changed from 1.18.0 [default] to 1.20.0 [default]
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-src: PV 
changed from "1.18.0" to "1.20.0"
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-src: PKGV 
changed from 1.18.0 [default] to 1.20.0 [default]
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-staticdev: PV 
changed from "1.18.0" to "1.20.0"
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling-staticdev: 
PKGV changed from 1.18.0 [default] to 1.20.0 [default]
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling: PV changed 
from "1.18.0" to "1.20.0"
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling: PKGSIZE 
changed from 680784 to 680489 (-0%)
packages/core2-64-poky-linux/python3-hatchling/python3-hatchling: PKGV changed 
from 1.18.0 [default] to 1.20.0 [default]
Changes to packages/core2-64-poky-linux/python3-hatchling (sysroot):
  /usr/lib/python3.11/site-packages/hatchling-1.18.0.dist-info moved to 
/usr/lib/python3.11/site-packages/hatchling-1.20.0.dist-info
Changes to packages/x86_64-linux/python3-hatchling-native (sysroot):
  /usr/lib/python3.11/site-packages/hatchling-1.18.0.dist-info moved to 

[OE-core] [AUH] python3-dtschema: upgrading to 2023.11 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-python3-dtschema-upgrade-2023.7-2023.11.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 12bbc6bcb0d59da0d2a64e739f4612fbf955c800 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 07:47:35 +
Subject: [PATCH] python3-dtschema: upgrade 2023.7 -> 2023.11

---
 .../{python3-dtschema_2023.7.bb => python3-dtschema_2023.11.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-dtschema_2023.7.bb => 
python3-dtschema_2023.11.bb} (85%)

diff --git a/meta/recipes-devtools/python/python3-dtschema_2023.7.bb 
b/meta/recipes-devtools/python/python3-dtschema_2023.11.bb
similarity index 85%
rename from meta/recipes-devtools/python/python3-dtschema_2023.7.bb
rename to meta/recipes-devtools/python/python3-dtschema_2023.11.bb
index c1dc3e019a..5453d96f8a 100644
--- a/meta/recipes-devtools/python/python3-dtschema_2023.7.bb
+++ b/meta/recipes-devtools/python/python3-dtschema_2023.11.bb
@@ -7,7 +7,7 @@ inherit pypi setuptools3
 
 PYPI_PACKAGE = "dtschema"
 
-SRC_URI[sha256sum] = 
"de7cd73a35244cf76a8cdd9919bbeb31f362aa5744f3c76c80e0e612489dd0c0"
+SRC_URI[sha256sum] = 
"cf9a449ea743c0a955cf6034ef246668fa5ea177684977c61fef7604af5f273b"
 
 DEPENDS += "python3-setuptools-scm-native"
 RDEPENDS:${PN} += "\
-- 
2.42.0



0001-python3-dtschema-upgrade-2023.7-2023.11.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1845 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (910 cached, 1 parsed). 1842 targets, 38 
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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-2d27714166974a5afb77333b4fc5ac808129aa1b"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:2d27714166974a5afb77333b4fc5ac808129aa1b"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 383 Local 373 Mirrors 0 Missed 10 Current 406 (97% 
match, 98% complete)
NOTE: Executing Tasks
NOTE: Running setscene task 434 of 789 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtc_1.7.0.bb:do_create_spdx_setscene)
NOTE: Running setscene task 442 of 789 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtschema_2023.11.bb:do_populate_lic_setscene)
NOTE: Running setscene task 444 of 789 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtschema_2023.11.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 454 of 789 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-jsonschema_4.17.3.bb:do_create_spdx_setscene)
NOTE: Running setscene task 461 of 789 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-rfc3987_1.3.8.bb:do_create_spdx_setscene)
NOTE: Running setscene task 462 of 789 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-ruamel-yaml_0.17.35.bb:do_create_spdx_setscene)
NOTE: recipe python3-dtc-1.7.0-r0: task do_create_spdx_setscene: Started
NOTE: recipe python3-dtschema-2023.11-r0: task 
do_deploy_source_date_epoch_setscene: Started
NOTE: recipe python3-dtschema-2023.11-r0: task do_populate_lic_setscene: Started
NOTE: recipe python3-rfc3987-1.3.8-r0: task do_create_spdx_setscene: Started
NOTE: recipe python3-jsonschema-4.17.3-r0: task do_create_spdx_setscene: Started
NOTE: recipe python3-ruamel-yaml-0.17.35-r0: task do_create_spdx_setscene: 
Started
NOTE: recipe 

[OE-core] [AUH] gdb: upgrading to 14.1 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

The following devtool command failed:  finish -f gdb 
/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/gdb
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1843 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (911 cached, 1 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-64 sysroot...done.

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

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 349, in 

ret = main()
  ^^
  File "/home/pokybuild/yocto-worker/auh/build/scripts/devtool", line 336, in 
main
ret = args.func(args, config, basepath, workspace)
  
  File 
"/home/pokybuild/yocto-worker/auh/build/scripts/lib/devtool/standard.py", line 
2217, in finish
updated, appendfile, removed = _update_recipe(args.recipename, workspace, 
rd, args.mode, appendlayerdir, wildcard_version=True, no_remove=False, 
no_report_remove=removing_original, initial_rev=args.initial_rev, 
dry_run_outdir=dry_run_outdir, no_overrides=args.no_overrides, 
force_patch_refresh=args.force_patch_refresh)
   

  File 
"/home/pokybuild/yocto-worker/auh/build/scripts/lib/devtool/standard.py", line 
1913, in _update_recipe
updated, appendf, removed = _update_recipe_patch(recipename, workspace, 
srctree, crd, appendlayerdir, wildcard_version, no_remove, no_report_remove, 
initial_rev, dry_run_outdir, force_patch_refresh)

^^
  File 
"/home/pokybuild/yocto-worker/auh/build/scripts/lib/devtool/standard.py", line 
1749, in _update_recipe_patch
appendfile, destpath = oe.recipeutils.bbappend_recipe(
   ^^^
  File "/home/pokybuild/yocto-worker/auh/build/meta/lib/oe/recipeutils.py", 
line 721, in bbappend_recipe
appendpath, pathok = get_bbappend_path(rd, destlayerdir, wildcardver)
 
  File "/home/pokybuild/yocto-worker/auh/build/meta/lib/oe/recipeutils.py", 
line 630, in get_bbappend_path
confdata = bb.cookerdata.parse_config_file(destlayerconf, confdata)
   
  File "/home/pokybuild/yocto-worker/auh/build/bitbake/lib/bb/cookerdata.py", 
line 174, in wrapped
raise bb.BBHandledException()
bb.BBHandledException


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

Regards,
The Upgrade Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: 

[OE-core] [AUH] librepo: upgrading to 1.17.0 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe librepo failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1845 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-620e59afc97ca8bed845ffbdeb0a08224b885c0c"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:620e59afc97ca8bed845ffbdeb0a08224b885c0c"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto ae727d99086f70f39fba5695af5460e1da908c1b
WARNING: Command 'git rebase ae727d99086f70f39fba5695af5460e1da908c1b' failed:
Auto-merging CMakeLists.txt
CONFLICT (content): Merge conflict in 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/librepo
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/librepo/librepo_1.17.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 (#192459): 
https://lists.openembedded.org/g/openembedded-core/message/192459
Mute This Topic: https://lists.openembedded.org/mt/103190872/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] ttyrun: upgrading to 2.30.0 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-ttyrun-upgrade-2.29.0-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 2d25fc60df53b37f321cb6247972dd2ef8087dd4 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 06:11:18 +
Subject: [PATCH] ttyrun: upgrade 2.29.0 -> 2.30.0

---
 meta/recipes-core/ttyrun/{ttyrun_2.29.0.bb => ttyrun_2.30.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-core/ttyrun/{ttyrun_2.29.0.bb => ttyrun_2.30.0.bb} (93%)

diff --git a/meta/recipes-core/ttyrun/ttyrun_2.29.0.bb 
b/meta/recipes-core/ttyrun/ttyrun_2.30.0.bb
similarity index 93%
rename from meta/recipes-core/ttyrun/ttyrun_2.29.0.bb
rename to meta/recipes-core/ttyrun/ttyrun_2.30.0.bb
index e0956b9ac6..73c6c58c9d 100644
--- a/meta/recipes-core/ttyrun/ttyrun_2.29.0.bb
+++ b/meta/recipes-core/ttyrun/ttyrun_2.30.0.bb
@@ -7,7 +7,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=f5118f167b055bfd7c3450803f1847af"
 
 SRC_URI = 
"git://github.com/ibm-s390-linux/s390-tools;protocol=https;branch=master"
-SRCREV = "d9ce54dee3ac3827e76624352293a83eb05c727e"
+SRCREV = "c217f6be6addd4d008f110efa53fbec79681dbfd"
 
 S = "${WORKDIR}/git"
 
-- 
2.42.0



0001-ttyrun-upgrade-2.29.0-2.30.0.patch
Description: Binary data
packages/core2-64-poky-linux/ttyrun: PKGV changed from 2.29.0 [default] to 
2.30.0 [default]
packages/core2-64-poky-linux/ttyrun: PV changed from "2.29.0" to "2.30.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-dbg: PKGV changed from 2.29.0 
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-dbg: PV changed from "2.29.0" to 
"2.30.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-dev: PKGV changed from 2.29.0 
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-dev: PV changed from "2.29.0" to 
"2.30.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-doc: PKGV changed from 2.29.0 
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-doc: PV changed from "2.29.0" to 
"2.30.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-locale: PKGV changed from 2.29.0 
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-locale: PV changed from "2.29.0" to 
"2.30.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-src: PKGV changed from 2.29.0 
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-src: PV changed from "2.29.0" to 
"2.30.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-staticdev: PKGV changed from 2.29.0 
[default] to 2.30.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-staticdev: PV changed from "2.29.0" 
to "2.30.0"
packages/core2-64-poky-linux/ttyrun/ttyrun: PKGV changed from 2.29.0 [default] 
to 2.30.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun: PV changed from "2.29.0" to "2.30.0"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192449): 
https://lists.openembedded.org/g/openembedded-core/message/192449
Mute This Topic: https://lists.openembedded.org/mt/103190862/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-runtime: upgrading to 1.21.5 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe go-runtime failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1843 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-620e59afc97ca8bed845ffbdeb0a08224b885c0c"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:620e59afc97ca8bed845ffbdeb0a08224b885c0c"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
Loading cache...done.
Loaded 1843 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-620e59afc97ca8bed845ffbdeb0a08224b885c0c"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:620e59afc97ca8bed845ffbdeb0a08224b885c0c"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% 
complete)
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: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   2% || ETA:  0:00:05
Adding changed files:   4% |#   | ETA:  0:00:03
Adding changed files:   7% |##  | ETA:  0:00:03
Adding changed files:   9% |### | ETA:  0:00:03
Adding changed files:  12% || ETA:  0:00:02
Adding changed files:  14% |#   | ETA:  0:00:02
Adding changed files:  17% |##  | ETA:  0:00:02
Adding changed files:  19% |### | ETA:  0:00:02
Adding changed files:  22% || ETA:  0:00:02
Adding changed files:  24% || ETA:  0:00:02
Adding changed files:  27% |#   | ETA:  0:00:02
Adding changed files:  29% |##  | ETA:  0:00:02
Adding changed files:  32% |### | ETA:  0:00:02
Adding changed files:  34% || ETA:  0:00:02
Adding changed files:  37% |#   | ETA:  0:00:02
Adding changed files:  39% |##  | ETA:  0:00:02
Adding changed files:  42% |### | ETA:  0:00:02
Adding changed files:  44% || ETA:  0:00:01
Adding changed files:  46% || ETA:  0:00:01
Adding changed files:  49% |#   | ETA:  0:00:01
Adding changed files:  51% |##  | ETA:  0:00:01
Adding changed files:  54% |### | ETA:  0:00:01
Adding changed files:  56% || ETA:  0:00:01
Adding changed files:  59% |#   | ETA:  0:00:01
Adding changed files:  61% |##  | ETA:  0:00:01
Adding changed files:  64% |### | ETA:  0:00:01
Adding changed files:  66% || ETA:  0:00:01
Adding changed files:  69% || ETA:  0:00:01
Adding changed files:  71% 

[OE-core] [AUH] go: upgrading to 1.21.5 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe go failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1844 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-620e59afc97ca8bed845ffbdeb0a08224b885c0c"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:620e59afc97ca8bed845ffbdeb0a08224b885c0c"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
Loading cache...done.
Loaded 1844 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-620e59afc97ca8bed845ffbdeb0a08224b885c0c"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:620e59afc97ca8bed845ffbdeb0a08224b885c0c"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% 
complete)
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: 3 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   2% || ETA:  0:00:05
Adding changed files:   4% |#   | ETA:  0:00:03
Adding changed files:   7% |##  | ETA:  0:00:03
Adding changed files:   9% |### | ETA:  0:00:03
Adding changed files:  12% || ETA:  0:00:02
Adding changed files:  14% |#   | ETA:  0:00:02
Adding changed files:  17% |##  | ETA:  0:00:02
Adding changed files:  19% |### | ETA:  0:00:02
Adding changed files:  22% || ETA:  0:00:02
Adding changed files:  24% || ETA:  0:00:02
Adding changed files:  27% |#   | ETA:  0:00:02
Adding changed files:  29% |##  | ETA:  0:00:02
Adding changed files:  32% |### | ETA:  0:00:02
Adding changed files:  34% || ETA:  0:00:02
Adding changed files:  37% |#   | ETA:  0:00:02
Adding changed files:  39% |##  | ETA:  0:00:02
Adding changed files:  42% |### | ETA:  0:00:02
Adding changed files:  44% || ETA:  0:00:01
Adding changed files:  46% || ETA:  0:00:01
Adding changed files:  49% |#   | ETA:  0:00:01
Adding changed files:  51% |##  | ETA:  0:00:01
Adding changed files:  54% |### | ETA:  0:00:01
Adding changed files:  56% || ETA:  0:00:01
Adding changed files:  59% |#   | ETA:  0:00:01
Adding changed files:  61% |##  | ETA:  0:00:01
Adding changed files:  64% |### | ETA:  0:00:01
Adding changed files:  66% || ETA:  0:00:01
Adding changed files:  69% || ETA:  0:00:01
Adding changed files:  71% |#   

[OE-core] [AUH] pkgconf: upgrading to 2.1.0 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-pkgconf-upgrade-2.0.3-2.1.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 ad430f2217755c12d924d795c71d592b76e19587 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 07:27:27 +
Subject: [PATCH] pkgconf: upgrade 2.0.3 -> 2.1.0

---
 .../pkgconf/{pkgconf_2.0.3.bb => pkgconf_2.1.0.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/pkgconf/{pkgconf_2.0.3.bb => pkgconf_2.1.0.bb} 
(96%)

diff --git a/meta/recipes-devtools/pkgconf/pkgconf_2.0.3.bb 
b/meta/recipes-devtools/pkgconf/pkgconf_2.1.0.bb
similarity index 96%
rename from meta/recipes-devtools/pkgconf/pkgconf_2.0.3.bb
rename to meta/recipes-devtools/pkgconf/pkgconf_2.1.0.bb
index 5aa5a191f2..1921f3a086 100644
--- a/meta/recipes-devtools/pkgconf/pkgconf_2.0.3.bb
+++ b/meta/recipes-devtools/pkgconf/pkgconf_2.1.0.bb
@@ -20,7 +20,7 @@ SRC_URI = "\
 file://pkg-config-native.in \
 file://pkg-config-esdk.in \
 "
-SRC_URI[sha256sum] = 
"cabdf3c474529854f7ccce8573c5ac68ad34a7e621037535cbc3981f6b23836c"
+SRC_URI[sha256sum] = 
"266d5861ee51c52bc710293a1d36622ae16d048d71ec56034a02eb9cf9677761"
 
 inherit autotools
 
-- 
2.42.0



0001-pkgconf-upgrade-2.0.3-2.1.0.patch
Description: Binary data
packages/core2-64-poky-linux/pkgconf: PKGV changed from 2.0.3 [default] to 
2.1.0 [default]
packages/core2-64-poky-linux/pkgconf: SRC_URI changed from 
"https://distfiles.ariadne.space/pkgconf/pkgconf-2.0.3.tar.xz 
file://pkg-config-wrapper file://pkg-config-native.in 
file://pkg-config-esdk.in" to 
"https://distfiles.ariadne.space/pkgconf/pkgconf-2.1.0.tar.xz 
file://pkg-config-wrapper file://pkg-config-native.in file://pkg-config-esdk.in"
packages/core2-64-poky-linux/pkgconf: PV changed from "2.0.3" to "2.1.0"
packages/core2-64-poky-linux/pkgconf/pkgconf-dbg: PKGV changed from 2.0.3 
[default] to 2.1.0 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-dbg: PKGSIZE changed from 310288 
to 314232 (+1%)
packages/core2-64-poky-linux/pkgconf/pkgconf-dbg: PV changed from "2.0.3" to 
"2.1.0"
packages/core2-64-poky-linux/pkgconf/pkgconf-dev: PKGV changed from 2.0.3 
[default] to 2.1.0 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-dev: PKGSIZE changed from 24195 to 
24354 (+1%)
packages/core2-64-poky-linux/pkgconf/pkgconf-dev: PV changed from "2.0.3" to 
"2.1.0"
packages/core2-64-poky-linux/pkgconf/pkgconf-doc: PKGV changed from 2.0.3 
[default] to 2.1.0 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-doc: PV changed from "2.0.3" to 
"2.1.0"
packages/core2-64-poky-linux/pkgconf/pkgconf-locale: PKGV changed from 2.0.3 
[default] to 2.1.0 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-locale: PV changed from "2.0.3" to 
"2.1.0"
packages/core2-64-poky-linux/pkgconf/pkgconf-src: PKGV changed from 2.0.3 
[default] to 2.1.0 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-src: PKGSIZE changed from 269541 
to 273448 (+1%)
packages/core2-64-poky-linux/pkgconf/pkgconf-src: PV changed from "2.0.3" to 
"2.1.0"
packages/core2-64-poky-linux/pkgconf/pkgconf-staticdev: PKGV changed from 2.0.3 
[default] to 2.1.0 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-staticdev: PV changed from "2.0.3" 
to "2.1.0"
packages/core2-64-poky-linux/pkgconf/pkgconf: PKGV changed from 2.0.3 [default] 
to 2.1.0 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf: PKGSIZE changed from 154025 to 
154057 (+0%)
packages/core2-64-poky-linux/pkgconf/pkgconf: PV changed from "2.0.3" to "2.1.0"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192457): 
https://lists.openembedded.org/g/openembedded-core/message/192457
Mute This Topic: https://lists.openembedded.org/mt/103190870/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] dpkg: upgrading to 1.22.1 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-dpkg-upgrade-1.22.0-1.22.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 7c1ec193bcb33b5214a607e4c40b6de180133736 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 06:40:55 +
Subject: [PATCH] dpkg: upgrade 1.22.0 -> 1.22.1

---
 .../0001-Add-support-for-riscv32-CPU.patch | 14 ++
 ...uild.c-ignore-return-of-1-from-tar-cf.patch |  4 ++--
 .../dpkg/0001-dpkg-Support-muslx32-build.patch | 14 ++
 ...wrs-kernel-version-which-has-characte.patch | 11 +--
 ...ts-expect-D-to-be-set-when-running-in.patch |  4 ++--
 ...ction-doesn-t-work-properly-for-all-s.patch | 13 +
 ...-add-musleabi-to-known-target-tripets.patch | 17 +
 c-Remove-usage-of-clamp-mtime-in-tar.patch | 11 ++-
 .../dpkg/dpkg/add_armeb_triplet_entry.patch| 18 ++
 meta/recipes-devtools/dpkg/dpkg/arch_pm.patch  | 11 +++
 meta/recipes-devtools/dpkg/dpkg/noman.patch| 10 ++
 meta/recipes-devtools/dpkg/dpkg/pager.patch| 12 ++--
 .../dpkg/dpkg/remove-tar-no-timestamp.patch| 14 --
 .../dpkg/{dpkg_1.22.0.bb => dpkg_1.22.1.bb}|  2 +-
 14 files changed, 83 insertions(+), 72 deletions(-)
 rename meta/recipes-devtools/dpkg/{dpkg_1.22.0.bb => dpkg_1.22.1.bb} (95%)

diff --git 
a/meta/recipes-devtools/dpkg/dpkg/0001-Add-support-for-riscv32-CPU.patch 
b/meta/recipes-devtools/dpkg/dpkg/0001-Add-support-for-riscv32-CPU.patch
index 52e85705fa..70079420e3 100644
--- a/meta/recipes-devtools/dpkg/dpkg/0001-Add-support-for-riscv32-CPU.patch
+++ b/meta/recipes-devtools/dpkg/dpkg/0001-Add-support-for-riscv32-CPU.patch
@@ -1,20 +1,21 @@
-From 279e4c274f5f295823cf9fa95d3ba131f6d711db Mon Sep 17 00:00:00 2001
+From 068e1c1f58dfc6e127bac84b478ce20b3a21cfbe Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Wed, 29 Apr 2020 22:02:23 -0700
 Subject: [PATCH] Add support for riscv32 CPU
 
 Upstream-Status: Pending
 Signed-off-by: Khem Raj 
+
 ---
  data/cputable | 1 +
  scripts/Dpkg/Vendor/Debian.pm | 1 +
  2 files changed, 2 insertions(+)
 
 diff --git a/data/cputable b/data/cputable
-index 9f2a8e0..1d935b1 100644
+index 575c008e3..7a801a03a 100644
 --- a/data/cputable
 +++ b/data/cputable
-@@ -41,6 +41,7 @@ powerpc  powerpc (powerpc|ppc)   
32  big
+@@ -43,6 +43,7 @@ powerpc  powerpc (powerpc|ppc)   
32  big
  powerpcel powerpcle   powerpcle   32  little
  ppc64 powerpc64   (powerpc|ppc)64 64  big
  ppc64el   powerpc64le powerpc64le 64  little
@@ -23,10 +24,10 @@ index 9f2a8e0..1d935b1 100644
  s390  s390s39032  big
  s390x s390x   s390x   64  big
 diff --git a/scripts/Dpkg/Vendor/Debian.pm b/scripts/Dpkg/Vendor/Debian.pm
-index a352bbd..fa1d90b 100644
+index dcc3cc124..89c9b41c1 100644
 --- a/scripts/Dpkg/Vendor/Debian.pm
 +++ b/scripts/Dpkg/Vendor/Debian.pm
-@@ -306,6 +306,7 @@ sub _add_build_flags {
+@@ -200,6 +200,7 @@ sub set_build_features {
  powerpc
  ppc64
  ppc64el
@@ -34,6 +35,3 @@ index a352bbd..fa1d90b 100644
  riscv64
  s390x
  sparc
--- 
-2.26.2
-
diff --git 
a/meta/recipes-devtools/dpkg/dpkg/0001-build.c-ignore-return-of-1-from-tar-cf.patch
 
b/meta/recipes-devtools/dpkg/dpkg/0001-build.c-ignore-return-of-1-from-tar-cf.patch
index f2367c95e9..6c66fdf565 100644
--- 
a/meta/recipes-devtools/dpkg/dpkg/0001-build.c-ignore-return-of-1-from-tar-cf.patch
+++ 
b/meta/recipes-devtools/dpkg/dpkg/0001-build.c-ignore-return-of-1-from-tar-cf.patch
@@ -1,4 +1,4 @@
-From e3ade3464b8a1129a55c2790cf114d9ae01e3cda Mon Sep 17 00:00:00 2001
+From 8a923b9dfae57fc9b2cab656324c739e8afb9d36 Mon Sep 17 00:00:00 2001
 From: Paul Eggleton 
 Date: Tue, 16 Jun 2020 03:57:25 +
 Subject: [PATCH] build.c: ignore return of 1 from tar -cf
@@ -29,7 +29,7 @@ Signed-off-by: Paul Eggleton 
  1 file changed, 4 insertions(+), 1 deletion(-)
 
 diff --git 

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

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.27.7-3.28.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 006b5129489611d68dec410a145a067692f339dd Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 06:28:32 +
Subject: [PATCH] cmake: upgrade 3.27.7 -> 3.28.1

---
 meta/recipes-devtools/cmake/cmake.inc   | 2 +-
 .../recipes-devtools/cmake/{cmake_3.27.7.bb => cmake_3.28.1.bb} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/cmake/{cmake_3.27.7.bb => cmake_3.28.1.bb} (100%)

diff --git a/meta/recipes-devtools/cmake/cmake.inc 
b/meta/recipes-devtools/cmake/cmake.inc
index ecb0e487df..16bdb34b5e 100644
--- a/meta/recipes-devtools/cmake/cmake.inc
+++ b/meta/recipes-devtools/cmake/cmake.inc
@@ -19,7 +19,7 @@ CMAKE_MAJOR_VERSION = 
"${@'.'.join(d.getVar('PV').split('.')[0:2])}"
 SRC_URI = "https://cmake.org/files/v${CMAKE_MAJOR_VERSION}/cmake-${PV}.tar.gz \
 "
 
-SRC_URI[sha256sum] = 
"08f71a106036bf051f692760ef9558c0577c42ac39e96ba097e7662bd4158d8e"
+SRC_URI[sha256sum] = 
"15e94f83e647f7d620a140a7a5da76349fc47a1bfed66d0f5cdee8e7344079ad"
 
 UPSTREAM_CHECK_REGEX = "cmake-(?P\d+(\.\d+)+)\.tar"
 
diff --git a/meta/recipes-devtools/cmake/cmake_3.27.7.bb 
b/meta/recipes-devtools/cmake/cmake_3.28.1.bb
similarity index 100%
rename from meta/recipes-devtools/cmake/cmake_3.27.7.bb
rename to meta/recipes-devtools/cmake/cmake_3.28.1.bb
-- 
2.42.0

NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1844 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (909 cached, 2 parsed). 1842 targets, 38 
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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-2cd6afaa61f4c0e339ce238406d764c8c8b4b819"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:2cd6afaa61f4c0e339ce238406d764c8c8b4b819"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 205 Local 112 Mirrors 0 Missed 93 Current 209 (54% 
match, 77% complete)
Removing 14 stale sstate objects for arch x86_64...done.
Removing 6 stale sstate objects for arch core2-64...done.
Removing 20 stale sstate objects for arch qemux86_64...done.
NOTE: Executing Tasks
NOTE: Running setscene task 227 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/expat/expat_2.5.0.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 240 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/bzip2/bzip2_1.0.8.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 241 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/libarchive/libarchive_3.7.2.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 246 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/xz/xz_5.4.4.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 250 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/zstd/zstd_1.5.5.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 254 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/acl_2.3.1.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 258 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-support/attr/attr_2.5.1.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 267 of 414 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/ncurses/ncurses_6.4.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene 

[OE-core] [AUH] util-linux-libuuid: upgrading to 2.39.3 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *util-linux-libuuid* to 
*2.39.3* has Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 
0001-util-linux-libuuid-upgrade-2.39.2-2.39.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 f2d399c227d3b098bdf1e8f12a60baa62df2ab55 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 06:15:39 +
Subject: [PATCH] util-linux-libuuid: upgrade 2.39.2 -> 2.39.3

---
 ...2.39.2.bb => util-linux-libuuid_2.39.3.bb} | 29 ++
 meta/recipes-core/util-linux/util-linux.inc   |  5 +--
 ...ls-include-libgen.h-for-basename-API.patch |  9 +++--
 ...Use-4K-buffer-size-instead-of-BUFSIZ.patch | 38 ---
 .../util-linux/avoid_parallel_tests.patch |  4 +-
 .../util-linux/configure-sbindir.patch| 19 +++---
 .../display_testname_for_subtest.patch| 12 +++---
 .../util-linux/util-linux/ptest.patch |  4 +-
 8 files changed, 61 insertions(+), 59 deletions(-)
 rename meta/recipes-core/util-linux/{util-linux-libuuid_2.39.2.bb => 
util-linux-libuuid_2.39.3.bb} (30%)
 delete mode 100644 
meta/recipes-core/util-linux/util-linux/0001-lscpu-Use-4K-buffer-size-instead-of-BUFSIZ.patch

diff --git a/meta/recipes-core/util-linux/util-linux-libuuid_2.39.2.bb 
b/meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
similarity index 30%
rename from meta/recipes-core/util-linux/util-linux-libuuid_2.39.2.bb
rename to meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
index 5d759aed94..687e4327c8 100644
--- a/meta/recipes-core/util-linux/util-linux-libuuid_2.39.2.bb
+++ b/meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
@@ -1,3 +1,32 @@
+# 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:
+#
+# --- README.licensing
+# +++ README.licensing
+# @@ -2,11 +2,13 @@
+#  The project util-linux doesn't use the same license for all of the code.
+#  There is code under:
+#  
+# -   * GPL-3.0-or-later   - GNU General Public License version 3, or any 
later version
+# +   * GPL-1.0-or-later   - GNU General Public License version 1, or any 
later version
+# +
+# +   * GPL-2.0- GNU General Public License version 2
+#  
+# * GPL-2.0-or-later   - GNU General Public License version 2, or any 
later version
+#  
+# -   * GPL-2.0- GNU General Public License version 2
+# +   * GPL-3.0-or-later   - GNU General Public License version 3, or any 
later version
+#  
+# * LGPL-2.1-or-later  - GNU Lesser General Public License 2.1 or any 
later version
+#  
+# 
+#
+
 # To allow util-linux to optionally build-depend on cryptsetup, libuuid is
 # split out of the main recipe, as it's needed by cryptsetup
 
diff --git a/meta/recipes-core/util-linux/util-linux.inc 
b/meta/recipes-core/util-linux/util-linux.inc
index e3bef5acfc..044d9861de 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -12,7 +12,7 @@ LICENSE:${PN}-libfdisk = "LGPL-2.1-or-later"
 LICENSE:${PN}-libmount = "LGPL-2.1-or-later"
 LICENSE:${PN}-libsmartcols = "LGPL-2.1-or-later"
 
-LIC_FILES_CHKSUM = 
"file://README.licensing;md5=12ae7768a65ec8f2e44d930df9cb43fa \
+LIC_FILES_CHKSUM = 
"file://README.licensing;md5=6b0e0a2320e66e62eef9b8149a6faec4 \
 file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
 
file://Documentation/licenses/COPYING.GPL-2.0-or-later;md5=b234ee4d69f5fce4486a80fdaf4a4263
 \
 
file://Documentation/licenses/COPYING.LGPL-2.1-or-later;md5=4fbd65380cdd255951079008b364516c
 \
@@ -35,8 +35,7 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
file://run-ptest \
file://display_testname_for_subtest.patch \
file://avoid_parallel_tests.patch \
-   file://0001-lscpu-Use-4K-buffer-size-instead-of-BUFSIZ.patch \

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

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe systemd-boot failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-63d160d3d0ef4c8e0f59a7b0265d2c77a4a022df"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:63d160d3d0ef4c8e0f59a7b0265d2c77a4a022df"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto db11bab38ccf1ed257f310d29070843d4c58ea01
WARNING: Command 'git rebase db11bab38ccf1ed257f310d29070843d4c58ea01' failed:
Auto-merging src/hibernate-resume/hibernate-resume-generator.c
CONFLICT (content): Merge conflict in 
src/hibernate-resume/hibernate-resume-generator.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/systemd-boot
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/systemd-boot/systemd-boot_255.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 (#192442): 
https://lists.openembedded.org/g/openembedded-core/message/192442
Mute This Topic: https://lists.openembedded.org/mt/103190855/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[OE-core] [AUH] btrfs-tools: upgrading to 6.6.3 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.6.3* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.5.3-6.6.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 6be05680ca595db15b920783bd34b401f87190a6 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 06:25:55 +
Subject: [PATCH] btrfs-tools: upgrade 6.5.3 -> 6.6.3

---
 ...-a-possibility-to-specify-where-python-modules-ar.patch | 7 ---
 .../{btrfs-tools_6.5.3.bb => btrfs-tools_6.6.3.bb} | 2 +-
 2 files changed, 5 insertions(+), 4 deletions(-)
 rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.5.3.bb => 
btrfs-tools_6.6.3.bb} (98%)

diff --git 
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
 
b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
index 5846f04d1a..f7e90de90b 100644
--- 
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
+++ 
b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
@@ -1,4 +1,4 @@
-From d3adfc21c9cc264bd191722f102963cbc4794259 Mon Sep 17 00:00:00 2001
+From 3ef2d48fc8614f1f1d9cffe3ab332272192d05de Mon Sep 17 00:00:00 2001
 From: Alexander Kanavin 
 Date: Wed, 23 May 2018 21:20:35 +0300
 Subject: [PATCH] Add a possibility to specify where python modules are
@@ -6,15 +6,16 @@ Subject: [PATCH] Add a possibility to specify where python 
modules are
 
 Upstream-Status: Inappropriate [oe-core specific to solve multilib use case]
 Signed-off-by: Alexander Kanavin 
+
 ---
  Makefile | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/Makefile b/Makefile
-index 1697794c..8ab38818 100644
+index 374f59b9..ed083f6b 100644
 --- a/Makefile
 +++ b/Makefile
-@@ -651,7 +651,7 @@ endif
+@@ -959,7 +959,7 @@ endif
  ifeq ($(PYTHON_BINDINGS),1)
  install_python: libbtrfsutil_python
$(Q)cd libbtrfsutil/python; \
diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.5.3.bb 
b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.6.3.bb
similarity index 98%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.5.3.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.6.3.bb
index 873d5e7a14..ef40f553fb 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.5.3.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.6.3.bb
@@ -18,7 +18,7 @@ DEPENDS = "util-linux zlib"
 SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master;protocol=https
 \

file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
"
-SRCREV = "a45c360b64660477c726e192d9e92ceb73a50f80"
+SRCREV = "92e18dbce521789e02057d406769b073d474fa72"
 S = "${WORKDIR}/git"
 
 PACKAGECONFIG ??= " \
-- 
2.42.0



0001-btrfs-tools-upgrade-6.5.3-6.6.3.patch
Description: Binary data
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PV changed from 
"6.5.3" to "6.6.3"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGV changed from 
6.5.3 [default] to 6.6.3 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGSIZE changed from 
24925904 to 25012304 (+0%)
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dev: PV changed from 
"6.5.3" to "6.6.3"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dev: PKGV changed from 
6.5.3 [default] to 6.6.3 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-doc: PV changed from 
"6.5.3" to "6.6.3"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-doc: PKGV changed from 
6.5.3 [default] to 6.6.3 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-locale: PV changed from 
"6.5.3" to "6.6.3"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-locale: PKGV changed from 
6.5.3 [default] to 6.6.3 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PV changed from 
"6.5.3" to "6.6.3"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PKGV changed from 
6.5.3 [default] to 6.6.3 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PKGSIZE changed from 
4123002 to 

[OE-core] [AUH] update-rc.d: upgrading to b8f950105010270a768aa12245d6abf166346015 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *update-rc.d* to 
*b8f950105010270a768aa12245d6abf166346015* has Succeeded.

Next steps:
- apply the patch: git am 0001-update-rc.d-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 c02d0fca6cc72c4bd1ccc9bef2e46a5237e6296a Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 06:13:23 +
Subject: [PATCH] update-rc.d: upgrade to latest revision

---
 meta/recipes-core/update-rc.d/update-rc.d_0.8.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb 
b/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb
index 043cb3f13e..ba622fe716 100644
--- a/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb
+++ b/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb
@@ -7,7 +7,7 @@ LICENSE = "GPL-2.0-or-later"
 LIC_FILES_CHKSUM = 
"file://update-rc.d;beginline=5;endline=15;md5=d40a07c27f535425934bb5001f2037d9"
 
 SRC_URI = "git://git.yoctoproject.org/update-rc.d;branch=master;protocol=https"
-SRCREV = "8636cf478d426b568c1be11dbd9346f67e03adac"
+SRCREV = "b8f950105010270a768aa12245d6abf166346015"
 
 UPSTREAM_CHECK_COMMITS = "1"
 
-- 
2.42.0



0001-update-rc.d-upgrade-to-latest-revision.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192440): 
https://lists.openembedded.org/g/openembedded-core/message/192440
Mute This Topic: https://lists.openembedded.org/mt/103190853/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] bluez5: upgrading to 5.71 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Next steps:
- apply the patch: git am 0001-bluez5-upgrade-5.70-5.71.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 625ed6403eaae17065f7a7a136ec806e00b961d3 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 05:14:47 +
Subject: [PATCH] bluez5: upgrade 5.70 -> 5.71

---
 meta/recipes-connectivity/bluez5/bluez5.inc   |   2 -
 .../0001-test-gatt-Fix-hung-issue.patch   |   2 +-
 ...et-for-building-tests-without-runnin.patch |   6 +-
 ...e_probe-failing-if-SDP-record-is-not.patch | 313 --
 ...shared-util.c-include-linux-limits.h.patch |   7 +-
 .../bluez5/bluez5/CVE-2023-45866.patch|  56 
 .../bluez5/{bluez5_5.70.bb => bluez5_5.71.bb} |   2 +-
 7 files changed, 9 insertions(+), 379 deletions(-)
 delete mode 100644 
meta/recipes-connectivity/bluez5/bluez5/0002-input-Fix-.device_probe-failing-if-SDP-record-is-not.patch
 delete mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2023-45866.patch
 rename meta/recipes-connectivity/bluez5/{bluez5_5.70.bb => bluez5_5.71.bb} 
(94%)

diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc 
b/meta/recipes-connectivity/bluez5/bluez5.inc
index 0bb157e202..e10158a6e5 100644
--- a/meta/recipes-connectivity/bluez5/bluez5.inc
+++ b/meta/recipes-connectivity/bluez5/bluez5.inc
@@ -55,8 +55,6 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/bluetooth/bluez-${PV}.tar.xz \

file://0001-tests-add-a-target-for-building-tests-without-runnin.patch \
file://0001-test-gatt-Fix-hung-issue.patch \
file://0004-src-shared-util.c-include-linux-limits.h.patch \
-   
file://0002-input-Fix-.device_probe-failing-if-SDP-record-is-not.patch \
-  file://CVE-2023-45866.patch \
"
 S = "${WORKDIR}/bluez-${PV}"
 
diff --git 
a/meta/recipes-connectivity/bluez5/bluez5/0001-test-gatt-Fix-hung-issue.patch 
b/meta/recipes-connectivity/bluez5/bluez5/0001-test-gatt-Fix-hung-issue.patch
index 06ebf1cde6..3546c7c305 100644
--- 
a/meta/recipes-connectivity/bluez5/bluez5/0001-test-gatt-Fix-hung-issue.patch
+++ 
b/meta/recipes-connectivity/bluez5/bluez5/0001-test-gatt-Fix-hung-issue.patch
@@ -1,4 +1,4 @@
-From 7dcc5f46a31ac4eaa67c0ab3aaae38005db7458f Mon Sep 17 00:00:00 2001
+From e8808a2f5e17d375411c7409eaffb17e72f65022 Mon Sep 17 00:00:00 2001
 From: Mingli Yu 
 Date: Fri, 24 Aug 2018 12:04:03 +0800
 Subject: [PATCH] test-gatt: Fix hung issue
diff --git 
a/meta/recipes-connectivity/bluez5/bluez5/0001-tests-add-a-target-for-building-tests-without-runnin.patch
 
b/meta/recipes-connectivity/bluez5/bluez5/0001-tests-add-a-target-for-building-tests-without-runnin.patch
index 7c47cc1a1e..be05093551 100644
--- 
a/meta/recipes-connectivity/bluez5/bluez5/0001-tests-add-a-target-for-building-tests-without-runnin.patch
+++ 
b/meta/recipes-connectivity/bluez5/bluez5/0001-tests-add-a-target-for-building-tests-without-runnin.patch
@@ -1,4 +1,4 @@
-From a657fddd13a2e756b0af315301f1c44081e2f668 Mon Sep 17 00:00:00 2001
+From 3724958858b0ee430f37fb83388c3737d2039a3a Mon Sep 17 00:00:00 2001
 From: Alexander Kanavin 
 Date: Fri, 1 Apr 2016 17:07:34 +0300
 Subject: [PATCH] tests: add a target for building tests without running them
@@ -11,10 +11,10 @@ Signed-off-by: Alexander Kanavin 
  1 file changed, 3 insertions(+)
 
 diff --git a/Makefile.am b/Makefile.am
-index 7041f8e..25966cd 100644
+index e7221bd..9595fd1 100644
 --- a/Makefile.am
 +++ b/Makefile.am
-@@ -594,6 +594,9 @@ endif
+@@ -710,6 +710,9 @@ endif
  TESTS = $(unit_tests)
  AM_TESTS_ENVIRONMENT = MALLOC_CHECK_=3 MALLOC_PERTURB_=69
  
diff --git 
a/meta/recipes-connectivity/bluez5/bluez5/0002-input-Fix-.device_probe-failing-if-SDP-record-is-not.patch
 
b/meta/recipes-connectivity/bluez5/bluez5/0002-input-Fix-.device_probe-failing-if-SDP-record-is-not.patch
deleted file mode 100644
index d0884338db..00
--- 
a/meta/recipes-connectivity/bluez5/bluez5/0002-input-Fix-.device_probe-failing-if-SDP-record-is-not.patch
+++ /dev/null
@@ -1,313 +0,0 @@
-From 3a9c637010f8dc1ba3e8382abe01065761d4f5bb Mon Sep 17 00:00:00 2001
-From: Luiz Augusto von Dentz 
-Date: Tue, 10 Oct 2023 12:38:29 -0700
-Subject: [PATCH 02/40] 

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

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe systemd failed.
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-63d160d3d0ef4c8e0f59a7b0265d2c77a4a022df"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:63d160d3d0ef4c8e0f59a7b0265d2c77a4a022df"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 
100% complete)
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: 3 seconds
INFO: Extracting current version source...
INFO: SRC_URI contains some conditional appends/prepends - will create branches 
to represent these
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto db11bab38ccf1ed257f310d29070843d4c58ea01
WARNING: Command 'git rebase db11bab38ccf1ed257f310d29070843d4c58ea01' failed:
Auto-merging src/hibernate-resume/hibernate-resume-generator.c
CONFLICT (content): Merge conflict in 
src/hibernate-resume/hibernate-resume-generator.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Rebasing devtool-override-libc-musl onto 
db11bab38ccf1ed257f310d29070843d4c58ea01
WARNING: Command 'git rebase db11bab38ccf1ed257f310d29070843d4c58ea01' failed:
Auto-merging src/hibernate-resume/hibernate-resume-generator.c
CONFLICT (content): Merge conflict in 
src/hibernate-resume/hibernate-resume-generator.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/systemd
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/systemd/systemd_255.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 (#192443): 
https://lists.openembedded.org/g/openembedded-core/message/192443
Mute This Topic: https://lists.openembedded.org/mt/103190856/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] dbus-wait: upgrading to 64bc7c8fae61ded0c4e555aa775911f84c56e438 SUCCEEDED

2023-12-15 Thread Auto Upgrade Helper
Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dbus-wait* to 
*64bc7c8fae61ded0c4e555aa775911f84c56e438* has Succeeded.

Next steps:
- apply the patch: git am 0001-dbus-wait-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 1ef5eaf1f952743257513154521d41fa4d4647c5 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 05:40:27 +
Subject: [PATCH] dbus-wait: upgrade to latest revision

---
 meta/recipes-core/dbus-wait/dbus-wait_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/dbus-wait/dbus-wait_git.bb 
b/meta/recipes-core/dbus-wait/dbus-wait_git.bb
index 1cdf07d03d..39363b9b3a 100644
--- a/meta/recipes-core/dbus-wait/dbus-wait_git.bb
+++ b/meta/recipes-core/dbus-wait/dbus-wait_git.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 DEPENDS = "dbus"
 
-SRCREV = "6cc6077a36fe2648a5f993fe7c16c9632f946517"
+SRCREV = "64bc7c8fae61ded0c4e555aa775911f84c56e438"
 PV = "0.1+git"
 
 SRC_URI = "git://git.yoctoproject.org/${BPN};branch=master;protocol=https"
-- 
2.42.0

NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (0 cached, 911 parsed). 1843 targets, 49 
skipped, 0 masked, 0 errors.
Removing 56 recipes from the core2-64 sysroot...done.
Removing 55 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux-musl"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-0d1c873513181e300b2111a896cd3f00a5bfee3b"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:0d1c873513181e300b2111a896cd3f00a5bfee3b"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 398 Local 385 Mirrors 0 Missed 13 Current 183 (96% 
match, 97% complete)
Removing 5 stale sstate objects for arch x86_64...done.
Removing 1 stale sstate objects for arch qemux86_64...done.
NOTE: Executing Tasks
NOTE: Running setscene task 192 of 581 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/dbus-wait/dbus-wait_git.bb:do_populate_lic_setscene)
NOTE: Running setscene task 194 of 581 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/dbus-wait/dbus-wait_git.bb:do_deploy_source_date_epoch_setscene)
NOTE: Running setscene task 195 of 581 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/dbus/dbus_1.14.10.bb:do_create_spdx_setscene)
NOTE: Running setscene task 196 of 581 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/base-passwd/base-passwd_3.6.2.bb:do_populate_sysroot_setscene)
NOTE: Running setscene task 204 of 581 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-extended/shadow/shadow-sysroot_4.6.bb:do_populate_sysroot_setscene)
NOTE: recipe shadow-sysroot-4.6-r0: task do_populate_sysroot_setscene: Started
NOTE: recipe dbus-wait-0.1+git-r0: task do_deploy_source_date_epoch_setscene: 
Started
NOTE: recipe dbus-wait-0.1+git-r0: task do_populate_lic_setscene: Started
NOTE: recipe base-passwd-3.6.2-r0: task do_populate_sysroot_setscene: Started
NOTE: recipe dbus-1.14.10-r0: task do_create_spdx_setscene: Started
NOTE: recipe dbus-wait-0.1+git-r0: task do_deploy_source_date_epoch_setscene: 
Succeeded
NOTE: recipe dbus-wait-0.1+git-r0: task do_populate_lic_setscene: Succeeded
NOTE: Running setscene task 310 of 581 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/dbus-wait/dbus-wait_git.bb:do_recipe_qa_setscene)
NOTE: recipe dbus-1.14.10-r0: task do_create_spdx_setscene: Succeeded
NOTE: Running setscene task 312 of 581 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-core/dbus/dbus_1.14.10.bb:do_packagedata_setscene)
NOTE: recipe shadow-sysroot-4.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: Running setscene task 326 of 581 

[OE-core] [AUH] usbutils: upgrading to 017 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-usbutils-upgrade-015-017.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 c7692089b6ddea808f23254b13eed788c2630f06 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Fri, 15 Dec 2023 05:03:36 +
Subject: [PATCH] usbutils: upgrade 015 -> 017

---
 meta/recipes-bsp/usbutils/{usbutils_015.bb => usbutils_017.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-bsp/usbutils/{usbutils_015.bb => usbutils_017.bb} (92%)

diff --git a/meta/recipes-bsp/usbutils/usbutils_015.bb 
b/meta/recipes-bsp/usbutils/usbutils_017.bb
similarity index 92%
rename from meta/recipes-bsp/usbutils/usbutils_015.bb
rename to meta/recipes-bsp/usbutils/usbutils_017.bb
index a30037b693..1a3ea8013c 100644
--- a/meta/recipes-bsp/usbutils/usbutils_015.bb
+++ b/meta/recipes-bsp/usbutils/usbutils_017.bb
@@ -13,7 +13,7 @@ DEPENDS = "libusb1 virtual/libiconv udev"
 
 SRC_URI = "${KERNELORG_MIRROR}/linux/utils/usb/usbutils/usbutils-${PV}.tar.gz \
   "
-SRC_URI[sha256sum] = 
"2b8140664578f39c3f6f0166a1b950f8655304e63e3d7f89899acb99bc5cb8e7"
+SRC_URI[sha256sum] = 
"f704c4cb78a060db88b43aac6ebfd3d93c2c5cf1d6dd0e42936faaf00814ab00"
 
 inherit autotools pkgconfig update-alternatives
 
-- 
2.42.0



0001-usbutils-upgrade-015-017.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1843 entries from dependency cache.
Parsing recipes...done.
Parsing of 911 .bb files complete (910 cached, 1 parsed). 1842 targets, 38 
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.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-524255ad266c88785cad2f410b3fd6b74aa24071"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:524255ad266c88785cad2f410b3fd6b74aa24071"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 462 Local 452 Mirrors 0 Missed 10 Current 433 (97% 
match, 98% complete)
NOTE: Executing Tasks
NOTE: Running setscene task 442 of 895 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-bsp/usbutils/usbutils_017.bb:do_populate_lic_setscene)
NOTE: Running setscene task 444 of 895 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-bsp/usbutils/usbutils_017.bb:do_deploy_source_date_epoch_setscene)
NOTE: recipe usbutils-017-r0: task do_populate_lic_setscene: Started
NOTE: recipe usbutils-017-r0: task do_deploy_source_date_epoch_setscene: Started
NOTE: recipe usbutils-017-r0: task do_deploy_source_date_epoch_setscene: 
Succeeded
NOTE: recipe usbutils-017-r0: task do_populate_lic_setscene: Succeeded
NOTE: Running setscene task 895 of 895 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-bsp/usbutils/usbutils_017.bb:do_recipe_qa_setscene)
NOTE: recipe usbutils-017-r0: task do_recipe_qa_setscene: Started
NOTE: recipe usbutils-017-r0: task do_recipe_qa_setscene: Succeeded
NOTE: Setscene tasks completed
NOTE: Running task 1978 of 2499 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-bsp/usbutils/usbutils_017.bb:do_fetch)
NOTE: recipe usbutils-017-r0: task do_fetch: Started
NOTE: recipe usbutils-017-r0: task do_fetch: Succeeded
NOTE: Running task 2320 of 2499 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-bsp/usbutils/usbutils_017.bb:do_unpack)
NOTE: Running task 2321 of 2499 
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-bsp/usbutils/usbutils_017.bb:do_prepare_recipe_sysroot)
NOTE: recipe usbutils-017-r0: task do_unpack: Started
NOTE: recipe usbutils-017-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe usbutils-017-r0: task do_unpack: Succeeded
NOTE: 

[OE-core] [AUH] kbd: upgrading to 2.6.4 FAILED

2023-12-15 Thread Auto Upgrade Helper
Hello,

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

Detailed error information:

The following devtool command failed:  upgrade kbd -V 2.6.4
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1842 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cbfb9e4e03ade792ac93f5bd7e6a03f6a062f8db"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cbfb9e4e03ade792ac93f5bd7e6a03f6a062f8db"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 
100% complete)
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 1842 entries from dependency cache.
Parsing recipes...done.
Parsing of 912 .bb files complete (910 cached, 2 parsed). 1843 targets, 38 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3+snapshot-cbfb9e4e03ade792ac93f5bd7e6a03f6a062f8db"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   
workspace= 
"tmp-auh-upgrades:cbfb9e4e03ade792ac93f5bd7e6a03f6a062f8db"

Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing 
build without monitoring pressure
done.
Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% 
complete)
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://cdn.kernel.org/pub/linux/utils/kbd/kbd-2.6.4.tar.xz, attempting MIRRORS 
if available
NOTE: Tasks Summary: Attempted 92 tasks of which 90 didn't need to be rerun and 
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
NOTE: The errors for this build are stored in 
/home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20231215055446.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_20231215055446.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://cdn.kernel.org/pub/linux/utils/kbd/kbd-2.6.4.tar.xz...
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-i4qqcon3/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-i4qqcon3/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-i4qqcon3/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipe
 
tool-i4qqcon3/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-i4qqcon3/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-i4qqcon3/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 -O 
/srv/autobuilder/autobuilder.yocto.io/current_sources/kbd-2.6.4.tar.xz.tmp -P 
/srv/autobuilder/autobuilder.yocto.io/current_sources 
'https://cdn.kernel.org/pub/linux/utils/kbd/kbd-2.6.4.tar.xz' 

[OE-core] [PATCH 0/1] nfs-utils: Update Upstream-Status

2023-12-15 Thread Robert Yang via lists.openembedded.org
From: Robert Yang 

The following changes since commit ae642a4b038c6946e6c8aa9778bf09099d938a31:

  sstate: Fix dir ownership issues in SSTATE_DIR (2023-12-15 11:14:29 +)

are available in the Git repository at:

  https://github.com/robertlinux/yocto rbt/nfs-utils
  https://github.com/robertlinux/yocto/tree/rbt/nfs-utils

Robert Yang (1):
  nfs-utils: Update Upstream-Status

 .../0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192432): 
https://lists.openembedded.org/g/openembedded-core/message/192432
Mute This Topic: https://lists.openembedded.org/mt/103190381/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/1] nfs-utils: Update Upstream-Status

2023-12-15 Thread Robert Yang via lists.openembedded.org
From: Robert Yang 

Update Upstream-Status for 
0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch.

Signed-off-by: Robert Yang 
---
 .../0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-connectivity/nfs-utils/nfs-utils/0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch
 
b/meta/recipes-connectivity/nfs-utils/nfs-utils/0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch
index 8607b64cb1f..57d4660571f 100644
--- 
a/meta/recipes-connectivity/nfs-utils/nfs-utils/0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch
+++ 
b/meta/recipes-connectivity/nfs-utils/nfs-utils/0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch
@@ -9,7 +9,7 @@ reexport.c:62:17: error: implicit declaration of function 
'sleep' [-Werror=impli
62 | sleep(1);
 
 
-Upstream-Status: Pending
+Upstream-Status: Submitted 
[https://marc.info/?l=linux-nfs=170254661824522=2]
 
 Signed-off-by: Robert Yang 
 ---
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192433): 
https://lists.openembedded.org/g/openembedded-core/message/192433
Mute This Topic: https://lists.openembedded.org/mt/103190382/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] mesa: upgrade 23.2.1 -> 23.3.1

2023-12-15 Thread Lucas Stach
- build amd vulkan driver for x86 platforms
- drop included patch
[https://gitlab.freedesktop.org/mesa/mesa/-/blob/1fbdd37d4c1133ced5eb9812daa1fff04cbf5daa/meson.build#L1711]

Signed-off-by: Lucas Stach 
---
Based on the 23.3.0 update patch [1] from Markus Volk, but bumped to 23.3.1
and fixed sstate mismatches between 32bit and 64bit.

[1] https://lore.kernel.org/openembedded-core/poqf5s.m9f40qh9iv...@t-online.de/
---
 ...e-cmake-dependency-detector-for-llvm.patch | 42 ---
 .../{mesa-gl_23.2.1.bb => mesa-gl_23.3.1.bb}  |  0
 meta/recipes-graphics/mesa/mesa.inc   |  9 ++--
 .../mesa/{mesa_23.2.1.bb => mesa_23.3.1.bb}   |  0
 4 files changed, 4 insertions(+), 47 deletions(-)
 delete mode 100644 
meta/recipes-graphics/mesa/files/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
 rename meta/recipes-graphics/mesa/{mesa-gl_23.2.1.bb => mesa-gl_23.3.1.bb} 
(100%)
 rename meta/recipes-graphics/mesa/{mesa_23.2.1.bb => mesa_23.3.1.bb} (100%)

diff --git 
a/meta/recipes-graphics/mesa/files/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
 
b/meta/recipes-graphics/mesa/files/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
deleted file mode 100644
index 4cded0546dc4..
--- 
a/meta/recipes-graphics/mesa/files/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From 00d41cd5aa3f4b494dc276c9b4ccdc096310c91f Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Thu, 28 Sep 2023 15:34:22 -0700
-Subject: [PATCH] meson: use llvm-config instead of cmake to fix linking errors 
with meson 1.2.1
-
-meson dependency auto dependency detection uses cmake and then
-config-tool to process dependencies, in mesa the logic to detect llvm is
-using auto detection which means if it finds cmake then it will try to
-use cmake method. Cmake method works ok except a case when llvm-dev
-package is installed on the build host then it generates its own
-native.meson file and ignores OE supplied meson.native file which has
-correct llvm-config tool specified which is pointing to llvm-config from
-native sysroot. The generated meson.native file points to one found in
-/usr/bin and there onwards detector finds native install of llvm and
-configures that into building native mesa package.
-
-Since cmake detector does not always work, disable it by default and use
-config-tool which works in all cases. This is suggested in below issues
-too
-
-A similar issue is open in meson upstream [1] and mesa [2]
-
-[1] https://github.com/mesonbuild/meson/issues/10483
-[2] https://gitlab.freedesktop.org/mesa/mesa/-/issues/6738
-
-Upstream-Status: Submitted 
[https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25438]
-
-Signed-off-by: Khem Raj 

- meson.build | 1 +
- 1 file changed, 1 insertion(+)
-
 a/meson.build
-+++ b/meson.build
-@@ -1659,6 +1659,7 @@ with_llvm = false
- if _llvm.allowed()
-   dep_llvm = dependency(
- 'llvm',
-+method : host_machine.system() == 'windows' ? 'auto' : 'config-tool',
- version : _llvm_version,
- modules : llvm_modules,
- optional_modules : llvm_optional_modules,
diff --git a/meta/recipes-graphics/mesa/mesa-gl_23.2.1.bb 
b/meta/recipes-graphics/mesa/mesa-gl_23.3.1.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_23.2.1.bb
rename to meta/recipes-graphics/mesa/mesa-gl_23.3.1.bb
diff --git a/meta/recipes-graphics/mesa/mesa.inc 
b/meta/recipes-graphics/mesa/mesa.inc
index e5c405a9728c..5f5c8ceb4c84 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -18,10 +18,9 @@ SRC_URI = 
"https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \

file://0001-meson.build-check-for-all-linux-host_os-combinations.patch \
file://0001-meson-misdetects-64bit-atomics-on-mips-clang.patch \
file://0001-gallium-Fix-build-with-llvm-17.patch \
-   file://0001-meson-Disable-cmake-dependency-detector-for-llvm.patch \
 "
 
-SRC_URI[sha256sum] = 
"64de0616fc2d801f929ab1ac2a4f16b3e2783c4309a724c8a259b20df8bbc1cc"
+SRC_URI[sha256sum] = 
"6e48126d70fdb3f20ffeb246ca0c2e41ffdc835f0663a03d4526b8bf5db41de6"
 
 UPSTREAM_CHECK_GITTAGREGEX = "mesa-(?P\d+(\.\d+)+)"
 
@@ -105,10 +104,10 @@ PACKAGECONFIG[dri3] = "-Ddri3=enabled, -Ddri3=disabled, 
xorgproto libxshmfence"
 # Vulkan drivers need dri3 enabled
 # amd could be enabled as well but requires gallium-llvm with llvm >= 3.9
 VULKAN_DRIVERS = ""
-VULKAN_DRIVERS:append:x86 = ",intel"
-VULKAN_DRIVERS:append:x86-64 = ",intel"
+VULKAN_DRIVERS:append:x86 = ",intel,amd"
+VULKAN_DRIVERS:append:x86-64 = ",intel,amd"
 # i686 is a 32 bit override for mesa-native
-VULKAN_DRIVERS:append:i686 = ",intel"
+VULKAN_DRIVERS:append:i686 = ",intel,amd"
 VULKAN_DRIVERS:append ="${@bb.utils.contains('PACKAGECONFIG', 'freedreno', 
',freedreno', '', d)}"
 VULKAN_DRIVERS:append ="${@bb.utils.contains('PACKAGECONFIG', 'broadcom', 
',broadcom', '', d)}"
 VULKAN_DRIVERS:append 

Re: [OE-Core][PATCH] rust: Upgrade 1.71.1 -> 1.74.1

2023-12-15 Thread Alex Kiernan
On Thu, Dec 14, 2023 at 10:28 AM Ross Burton  wrote:
>
> On 13 Dec 2023, at 14:06, Richard Purdie via lists.openembedded.org 
>  wrote:
> > I've run this with this patch included:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4082
>
> Same failure:
>
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20231213-s13b67oz/packages/diff-html/
>
> Ross

Thanks both.

It does look like its just filename churn, but I cannot find where
those names actually get generated :| Suspect this will be a report
upstream and hope someone helps.

-- 
Alex Kiernan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192430): 
https://lists.openembedded.org/g/openembedded-core/message/192430
Mute This Topic: https://lists.openembedded.org/mt/103146651/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] ldconfig-native: Add usrmerge support

2023-12-15 Thread Johannes Pointner
On Wed, Dec 13, 2023 at 12:01 PM Ross Burton  wrote:
>
> On 6 Dec 2023, at 07:40, Johannes Pointner via lists.openembedded.org 
>  wrote:
> >
> > From: Johannes Pointner 
> >
> > If DISTRO_FEATURE usrmerge is enabled, SLIBDIR is just a symlink to LIBDIR.
> > ldconfig-native uses hardcoded paths for SLIBDIR and LIBDIR that are fine 
> > for
> > the not usrmerge case. But if usrmerge is enabled ldconfig-native generates 
> > a
> > ld.so.cache, which is done in rootfs.py, that looks like this:
> > 236 libs found in cache `/etc/ld.so.cache'
> >   libzstd.so.1 (libc6) => /lib/libzstd.so.1
> >   libz.so.1 (libc6) => /lib/libz.so.1
> >   libxtables.so.12 (libc6) => /lib/libxtables.so.12
> >   libxslt.so.1 (libc6) => /lib/libxslt.so.1
> >   libxml2.so.2 (libc6) => /lib/libxml2.so.2
> >
> > This breaks for example the Qt QLibraryInfo paths if Qt is configured
> > 'relocatable' and leads to the issue that the QtWebEngine can find the
> > QtWebEngineProcess, Qt WebEngine resources,...
> >
> > Therefore don't let ldconfig-native parse SLIBDIR if it is a symlink.
>
> This still doesn’t explain *why* ldconfig is broken, why the workaround is a 
> yocto-specific fix in ldconfig and not a general fix that other distros have, 
> and why this isn’t a problem with Qt.
As I wrote above ldconfig-native is broken for the usrmerge case
because it uses hardcoded paths which are correct for the "not
usrmerge case" but not for the "usrmerge case".
Other distros as also the yocto ldconfig for the target system is
configured at build time with the correct paths and works fine.
This is an issue for Qt because it tries to determine the library
locations using dladdr and this leads to incorrect paths that in my
case broke QtWebEngine.
>
> Ross
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192429): 
https://lists.openembedded.org/g/openembedded-core/message/192429
Mute This Topic: https://lists.openembedded.org/mt/103009101/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] strace: Disable bluetooth support by default

2023-12-15 Thread Richard Purdie
On Fri, 2023-12-15 at 11:59 +, Ross Burton wrote:
> On 15 Dec 2023, at 10:49, Yoann Congal  wrote:
> > FYI, since Khem's patch ([OE-core] [PATCH] util-linux: Delete md-
> > raid tests) also prevent bluez to be built in a default core-image-
> > minimal build, we can skip this one (strace: Disable bluetooth
> > support by default) and still fix [YOCTO #15323].
> 
> I’m a fan of both.  Bluetooth support in strace is a niche usecase and easily 
> enabled.

I have a half drafted email saying I was thinking of both too! (I then
got distracted).

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192428): 
https://lists.openembedded.org/g/openembedded-core/message/192428
Mute This Topic: https://lists.openembedded.org/mt/103146402/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: Handle recipes with a menuconfig task correctly

2023-12-15 Thread Peter Kjellerstedt
This avoids the following error when running `devtool modify` on a
recipe that has a menuconfig task, but does not have
KCONFIG_CONFIG_ENABLE_MENUCONFIG set.

  .../temp/run.do_configure.4163366: line 152:
  ${@ oe.types.boolean('${KCONFIG_CONFIG_ENABLE_MENUCONFIG}') }: bad 
substitution
  WARNING: .../temp/run.do_configure.4163366:152 exit 1 from
  '[ ${@ oe.types.boolean('${KCONFIG_CONFIG_ENABLE_MENUCONFIG}') } = True ]'

Signed-off-by: Peter Kjellerstedt 
---
 scripts/lib/devtool/standard.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index c5b6458d06..559fd45676 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -986,7 +986,7 @@ def modify(args, config, basepath, workspace):
 '}\n')
 if rd.getVarFlag('do_menuconfig','task'):
 f.write('\ndo_configure:append() {\n'
-'if [ ${@ 
oe.types.boolean(\'${KCONFIG_CONFIG_ENABLE_MENUCONFIG}\') } = True ]; then\n'
+'if [ 
${@oe.types.boolean(d.getVar("KCONFIG_CONFIG_ENABLE_MENUCONFIG"))} = True ]; 
then\n'
 'cp ${KCONFIG_CONFIG_ROOTDIR}/.config 
${S}/.config.baseline\n'
 'ln -sfT ${KCONFIG_CONFIG_ROOTDIR}/.config 
${S}/.config.new\n'
 'fi\n'

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192427): 
https://lists.openembedded.org/g/openembedded-core/message/192427
Mute This Topic: https://lists.openembedded.org/mt/103189021/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] strace: Disable bluetooth support by default

2023-12-15 Thread Ross Burton
On 15 Dec 2023, at 10:49, Yoann Congal  wrote:
> FYI, since Khem's patch ([OE-core] [PATCH] util-linux: Delete md-raid tests) 
> also prevent bluez to be built in a default core-image-minimal build, we can 
> skip this one (strace: Disable bluetooth support by default) and still fix 
> [YOCTO #15323].

I’m a fan of both.  Bluetooth support in strace is a niche usecase and easily 
enabled.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192426): 
https://lists.openembedded.org/g/openembedded-core/message/192426
Mute This Topic: https://lists.openembedded.org/mt/103146402/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] strace: Disable bluetooth support by default

2023-12-15 Thread Yoann Congal


Le 14/12/2023 à 20:36, Khem Raj a écrit :
> On Thu, Dec 14, 2023 at 11:33 AM Alexandre Belloni
>  wrote:
>>
>> On 14/12/2023 10:53:05-0800, Khem Raj wrote:
>>> On Thu, Dec 14, 2023 at 1:10 AM Alexander Kanavin
>>>  wrote:

 On Wed, 13 Dec 2023 at 09:57, Yoann Congal  wrote:
>
> The bluetooth support adds a bluez5 dependency (and,recursively, a lot
> of other stuff). Disable it by default to avoid having to build all of
> this when it is not needed.
>
> This decrease the number of tasks run for a core-image-minimal build by
> ~1000 (-21%).
>
> To re-enable bluetooth support in strace, add "bluez" to strace
> PACKAGECONFIG. For example, in local.conf:
>   PACKAGECONFIG:append:pn-strace = " bluez"
>
> Fixes [YOCTO #15323]

 I'm afraid I have to raise objections.

 First, this needs an explanation: what functionality in strace does
 this disable? Is that functionality important from the point of having
 bluetooth in DISTRO_FEATURES? Not respecting DISTRO_FEATURES sets a
 bad precedent, and should be more carefully justified and treated as
 an exception.

 Second, why is strace even needed in the context of
 core-image-minimal? It's not installed into the image, so I went and
 checked:
 util-linux-ptest needs mdadm
 mdadm-ptest needs strace.
>>>
>>> I looked briefly into util-linux pertaining to mdadm needs in tests, there
>>> are 4 tests needing it.
>>> md-raid0-whole, md-raid1-part, md-raid1-whole, align-512-4K-md
>>>
>>> and all of them are marked as
>>> TS_KNOWN_FAIL="yes"
>>>
>>> See 
>>> https://github.com/util-linux/util-linux/commit/7519c3edab120b14623931d5ddb16fdc6e7cad5d
>>>
>>> I think we can skip running these tests as well and safely avoid
>>> depending upon mdadm for util-linux ptests which can break the depchain as 
>>> well.
>>>
>>
>> I think dropping the mdam ptests was the plan seeing the amount of
>> breakage this does on the AB.
> 
> Good deal, I also see them happening on musl so I went ahead and cooked a 
> patch
> and posted it on ml. Musl util-linux ptests have 4 less fails now.

FYI, since Khem's patch ([OE-core] [PATCH] util-linux: Delete md-raid tests) 
also prevent bluez to be built in a default core-image-minimal build, we can 
skip this one (strace: Disable bluetooth support by default) and still fix 
[YOCTO #15323].

>>

 Which begs the question. Should we continue to enable ptest by default
 in poky? Should we create and use a ptest-less distro configuration?
 It does pull in a ton of extra stuff all over the place which
 lengthens the builds a lot. And the resulting ptest packages aren't
 even used until one explicitly requests one of the ptest images.

 As an example, I saw an oe-selftest-armhost yesterday, which ran
 nearly 17 hours:
 https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/2587

 If you go and look at what tests in it took the longest time, you see:
 2023-12-13 15:45:22,812 - oe-selftest - INFO - RESULTS -
 runtime_test.Postinst.test_postinst_rootfs_and_boot_systemd: PASSED
 (32620.46s)
 2023-12-13 15:45:22,794 - oe-selftest - INFO - RESULTS -
 prservice.BitbakePrTests.test_import_export_override_db: PASSED
 (12789.45s)
 2023-12-13 15:45:22,789 - oe-selftest - INFO - RESULTS -
 overlayfs.OverlayFSEtcRunTimeTests.test_all_required_variables_set:
 PASSED (35205.79s)
 2023-12-13 15:45:22,781 - oe-selftest - INFO - RESULTS -
 minidebuginfo.Minidebuginfo.test_minidebuginfo: PASSED (15395.76s)
 2023-12-13 15:45:22,782 - oe-selftest - INFO - RESULTS -
 multiconfig.MultiConfig.test_multiconfig: PASSED (11098.06s)
 2023-12-13 15:45:22,776 - oe-selftest - INFO - RESULTS -
 incompatible_lic.IncompatibleLicensePerImageTests.test_bash_and_license:
 PASSED (24012.67s)
 2023-12-13 15:45:22,775 - oe-selftest - INFO - RESULTS -
 imagefeatures.ImageFeatures.test_mandb: PASSED (19394.74s)
 2023-12-13 15:45:22,762 - oe-selftest - INFO - RESULTS -
 devtool.DevtoolExtractTests.test_devtool_build_image: PASSED
 (27341.75s)
 2023-12-13 15:45:22,760 - oe-selftest - INFO - RESULTS -
 debuginfod.Debuginfod.test_debuginfod_qemu: PASSED (25784.11s)
 2023-12-13 15:45:22,759 - oe-selftest - INFO - RESULTS -
 containerimage.ContainerImageTests.test_expected_files: PASSED
 (19453.84s)
 2023-12-13 15:45:22,758 - oe-selftest - INFO - RESULTS -
 buildoptions.SanityOptionsTest.test_options_warnqa_errorqa_switch:
 PASSED (10492.68s)
 2023-12-13 15:45:22,758 - oe-selftest - INFO - RESULTS -
 buildoptions.ToolchainOptions.test_toolchain_fortran: PASSED
 (11367.46s)
 2023-12-13 15:45:22,743 - oe-selftest - INFO - RESULTS -
 baremetal.BaremetalTest.test_baremetal: PASSED (24196.04s)

 The same a-full selftest, but on a x86 host has these times, quicker
 than arm but still measured 

Re: [OE-core] [PATCH] util-linux: Delete md-raid tests

2023-12-15 Thread Yoann Congal
Hi,

Le 14/12/2023 à 20:34, Khem Raj a écrit :
> These tests are marked as known failures upstream as well [1]
> if we delete them then we can drop dependency on mdadm for ptests which
> can further reduce the dependency chain for ptest enabled minimal images
> 
> [1] 
> https://github.com/util-linux/util-linux/commit/7519c3edab120b14623931d5ddb16fdc6e7cad5d
> 
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-core/util-linux/util-linux_2.39.2.bb | 8 +++-
>  1 file changed, 7 insertions(+), 1 deletion(-)

Just tested it: this patch also work to remove bluez from the dependency chain 
of a default core-image-minimal build 
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=15323)

Regards,
-- 
Yoann Congal
Smile ECS - Tech Expert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192424): 
https://lists.openembedded.org/g/openembedded-core/message/192424
Mute This Topic: https://lists.openembedded.org/mt/103177008/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] curl: update to 8.5.0

2023-12-15 Thread Lee Chee Yang
From: Lee Chee Yang 

update include fix for CVE-2023-46218.

skip test 1477 which check that libcurl-errors.3 and the public
header files have the same set of error codes.
Notes: This test is not included in the source tarball.
https://github.com/curl/curl/issues/12462

Release Notes:
curl and libcurl 8.5.0

 Public curl releases: 253
 Command line options: 258
 curl_easy_setopt() options:   303
 Public functions in libcurl:  93
 Contributors: 3039

This release includes the following changes:

 o gnutls: support CURLSSLOPT_NATIVE_CA [31]
 o HTTP3: ngtcp2 builds are no longer experimental [77]

This release includes the following bugfixes:

 o appveyor: make VS2008-built curl tool runnable [93]
 o asyn-thread: use pipe instead of socketpair for IPC when available [4]
 o autotools: accept linker flags via `CURL_LDFLAGS_{LIB,BIN}` [128]
 o autotools: avoid passing `LDFLAGS` twice to libcurl [127]
 o autotools: delete LCC compiler support bits [137]
 o autotools: fix/improve gcc and Apple clang version detection [136]
 o autotools: stop setting `-std=gnu89` with `--enable-warnings` [135]
 o autotools: update references to deleted `crypt-auth` option [46]
 o BINDINGS: add V binding [54]
 o build: add `src/.checksrc` to source tarball [1]
 o build: add more picky warnings and fix them [172]
 o build: always revert `#pragma GCC diagnostic` after use [143]
 o build: delete `HAVE_STDINT_H` and `HAVE_INTTYPES_H` [107]
 o build: delete support bits for obsolete Windows compilers [106]
 o build: fix 'threadsafe' feature detection for older gcc [19]
 o build: fix builds that disable protocols but not digest auth [174]
 o build: fix compiler warning with auths disabled [85]
 o build: fix libssh2 + `CURL_DISABLE_DIGEST_AUTH` + `CURL_DISABLE_AWS` [120]
 o build: picky warning updates [125]
 o build: require Windows XP or newer [86]
 o cfilter: provide call to tell connection to forget a socket [65]
 o checksrc.pl: support #line instructions
 o CI: add autotools, out-of-tree, debug build to distro check job [14]
 o CI: ignore test 286 on Appveyor gcc 9 build [6]
 o cmake: add `CURL_DISABLE_BINDLOCAL` option [146]
 o cmake: add test for `DISABLE` options, add `CURL_DISABLE_HEADERS_API` [138]
 o cmake: dedupe Windows system libs [114]
 o cmake: fix `HAVE_H_ERRNO_ASSIGNABLE` detection [2]
 o cmake: fix CURL_DISABLE_GETOPTIONS [12]
 o cmake: fix multiple include of CURL package [96]
 o cmake: fix OpenSSL quic detection in quiche builds [56]
 o cmake: option to disable install & drop `curlu` target when unused [72]
 o cmake: pre-fill rest of detection values for Windows [50]
 o cmake: replace `check_library_exists_concat()` [23]
 o cmake: speed up threads setup for Windows [68]
 o cmake: speed up zstd detection [69]
 o config-win32: set `HAVE_SNPRINTF` for mingw-w64 [123]
 o configure: better --disable-http [80]
 o configure: check for the fseeko declaration too [55]
 o conncache: use the closure handle when disconnecting surplus connections 
[173]
 o content_encoding: make Curl_all_content_encodings allocless [101]
 o cookie: lowercase the domain names before PSL checks [160]
 o curl.h: delete Symbian OS references [162]
 o curl.h: on FreeBSD include sys/param.h instead of osreldate.h [21]
 o curl.rc: switch out the copyright symbol for plain ASCII [167]
 o curl: improved IPFS and IPNS URL support [87]
 o curl_easy_duphandle.3: clarify how HSTS and alt-svc are duped [99]
 o Curl_http_body: cleanup properly when Curl_getformdata errors [152]
 o curl_setup: disallow Windows IPv6 builds missing getaddrinfo [57]
 o curl_sspi: support more revocation error names in error messages [95]
 o CURLINFO_PRETRANSFER_TIME_T.3: fix time explanation [181]
 o CURLMOPT_MAX_CONCURRENT_STREAMS: make sure the set value is within range 
[165]
 o CURLOPT_CAINFO_BLOB.3: explain what CURL_BLOB_COPY does [113]
 o CURLOPT_WRITEFUNCTION.3: clarify libcurl returns for CURL_WRITEFUNC_ERROR 
[45]
 o CURPOST_POSTFIELDS.3: add CURLOPT_COPYPOSTFIELDS in SEE ALSO
 o docs/example/keepalive.c: show TCP keep-alive options [73]
 o docs/example/localport.c: show off CURLOPT_LOCALPORT [83]
 o docs/examples/interface.c: show CURLOPT_INTERFACE use [84]
 o docs/libcurl: fix three minor man page format mistakes [26]
 o docs/libcurl: SYNSOPSIS cleanup [150]
 o docs: add supported version for the json write-out [92]
 o docs: clarify that curl passes on input unfiltered [47]
 o docs: fix function typo in curl_easy_option_next.3 [36]
 o docs: KNOWN_BUGS cleanup
 o docs: make all examples in all libcurl man pages compile [175]
 o docs: preserve the modification date when copying the prebuilt man page [89]
 o docs: remove bold from some man page SYNOPSIS sections [90]
 o docs: use SOURCE_DATE_EPOCH for generated manpages [16]
 o doh: provide better return code for responses w/o addresses [133]
 o doh: use PIPEWAIT when HTTP/2 is attempted [63]
 o duphandle: also free 'outcurl->cookies' in error path [122]
 o duphandle: make dupset() not