Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Quentin Schulz <foss+buildroot@0leil.net>,
	 Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH 2025.02.x 5/5] package/qt5: bump packages to latest 5.15 kde submodule version
Date: Sun, 07 Jun 2026 07:41:37 +0300	[thread overview]
Message-ID: <87bjdn9d32.fsf@tarshish> (raw)
In-Reply-To: <20260605125009.272558-1-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Fri, 5 Jun 2026 14:50:08 +0200")

Hi Thomas,

On Fri, Jun 05 2026, Thomas Perale via buildroot wrote:
> In reply of:
>> Bump qt5 packages to latest submodule versions from
>> https://invent.kde.org/qt/qt/qt5/-/tree/kde/5.15
>> 
>> qtbase repo is a few commits after a tag named v5.15.18-lts-lgpl so
>> assume it's now 5.15.18.
>> 
>> qt5base patches are updated to make them apply silently and cleanly.
>> 
>> For qt5webengine-chromium:
>> - 0001-Add-python3-build-support.patc is removed as commit 68302c9ea158
>>   ("Enable building with Python 3") contains similar changes,
>> - 0004-Migrate-presubmit-to-python3.patch is only partially kept as
>>   commit 68302c9ea158 ("Enable building with Python 3") contains similar
>>   changes,
>> - 0006-Fix-build-in-Python-3.11-invalid-mode-rU.patch is only partially
>>   kept as commit 68302c9ea158 ("Enable building with Python 3") contains
>>   similar changes,
>> - 0007-Replace-imp.load_source-with-importlib-equivalent.patch is
>>   removed as commit 68302c9ea158 ("Enable building with Python 3")
>>   contains similar changes,
>> - 0010-Fix-building-with-system-libxml2.patch is removed as commit
>>   c98d28f2f0f2 ("Fix building with system libxml2") contains similar
>>   changes,
>> - 0012-Include-cstdint-for-uintptr_t-uint8_t-etc.patch is renamed
>>   0009-Include-cstdint-for-uintptr_t-uint8_t-etc.patch and contains more
>>   file patching to make qt5webengine build again,
>> 
>> For qt5webengine:
>> - 0002-Add-python3-build-support.patch is removed as commit 2294cc4ed5fd
>>   ("Add option to chose python version for building 5.15 WebEngine")
>>   contains similar changes. It now supports both Python2 and Python3 and
>>   defaults to Python2 if found first. This can be overridden with
>>   -webengine-python-version python3 in QT5WEBENGINE_CONF_OPTS but this
>>   was unnecessary in my tests as Python3 was properly selected from
>>   $(HOST_DIR)/bin/.
>> 
>> qt5webengine-chromium is updated with qt5webengine following the logic
>> stated in Buildroot commit c53455ea4ffa
>> ("package/qt5/qt5webengine-chromium: bump version after qtwebengine
>> bump").
>> 
>> I am unsure whether qt5webengine-chromium-catapult also requires an
>> update.
>> 
>> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
>> [qt5webengine-chromium/0011-Shorted-printed-cmd-when-long-commands-fail.patch
>>  doesn't exist in 2025.02.x, file renaming not done]
>> [qt5webengine-chromium/0012-Include-cstdint-for-uintptr_t-uint8_t-etc.patch
>>  is named 0011-Include-cstdint-for-uintptr_t-uint8_t-etc.patch in
>>  2025.02.x, adapt renaming]
>> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> Applied to 2025.02.x & 2026.02.x. Thanks

Not in 2025.02.x as of a20dafe5c190a7 ("package/pkg-generic: Add
/usr/share/info/dir to $(2)_DROP_FILES_OR_DIRS"), or in 2026.02.x as of
commit 2121a13066e52 ("package/redis: update CPE vendor").

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-06-07  4:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 11:01 [Buildroot] [PATCH 2025.02.x 0/5] package/qt5: misc fixes + bump to 5.15.18 Quentin Schulz via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 1/5] package/qt5/qt53d: disable assimp support when BR2_PACKAGE_ASSIMP is not set Quentin Schulz via buildroot
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 2/5] package/qt5/qt53d: force using Buildroot's assimp when selected Quentin Schulz via buildroot
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 3/5] package/qt5/qt53d: always disable assimp support Quentin Schulz via buildroot
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 4/5] package/qt5/qt5webengine-chromium: fix zlib license hash Quentin Schulz via buildroot
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-03-24 11:01 ` [Buildroot] [PATCH 2025.02.x 5/5] package/qt5: bump packages to latest 5.15 kde submodule version Quentin Schulz via buildroot
2026-03-27 16:58   ` Quentin Schulz via buildroot
2026-04-10 10:09     ` Thomas Perale via buildroot
2026-06-08 10:28       ` Quentin Schulz via buildroot
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-06-07  4:41     ` Baruch Siach via buildroot [this message]

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=87bjdn9d32.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=foss+buildroot@0leil.net \
    --cc=thomas.perale@mind.be \
    /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