Ubuntu also at it: https://ubuntu-archive-team.ubuntu.com/transitions/html/qt5-removal.html#!good,bad,partial,!unknown,!notintesting The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bdb7464de0b218785ab55a983ca37afa143e502f commit bdb7464de0b218785ab55a983ca37afa143e502f Author: Matt Jolly <kangie@gentoo.org> AuthorDate: 2025-01-28 22:33:24 +0000 Commit: Matt Jolly <kangie@gentoo.org> CommitDate: 2025-01-28 23:26:19 +0000 www-client/chromium: backport 'Qt5 optional' patch to M134 No revbump as this build-time change isn't worth forcing a rebuild for all users (and `dev` is unkeyworded). A new `dev` channel release is expected later this week. Closes: https://bugs.gentoo.org/926166 Bug: https://bugs.gentoo.org/948836 Signed-off-by: Matt Jolly <kangie@gentoo.org> www-client/chromium/chromium-134.0.6974.3.ebuild | 46 +++++++----------------- 1 file changed, 12 insertions(+), 34 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e1308318aba181f63efe86caf26fc119662f110 commit 6e1308318aba181f63efe86caf26fc119662f110 Author: Matt Jolly <kangie@gentoo.org> AuthorDate: 2025-01-28 22:23:21 +0000 Commit: Matt Jolly <kangie@gentoo.org> CommitDate: 2025-01-28 23:26:19 +0000 www-client/chromium: backport QT5 optional patch to M133 No revbump as it's not worth forcing one over this build-time change (and I expect a new release within 24h). Bug: https://bugs.gentoo.org/926166 Bug: https://bugs.gentoo.org/948836 Signed-off-by: Matt Jolly <kangie@gentoo.org> www-client/chromium/chromium-133.0.6943.27.ebuild | 40 +++++------------------ 1 file changed, 9 insertions(+), 31 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c53b3e80c419b5b94d94523085be6cb0fad8f86c commit c53b3e80c419b5b94d94523085be6cb0fad8f86c Author: Matt Jolly <kangie@gentoo.org> AuthorDate: 2025-01-28 22:10:09 +0000 Commit: Matt Jolly <kangie@gentoo.org> CommitDate: 2025-01-28 23:26:19 +0000 www-client/chromium: add 132.0.6834.159 This commit removes support for QT5 in Gentoo Chromium builds, other channels to follow shortly as the required patch has been backported. Bug: https://bugs.gentoo.org/948983 Bug: https://bugs.gentoo.org/926166 Bug: https://bugs.gentoo.org/948836 Signed-off-by: Matt Jolly <kangie@gentoo.org> www-client/chromium/Manifest | 2 + www-client/chromium/chromium-132.0.6834.159.ebuild | 1432 ++++++++++++++++++++ .../chromium/files/chromium-134-qt5-optional.patch | 133 ++ 3 files changed, 1567 insertions(+) Porting hints: https://doc.qt.io/qt-6/portingguide.html https://www.qt.io/blog/references-and-hints-about-porting-from-qt5-to-qt6 https://www.qt.io/blog/porting-from-qt-5-to-qt-6-using-qt5compat-library The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=454f20208208d20ce7d3ec82e82bb41dc032907f commit 454f20208208d20ce7d3ec82e82bb41dc032907f Author: Matt Jolly <kangie@gentoo.org> AuthorDate: 2025-03-06 08:41:31 +0000 Commit: Matt Jolly <kangie@gentoo.org> CommitDate: 2025-03-06 08:56:00 +0000 www-client/*: Chromium-based browsers: Drop the `qt5` USE The Chromium-based binary browsers (Chrome, Edge, Opera) ship binaries with a Qt5 shim for some dialogs (etc). Drop the USE, dependencies, and any related logic. Bug: https://bugs.gentoo.org/948836 Signed-off-by: Matt Jolly <kangie@gentoo.org> ...140.0.ebuild => microsoft-edge-dev-135.0.3140.0-r1.ebuild} | 11 ++--------- ...154.2.ebuild => microsoft-edge-dev-135.0.3154.2-r1.ebuild} | 11 ++--------- ...154.3.ebuild => microsoft-edge-dev-135.0.3154.3-r1.ebuild} | 11 ++--------- 3 files changed, 6 insertions(+), 27 deletions(-) |
Qt5 upstream OSS support ended on 2020-12-08. Since then, public availability of commercial 5.15 LTS releases is delayed by 1 year. That concerns anything they fix in their private 5.15 branch that is not a Qt6 fix and therefore backportable from public branches - backports, however, that also get more complex with every new Qt6 release. > - Most of KDE projects have ported away to Qt6. > - No other DE/WM based on Qt5 is left in ::gentoo to benefit from the option. > - Therefore I do not plan to put any more time into Qt5 packaging, much less > backporting LTS fixes to KDE Qt repositories. > - GCC, ICU, Python, ... may at any future release break Qt5, QtWebEngine in > particular. Since our users build from source, Gentoo gets hit first with any build issues. That means we can't sit back and do nothing until a real showstopper arrives. This tracker starts as a collection of tasks to port away from Qt5 while we still have time to: - check, if Qt6 support exists and just waits to be enabled, maybe after a version bump - for simple packages with qmake build system, check if s/eqmake5/eqmake6/ may works - go upstream to inform about the need to port to Qt6 or ask about project status for slow-moving repositories - collect patches from other distributions - port it ourselves and submit it upstream ofc