I'm not giving the usual fanfare. This has been an absolute slog.
Ports changes:
qt6-base: Added WAYLAND option. This is congruent with the X11 option.
We really don't recommend disabling this option, but it is
available for advanced users who don't want wayland for
whatever reason.
This dep is required by the at-spi-bus-launcher program installed by
this package.
Not bumping PORTREVISION as I'm going to update the port in quick succession.
Upstream is gone and port is unfetchable, claimed successor is gone
and additionally it also depends on QT 5 which is going away
Reference:
https://github.com/ArtrixTech/DynaGammy
PR: 289509
Approved by: maintainer timeout, 3+ weeks
September 30, 2025 by Jani Heikkinen
The last release from the Qt 6.9 series, Qt 6.9.3, is now available for
download. As a patch release, Qt 6.9.3 does not introduce new features
but delivers over 250 bug fixes, security updates, and enhancements on
top of the Qt 6.9.2 release. For a detailed breakdown of the most
significant changes, refer to the Qt 6.9.3 release notes.
Announcement:
https://www.qt.io/blog/qt-6.9.3-released
Release notes:
https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.9.3/release-note.md
FreeBSD ports changes:
devel/qt6-base:
- Remove a few stale patches and use dlsym to access environ. [1]
- Restore missing headers if the X11 option is disabled. [2]
devel/qt6-tools:
- Add support for devel/llvm21
www/qt6-webengine:
- Use dlsym to access environ. [1]
PySide6: Update to 6.9.3
As part of the Qt6 update, PySide6 and its support tools have also been
updated to 6.9.3.
Reported by: arrowd [1], angry_vincent on #freebsd-desktop [2]
MFH: 2025Q4
Security: c27c05a7-a0c8-11f0-8471-4ccc6adda413
Pull Request: https://github.com/freebsd/freebsd-ports/pull/441 [1]
Co-authored-by: Gleb Popov <arrowd@FreeBSD.org>
August 27, 2025 by Jani Heikkinen
We are excited to announce the release of Qt 6.9.2! As a patch release,
Qt 6.9.2 does not introduce new features but delivers over 550 bug fixes,
security updates, and enhancements on top of the Qt 6.9.1 release. For a
detailed breakdown of the most significant changes, refer to the
Qt 6.9.2 release notes.
Announcement:
https://www.qt.io/blog/qt-6.9.2-released
Release notes:
https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.9.2/release-note.md
MFH: 2025Q3
Security: edf83c10-83b8-11f0-b6e5-4ccc6adda413
2a11aa1e-83c7-11f0-b6e5-4ccc6adda413
The condition in the former patch makes the port use the date-tz
library of devel/date even when libc++ supports
std::chrono::current_zone, etc. Checking
_LIBCPP_HAS_NO_TIME_ZONE_DATABASE is enough and it won't be defined by
libstdc++.
Reported by: jbeich (via ports-committers)
Fixes: d9a1aaa98d16 (accessibility/hyprsunset: update to 0.3.1)
Commit 815623f49eb59d0946f08b569c5b2ddb655ee3f4 was incorrect and only changed glibmm->glibmm26 dependency for accessibility/atkmm
Partially revert it.
PR: 288434
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.
Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.
PR: 274671
Event: Kitchener-Waterloo Hackathon 202506
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
