From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 14/15] vte: upgrade 0.82.2 -> 0.84.0
Date: Fri, 19 Jun 2026 10:32:56 +0200 [thread overview]
Message-ID: <20260619083305.3505156-14-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20260619083305.3505156-1-alex.kanavin@gmail.com>
From: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
...rt-reproducibility-for-debug-sources.patch | 48 -------------------
.../vte/{vte_0.82.2.bb => vte_0.84.0.bb} | 6 ++-
2 files changed, 4 insertions(+), 50 deletions(-)
delete mode 100644 meta/recipes-support/vte/vte/0001-support-reproducibility-for-debug-sources.patch
rename meta/recipes-support/vte/{vte_0.82.2.bb => vte_0.84.0.bb} (90%)
diff --git a/meta/recipes-support/vte/vte/0001-support-reproducibility-for-debug-sources.patch b/meta/recipes-support/vte/vte/0001-support-reproducibility-for-debug-sources.patch
deleted file mode 100644
index 20e8f71c0e..0000000000
--- a/meta/recipes-support/vte/vte/0001-support-reproducibility-for-debug-sources.patch
+++ /dev/null
@@ -1,48 +0,0 @@
-From 0959004adbe46f88d558d2ce61b496c662c196f5 Mon Sep 17 00:00:00 2001
-From: Hongxu Jia <hongxu.jia@windriver.com>
-Date: Mon, 3 Nov 2025 06:13:11 +0000
-Subject: [PATCH] support reproducibility for debug sources
-
-While option --debug-sources is used, the generated source file contains
-build path comments which caused the build is not reproducible [1]
-...subprojects/simdutf/simdutf.h...
- 1 /* auto-generated on 2025-03-17 16:13:41 -0400. Do not edit! */
- 2 /* begin file include/simdutf.h */
- 3 // /build-dir/vte-0.82.1/subprojects/simdutf/include/simdutf.h:1
- 4 #ifndef SIMDUTF_H
-...subprojects/simdutf/simdutf.h...
-
-After apply this commit, use relative path to instead
-...subprojects/simdutf/simdutf.h...
- 1 /* auto-generated on 2025-03-17 16:13:41 -0400. Do not edit! */
- 2 /* begin file include/simdutf.h */
- 3 // include/simdutf.h:1
- 4 #ifndef SIMDUTF_H
-...subprojects/simdutf/simdutf.h...
-
-[1] https://reproducible-builds.org/
-
-Upstream-Status: Submitted [https://github.com/simdutf/simdutf/pull/848]
-
-Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
----
- singleheader/amalgamate.py | 3 ++-
- 1 file changed, 2 insertions(+), 1 deletion(-)
-
-diff --git a/singleheader/amalgamate.py b/singleheader/amalgamate.py
-index 190b2f6..75e0d78 100755
---- a/singleheader/amalgamate.py
-+++ b/singleheader/amalgamate.py
-@@ -385,7 +385,8 @@ def filter_features(file):
- current_features = None
- elif enabled:
- if context.args.debug_sources and not prev_line.endswith('\\'):
-- yield f"// {file}:{lineno}"
-+ RELFILE = os.path.relpath(file, PROJECTPATH)
-+ yield f"// {RELFILE}:{lineno}"
-
- if line or (not line and prev_line):
- yield line
---
-2.48.1
-
diff --git a/meta/recipes-support/vte/vte_0.82.2.bb b/meta/recipes-support/vte/vte_0.84.0.bb
similarity index 90%
rename from meta/recipes-support/vte/vte_0.82.2.bb
rename to meta/recipes-support/vte/vte_0.84.0.bb
index d5dced4ce6..70cc6b3c99 100644
--- a/meta/recipes-support/vte/vte_0.82.2.bb
+++ b/meta/recipes-support/vte/vte_0.84.0.bb
@@ -18,10 +18,12 @@ GIDOCGEN_MESON_OPTION = "docs"
inherit gnomebase gi-docgen features_check upstream-version-is-even gobject-introspection systemd vala
SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch \
- file://0001-support-reproducibility-for-debug-sources.patch;patchdir=./subprojects/simdutf \
"
-SRC_URI[archive.sha256sum] = "e1295aafc4682b3b550f1235dc2679baa0f71570d8ed543c001c1283d530be91"
+SRC_URI[archive.sha256sum] = "0414e31583836aeb7878da25f67c515f7e8879917ecc37c92e26b83e8d8fc3e3"
+# remove the below line when updating to vte 0.84.1 (or higher) as it includes
+# https://gitlab.gnome.org/GNOME/vte/-/commit/77fe661760d2afac1e4d5a4b7eba477cbed6b430
+EXTRA_OEMESON += "-Dsimdutf:base64=true"
ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
--
2.47.3
next prev parent reply other threads:[~2026-06-19 8:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 8:32 [PATCH 01/15] gn: upgrade to latest revision Alexander Kanavin
2026-06-19 8:32 ` [PATCH 02/15] util-linux: upgrade 2.41.3 -> 2.42.2 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 03/15] lttng-tools: upgrade 2.14.1 -> 2.15.1 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 04/15] lttng-modules: upgrade 2.14.4 " Alexander Kanavin
2026-06-19 8:32 ` [PATCH 05/15] lttng-ust: upgrade 2.14.0 " Alexander Kanavin
2026-06-19 8:32 ` [PATCH 06/15] systemtap: upgrade 5.4 -> 5.5 Alexander Kanavin
2026-06-22 5:12 ` [OE-core] " Mathieu Dubois-Briand
2026-06-19 8:32 ` [PATCH 07/15] inetutils: upgrade 2.7 -> 2.8 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 08/15] debugedit: upgrade 5.2 -> 5.3 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 09/15] elfutils: upgrade 0.194 -> 0.195 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 10/15] libsolv: upgrade 0.7.37 -> 0.7.39 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 11/15] man-pages: upgrade 6.17 -> 6.18 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 12/15] parted: upgrade 3.6 -> 3.7 Alexander Kanavin
2026-06-19 8:32 ` [PATCH 13/15] librsvg: upgrade: 2.62.2 -> 2.62.3 Alexander Kanavin
2026-06-19 8:32 ` Alexander Kanavin [this message]
2026-06-19 8:32 ` [PATCH 15/15] ovmf: upgrade edk2-stable202511 -> edk2-stable202605 Alexander Kanavin
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=20260619083305.3505156-14-alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=alex@linutronix.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