Qt5: Update to 5.15.19
This is the final release of Qt5. If your port still uses Qt5 and could
possibly use Qt6 instead, now would be a good time to make the switch.
PySide2: Update to 5.15.19
Announcement:
https://lists.qt-project.org/pipermail/announce/2026-May/000626.html
Release notes:
https://code.qt.io/cgit/qt/qtreleasenotes.git/tree/qt/5.15.19/release-note.md
Qt5: Update to 5.15.18
This is the penultimate release of Qt5. While Qt5 is EOL, due to the
LGPL releases being a year behind the commercial releases, there will
still be one more patch release in May 2026.
PySide2: Update to 5.15.18
Announcement:
https://lists.qt-project.org/pipermail/announce/2025-October/000592.html
Release notes:
https://code.qt.io/cgit/qt/qtreleasenotes.git/tree/qt/5.15.18/release-note.md
MFH: 2025Q4
Qt5: Update to 5.15.17 (getting down to the end)
Upstream standard support for Qt5 is officially over. [1] In short,
that means get your ports off of Qt5 ASAP, especially end-user
applications. FreeBSD deprecation of Qt5 is coming soon! It will likely
be a year of lead time, but please help in the meantime and remove qt5
flavors and child ports whenever possible.
www/qt5-webengine has been updated to 5.15.19 with security patches up to
Chromium 135.0.7049.95. It's unclear at this point if further security
patches will be publically available. The Qt5 WebEngine component,
however, is and forever will be based on Chromium 87.0.4280.144, which
is over 4 years old. Props to upstream for their backports over all
these years and making them publically available (probably more to do
with licensing constraints than anything, but hey).
We otherwise depend on KDE as our direct upstream to roll our distfiles,
which we have been hosting locally for over 3 years. Since Qt upstream
drops the LGPL releases of Qt 5.15.x a year later, there's no guarantee
KDE will rebase their patchset over the next year for the remaining two
.18 and .19 releases. This might be the last update for Qt5 on FreeBSD.
[1] https://www.qt.io/blog/qt-5.15-extended-support-for-subscription-license-holders
Qt5: Update to 5.15.16
Update devel/pyside2* and devel/shiboken2 to 5.15.16
Update www/qt5-webengine to include the latest security fixes in
the chromium submodule [1]
Release note:
https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.16/release-note.md
MFH: 2024Q4
Security: 16e472d5-a8aa-11ef-b680-4ccc6adda413 [1]
Qt5: Update to 5.15.15
Update devel/pyside2* and devel/shiboken2 to 5.15.15
Update www/qt5-webengine to include the latest security fixes in
the chromium submodule
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.15/release-note.md
MFH: 2024Q3
Security: 66907dab-6bb2-11ef-b813-4ccc6adda413
Qt5: Update to 5.15.14
Update devel/pyside2* and devel/shiboken to 5.15.14
Update devel/qt5-script* and www/qt5-webengine to 5.15.17
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.14/release-note.md
Qt5: Update to 5.15.13
Update devel/pyside2* and devel/shiboken to 5.15.13
Update www/qt5-webengine to latest commit. Python 3.x support has been
integrated upstream, so local patches have been removed.
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.13/release-note.md
net/qt5-network: Address CVE-2023-51714
A potential integer overflow has been discovered in Qt's HTTP2
implementation. If the HTTP2 implementation receives more then 4GiB
in total headers, or more than 2GiB for any given header pair, then
the internal buffers may overflow.
Reported by: vvd via #freebsd-desktop
MFH: 2024Q1
Security: e2f981f1-ad9e-11ee-8b55-4ccc6adda413
Qt5: Update to 5.15.12
Update devel/pyside2* and devel/shiboken2 to 5.15.12
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.12/release-note.md
Qt5: Update to 5.15.11
Update devel/pyside2* and devel/shiboken2 to 5.15.11
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.11/release-note.md
Qt5: Update to 5.15.10
Update devel/qt5-script* and www/qt5-webengine to 5.15.15-lts
Update devel/pyside2* and devel/shiboken2 to 5.15.10
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.10/release-note.md
PR: 273934
Exp-run by: antoine
net/qt5-network: Fix for libressl 3.5
The OPENSSL_STACK functions are *not* available in LibreSSL.
Bump port revision, as the build was previously successful with
libressl 3.5.
Approved by: tcberner (kde, mentor)
Differential Revision: https://reviews.freebsd.org/D37043
Mk/Uses: always use colon for build/run suffix
Most USES use a colon for build/run(/test) suffixes. Change kde.mk,
qt.mk and pyqt.mk to do the same, and update all ports using that.
Document in CHANGES.
PR: 266034
Exp-run by: antoine
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D36349
net/qt5-network: Runtime fixes with libressl
Patches updated based on this gentoo patch:
https://562050.bugs.gentoo.org/attachment.cgi?id=663100
- modified and extended for qt-network 5.15.5
- modified for libressl 3.5
Differential Revision: https://reviews.freebsd.org/D35729
qt5: Update Qt to 5.15.5 (KDE patched)
- update patch-collection diff to be at the highest patch-level
- update patch-collection diff to be against 5.15.5 instead of 5.15.2
- update devel/qt5-script to 5.15.10
- libressl support by Felix Palmen <felix@palmen-it.de>
PR: 264944
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D35619
net/qt5-network: fix with LibreSSL 3.5
LibreSSL 3.5 opaqued many structs and implemented more functions
in line with OpenSSL 1.1
Approved by: tcberner (mentor, kde)
Differential Revision: https://reviews.freebsd.org/D34619
Qt: Switch Qt5 to use KDE's Qt patch collection
From [1]
What's this?
This is a set of git repositories based on the last public
commits available for Qt 5.15 branches with a curated collection
of patches on top to ensure open source products can be used
comfortably until users transition to their Qt 6-based ports.
Which patches does it include?
This collection of patches includes patches that fix at least
one of the following:
* Security issues
* Crashes
* Functional defects
We only include patches that have been approved upstream in the
Qt project. If a patch cannot be merged upstream for technical
reasons (e.g. the class no longer exists), it can also be
merged.
The patches to merge will be decided based on their relevance
towards Open Source products and their viability.
PR: 260548
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D33446
[1] https://community.kde.org/Qt5PatchCollection
net/qt5-network: fix build with LibreSSL 3.4.0
"Upstream has erroneous #ifdefs which will lead to a runtime abort
if both TLS1_3_VERSION and OPENSSL_NO_PSK are defined. Adjust
them."
Obtained from:
https://github.com/openbsd/ports/commit/21d28f231753b5cef153a8ff487573ab5994769e
Approved by: fluffy (mentor, kde)
Differential Revision: https://reviews.freebsd.org/D32286
net/qt5-network: fix build with LibreSSL 3.3.2
Since LibreSSL's libssl now exposes DTLS1_2_VERSION, configure
detects DTLS support which changes the DTLSv1_listen(3) signature
to one that LibreSSL has never supported. Force disable DTLS feature
for SSL_DEFAULT=libressl or libressl-devel.
Based on: https://github.com/openbsd/ports/commit/9942e8d28c4ec59d8d4a20b8bf219b10573c1f31
Reviewed by: tcberner (kde, mentor)
Approved by: fluffy (kde, mentor)
Differential Revision: https://reviews.freebsd.org/D29877
Update Qt/PySide2 to 5.15.2 / PyQt to 5.15.1 / SIP to 5.4.0 This commit combines several updates.
- Update Qt to 5.12.2
- Update PyQt to 5.15.1
- Since PySide 5.15.1 is broken with Qt 5.15.2, so PySide and Shiboken are also updated to 5.15.2.
- Update sip to 5.4.0
SIP is a collection of tools to create Python bindings for C and C++ libraries and used by PyQt and wxPython. There are some changes with sip5 [1]:
- python 3.5+ is required
- sip drops support of old deprecated methods as sipdistutils & cie.
- this version breaks also PyQt5 extension ABI. SIP files will be installed in ${PYTHON_SITELIBDIR}/PyQt${_PYQT_VERSION}/bindings
- some ports will use the new pyqtbuilder package with the pyproject.toml setup. Instead if the project have a setup.py, you should use sip-build to build it.
- if a port needs sip, it should also needs pysip. BTW, py-qt5-core requires pysip, so that should be enough for PyQt packages.
List of ports impacted by this change. Most of the patches have been integrated or are in the process of being integrated upstream:
- devel/libsavitar
- graphics/py-python-poppler-qt5
- net-im/scudcloud
- net/libarcus
- print/py-frescobaldi
- science/py-veusz
- graphics/qgis and graphics/qgis-ltr
- deskutils/calibre
A special note regarding calibre. New versions require sip>=5, we update it to the latest version (thanks to madpilot@)
science/scidavis will remove the PyQt binding soon and there is no patch planned, so we remove the python option (ok makc@)
While here, convert some ports to USE_PYQT (cad/cura, cad/uranium, devel/eric6, ...)
Thanks to tcberner and adridg!
[1] https://www.riverbankcomputing.com/static/Docs/sip/
PR: 250853
Exp-run by: antoine
Only define USE_LDCONFIG in devel/qt5-core
All the qt5-ports share the same library directory. devel/qt5-core is dependet on
by all others.
So there is no need to add identical entries to libdata/ldconfig, and restart the
ldconfig service on every pkg change of those ports.
Reported by: bapt
Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D27224
Update Qt5 to 5.15
This is a major upgrade of the Qt libraries [1], [2].
* People that use upgrading mechanisms with incomplete dependency handling
(portmaster & Co) should make sure to manually remove the existing Qt
packages to guarantee a safe upgrade. Keep in mind, that Qt does not like if
you have an incomplete upgrade.
* This version of Qt drops support for OpenSSL 1.0 -- this means that there
won't be any binary packages for Qt5 provided by the FreeBSD package builders
for FreeBSD 11.x anymore -- and the same for *all* the ports depending on
net/qt5-network [3]. If you cannot upgrade to a more recent FreeBSD
version (12.x, 13.x), you will need to build Qt5 from ports while switching
to an SSL implementation from ports.
Big thanks are due for
* kai@ for updating webengine (also mikael@)
* Felix Palmen for providing LibreSSL support patches
* adridg@ and lbartoletti@ for helping me fix the fallout
[1] https://www.qt.io/blog/qt-5.15-released
[2] https://wiki.qt.io/New_Features_in_Qt_5.15
[3] https://www.freshports.org/net/qt5-network
PR: 247010
Exp-run by: antoine
net/qt5-network: readd support for LibreSSL
- as with every Qt5 upgrade, we dropped LibreSSL support
- this readds it
PR: 245600
Submitted by: rozhuk.im@gmail.com
Reported by: p5B2E9A8F@t-online.de
Update Qt5 to 5.14.2
Very big thanks go again to kai@ who provided the www/qt5-webengine upgrade (to 5.14.0).
Notably, video capture support was re-enabled.
Announcement:
https://www.qt.io/blog/qt-5.14-has-released
PR: 244964
Exp-run by: antoine
net/qt5-network: readd support for LibreSSL
- as with every Qt5 upgrade, we dropped LibreSSL support
- this readds it
PR: 240962
Submitted by: Walter Schwarzenfeld <w.schwarzenfeld@utanet.at>
Qt5 update to 5.13.0
For new features, check: https://wiki.qt.io/New_Features_in_Qt_5.13
Thanks to adridg who helped to fix a lot of packages.
Exp-run by: antoine
PR: 238782
Bump PORTREVISION for ports depending on the canonical version of GCC as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3 to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
net/qt5-network: Add patch from Qt upstream fixing QDnsLookup.
This should fix bug in net-im/psi, when connecting to some servers was failing.
Reviewed by: tcberner (mentor)
Update Qt5 to 5.12.1
Release announcement:
https://blog.qt.io/blog/2019/02/01/qt-5-12-1-released/
Changelog:
https://wiki.qt.io/Qt_5.12.1_Change_Files
- A change was required to qt-dist.mk to always pass LOCALBASE to qmake,
as Qt5 has been installed to a prefix for some time now, there should
not be any harm in that, with respect to it picking up installed versions
of itself during build.
PR: 235622
Exp-run by: antoine
Fix Qt5 symbol version scripts to put the catch-all clause first. When a symbol matches multiple clauses the last one takes precedence. If the catch-all is last it captures everything. In the case of Qt5 libraries this caused all symbols to have a Qt_5 label while some should have Qt_5_PRIVATE_API. This only affects lld because GNU ld always gives the catch-all lowest priority.
Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium. Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3] The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one. If there's no such non-weak symbol the call
in the weak wrapper resolves to the weak wrapper itself creating an infinite
call loop that overflows the stack and causes a crash. Some of the
allocation functions are variants of C++ new and delete and it probably
depends on the compiler whether these variants are used in other parts of
Qt5Webengine.
Remove the weak wrappers (make them Linux specific). This isn't binary
compatible but we are already breaking that with the changes to the symbol
versions.
[1] https://github.com/qt/qtwebengine/commit/5c2cbfccf9aafb547b0b30914c4056abd25942a4
[2] https://github.com/qt/qtwebengine/commit/2ed5054e3a800fa97c2c9e920ba1e6ea4b6ef2a5
[3] https://github.com/qt/qtwebengine/commit/009f5ebb4bd6e50188671e0815a5dae6afe39db5
Bump all ports that depend on Qt5.
PR: 234070
Exp-run by: antoine
Approved by: kde (adridg)
Be more defensive in Qt5Network code.
It's possible, but rather unlikely, to build Qt5Network with
QT_NO_NETWORKINTERFACE, and still get around to building the
generic bearer. In that case, comment out the workaround
that needs an interface.
PR: 232784
Obtained from: Max Steciuk
Update net/qt5-network to build against LibreSSL.
Patches by Charlie Li / ml_vishwin, with explanation in the patches.
Builds on 11.2 (ssl=unset, base, openssl) and 12.0 (ssl=unset, base,
libressl). Tested with otter-browser on 12.0 (ssl=unset, libressl).
PR: 234078
Submitted by: Charlie Li
Reported by: W. Schwarzenfeld
Differential Revision: https://reviews.freebsd.org/D18582
Fix net/qt5-network in the face of VLANs.
Adding a VLAN to a FreeBSD system caused memory corruption -- usually
enough to make rtld fall over with symbol resolution errors, although
in DEBUG builds it would just crash. Revamp network interface discovery
to not be full of memory gotcha's.
An explanation is included in the patches. While here, "make makesum"
has moved some files around.
PR: 231402, 233798, 232318
Reported by: Ting-Wei Lan, Nils Beyer, Marek Zarychta
Update Qt5 to 5.12.0
http://blog.qt.io/blog/2018/12/06/qt-5-12-lts-released/
- This breaks support for libressl again. Patches are welcome.
PR: 233705
Exp-run by: antoine
Bump PORTREVISION for ports depending on the canonical version of GCC defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590