From: Waldemar Brodkorb <wbx@openadk.org>
To: Angelo Compagnucci <angelo.compagnucci@gmail.com>
Cc: buildroot@buildroot.org,
Quentin Schulz <quentin.schulz@cherry.de>,
Joshua Henderson <joshua.henderson@microchip.com>,
Bartosz Bilas <b.bilas@grinn-global.com>,
Peter Seiderer <ps.report@gmx.net>,
Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [PATCH 0/2] package/qt5: security bump to version 5.15.19
Date: Tue, 10 Nov 2026 06:28:03 +0100 [thread overview]
Message-ID: <avKrY-io3kEIaRen@waldemar-brodkorb.de> (raw)
In-Reply-To: <20261109130533.4171508-1-angelo.compagnucci@gmail.com>
Hi Angelo, all,
Angelo Compagnucci wrote,
> This bumps the qt5 packages to Qt 5.15.19, from the kde/5.15 branch of
> KDE's Qt5 Patch Collection, which is now rebased on it. qt5webengine
> is bumped in its own patch, as it drops and refreshes some patches of
> qt5webengine-chromium.
>
> This should be the last Qt5 bump: Qt 5.15.19 is the very last Qt 5.15
> release, and the Qt Company ended its support of Qt 5.15 after 26 May
> 2025 [1]. KDE keeps its Qt5 Patch Collection only for the open source
> projects still on Qt 5.15 until they move to Qt 6, and only for very
> critical fixes [2]. Qt5 users should plan their move to Qt6.
>
> FYI: I am working on a series moving the Qt5 users to Qt6 and removing
> Qt5 from Buildroot. Before sending it, I would like to get feedback on
> this: would the removal be welcome, and when (for example after the
> next LTS)?
We are still using QT5, so it would be nice to keep it for the next
LTS and remove it afterwards.
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-11-10 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:05 [Buildroot] [PATCH 0/2] package/qt5: security bump to version 5.15.19 Angelo Compagnucci
2026-11-09 13:05 ` [Buildroot] [PATCH 1/2] " Angelo Compagnucci
2026-11-09 21:13 ` Julien Olivain via buildroot
2026-11-09 13:05 ` [Buildroot] [PATCH 2/2] package/qt5/qt5webengine: " Angelo Compagnucci
2026-11-09 13:42 ` [Buildroot] [PATCH 0/2] package/qt5: " Quentin Schulz via buildroot
2026-11-09 13:56 ` Angelo Compagnucci
2026-11-10 5:28 ` Waldemar Brodkorb [this message]
2026-11-10 13:57 ` Angelo Compagnucci
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=avKrY-io3kEIaRen@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=angelo.compagnucci@gmail.com \
--cc=b.bilas@grinn-global.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=joshua.henderson@microchip.com \
--cc=ps.report@gmx.net \
--cc=quentin.schulz@cherry.de \
/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