From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <f_l_k@t-online.de>, <openembedded-core@lists.openembedded.org>
Subject: Re: [oe-core][PATCH 1/3] gtk4: upgrade 4.22.5 -> 4.24.0
Date: Wed, 16 Sep 2026 13:43:25 +0200 [thread overview]
Message-ID: <DLGPQ1X40IXU.3E13NLLX5ZW3M@bootlin.com> (raw)
In-Reply-To: <20260916055325.3396270-1-f_l_k@t-online.de>
Hi,
On Wed Sep 16, 2026 at 7:53 AM CEST, Markus Volk via lists.openembedded.org wrote:
> Needs glib-2.0 >= 2.89.3, which the 2.90.0 upgrade provides.
>
> AI-Generated: Uses Claude Code (Claude Opus 5)
> Signed-off-by: Markus Volk <f_l_k@t-online.de>
> ---
> meta/recipes-gnome/gtk+/{gtk4_4.22.5.bb => gtk4_4.24.0.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-gnome/gtk+/{gtk4_4.22.5.bb => gtk4_4.24.0.bb} (97%)
>
> diff --git a/meta/recipes-gnome/gtk+/gtk4_4.22.5.bb b/meta/recipes-gnome/gtk+/gtk4_4.24.0.bb
> similarity index 97%
> rename from meta/recipes-gnome/gtk+/gtk4_4.22.5.bb
> rename to meta/recipes-gnome/gtk+/gtk4_4.24.0.bb
> index 5d7385d29a..8a350d44f2 100644
> --- a/meta/recipes-gnome/gtk+/gtk4_4.22.5.bb
> +++ b/meta/recipes-gnome/gtk+/gtk4_4.24.0.bb
> @@ -33,7 +33,7 @@ LIC_FILES_CHKSUM = " \
> file://tests/testgtk.c;endline=25;md5=49d06770681b8322466b52ed19d29fb2 \
> "
>
> -SRC_URI[archive.sha256sum] = "7fd725deb2cb3f8dc218ad862c5056ff8548f49d3b0e4081796e444c22d19686"
> +SRC_URI[archive.sha256sum] = "28ba4ac1c04f86eac09b79a163cb163a4c2b54442d9f7eccc04679062a581044"
>
> S = "${UNPACKDIR}/${GNOMEBN}-${PV}"
>
I think your patch triggers the following error:
ERROR: gtk4-4.24.0-r0 do_package_qa: QA Issue: File /usr/src/debug/gtk4/4.24.0/gtk/svg/libgtk_svg.a.p/gtk_svg-unity0.c in package gtk4-src contains reference to TMPDIR [buildpaths]
ERROR: gtk4-4.24.0-r0 do_package_qa: QA Issue: File /usr/src/debug/gtk4/4.24.0/gtk/svg/libgtk_svg.a.p/gtk_svg-unity0.c in package gtk4-src contains a reference to the build host HOME directory. If upstream hardcodes a directory path that matches your home, you can set OEQA_BUILDPATHS_SKIP = "/srv/pokybuild" in the recipe. [buildpaths]
Full log: https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/8949458/raw_inline
Parent build: https://autobuilder.yoctoproject.org/valkyrie/#/builders/10/builds/4634
Not sure we are going to merge this yet after reading the thread, but you might
want to look into it.
Antonin
next prev parent reply other threads:[~2026-09-16 11:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 5:53 [oe-core][PATCH 1/3] gtk4: upgrade 4.22.5 -> 4.24.0 Markus Volk
2026-09-16 5:53 ` [oe-core][PATCH 2/3] libadwaita: upgrade 1.9.3 -> 1.10.0 Markus Volk
2026-09-16 5:53 ` [oe-core][PATCH 3/3] adwaita-icon-theme: upgrade 50.0 -> 51.0 Markus Volk
2026-09-16 8:41 ` Richard Purdie
2026-09-16 9:05 ` Markus Volk
2026-09-16 9:12 ` Ross Burton
2026-09-16 11:43 ` Antonin Godard [this message]
2026-09-16 14:18 ` [oe-core][PATCH 1/3] gtk4: upgrade 4.22.5 -> 4.24.0 Markus Volk
2026-09-18 11:19 ` Ross Burton
2026-09-18 12:18 ` Markus Volk
2026-09-18 16:17 ` Ross Burton
2026-09-21 13:00 ` Ross Burton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DLGPQ1X40IXU.3E13NLLX5ZW3M@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=f_l_k@t-online.de \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox