comms/wsjtx: Update to 3.0.1
Release: WSJT-X 3.0.0-rc1
September 15, 2025
-------------------------
WSJT-X 3.0.0 introduces a number of new features and capabilities.
Release Candidates give advanced users an opportunity to exercise
new features and provide feedback to developers. If you use this
Release Candidate 1, please send related comments or questions to
one of our user forums.
The following features will be already familiar to those using one of
the WSJT-X Improved 2.8.0 i+ editions, but new to users of WSJT-X
2.7.0 and all earlier versions:
- Single-click Band Buttons can be enabled from the View menu.
- Filters can be used to suppress the display of various categories
[86 lines not shown]
e6000sw: Write the value, not the register, in Clause 45 writes
e6000sw_write_xmdio() loaded the Clause 45 register address into the
SMI PHY data register a second time, where the value to write belongs,
so every Clause 45 write stored the register address.
Its only caller, e6000sw_serdes_power(), runs at attach for ports 9 and
10 of the 88E6190 and 88E6190X to power one SERDES interface up and the
other down. It wrote 0x2000 to the SGMII control register and 0x1000
to the 10GBASE-R PCS control register instead, so neither interface was
powered down and the rest of each register was overwritten.
Fixes: 9aba06377d26 ("Add support for the Marvell 88E6190 11 ports switch.")
Sponsored by: Rubicon Communications, LLC ("Netgate")
security/vuxml: Document Elixir vulnerabilities
- add CVE-2026-109821 for URI.parse port limits
- add CVE-2026-115274 for JSON integer decoding beyond float64 range
- mark elixir before 1.18.6 and 1.19.7, and elixir-devel before 1.20.5
- add CVE-2026-97209 for mix deps.partition config, elixir-devel only
Sponsored by: SkunkWerks, GmbH
x11-fonts/rubik: Add Rubik font family
- add sans-serif font family with slightly rounded corners
- distribute the variable Roman and Italic fonts from the googlefonts
upstream, pinned to the e337a5 commit ("New binaries")
- supports Latin, Cyrillic, Hebrew, and Arabic scripts
Sponsored by: SkunkWerks, GmbH
iflib: Use a single tx dma map
The need for a separate map for TSO and non-TSO seems to have arisen from
a misunderstanding about the DMA requirements for Intel drivers like
ice/ixl/iavf. Specifically, this Intel hardware has a quirk where no
more than N (=8) segs can be DMA'ed per packet on the wire. This limit
was enforced using a DMA map with a low segment limit for non-TSO and a
driver specific check for TSO. This led to a *lot* of complexity in
iflib (~80 extra lines of code that this change removes) when the
limit can simply be enforced via the existing EFBIG mechanisms.
This change adds a new flag, IFLIB_SPARSE_TX, that drivers for hardware
with this quirk must set. When set, it causes non-TSO sends that
exceed isc_tx_nsegment to be treated as if bus_dmamap_load_mbuf_sg()
had returned EFBIG.
Due to the API/KABI change, I've bumped the FreeBSD version as well.
Note kgalazka suggested the flag, rather than a more awkward
[5 lines not shown]
textproc/py-mkdocs-simple-hooks: Mark DEPRECATED
Deprecated upstream, textproc/py-mkdocs 1.4+ has hooks built in.
Set EXPIRATION_DATE to 2026-11-30, as agreed with the maintainer.
PR: 299949
Approved by: Samir Noir <samir at noir.im> (maintainer)
MFH: 2026Q4
(cherry picked from commit 30927e6a7239c9908a09e45fc369b4e710103603)
textproc/py-mkdocs-simple-hooks: Mark DEPRECATED
Deprecated upstream, textproc/py-mkdocs 1.4+ has hooks built in.
Set EXPIRATION_DATE to 2026-11-30, as agreed with the maintainer.
PR: 299949
Approved by: Samir Noir <samir at noir.im> (maintainer)
MFH: 2026Q4
libthr: Create landing pad in thr_once in C++ exception
In _thr_once, if init_routine fails with exception, the stack allocate
__cup will become invalid when unwinder walk back and free the stack of
thr_once. This cause cleanup linked list be dangling. In here, we give
the cleanup function a landing pad so that we td can correctly point
to previous cleanup function.
Reviewed by: kib
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D61212
www/gitea: Security update 28.2.0 => 28.3.0, fix 21 CVEs
It contains a large number of security fixes, mostly around token
scopes, and bug fixes and performance improvements for Actions,
issues, pull requests and packages.
We strongly recommend that all users upgrade as soon as possible.
URL: https://blog.gitea.com/release-of-28.3.0/
PR: 300499
Approved by: portmgr@ (blanket, security fix)
MFH: 2026Q4
(cherry picked from commit 4d2e00911ddaa5f72c2833a803627a107da6be05)
libthr: Predict libthr is initialized in _thr_check_init
_thr_check_init() is called on hot paths such as pthread_once(), and
the uninitialized case can only happen once. Mark it with
__predict_false so the compiler lays out the initialized case as the
fall-through path.
Reviewed by: kib
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D61213
www/gitea: Security update 28.2.0 => 28.3.0, fix 21 CVEs
It contains a large number of security fixes, mostly around token
scopes, and bug fixes and performance improvements for Actions,
issues, pull requests and packages.
We strongly recommend that all users upgrade as soon as possible.
URL: https://blog.gitea.com/release-of-28.3.0/
PR: 300499
Approved by: portmgr@ (blanket, security fix)
MFH: 2026Q4
hastd: Remove pidfile on exit
Make hastd remove its pidfile before exit after catching a signal or a
stop control message, not just on failure to start.
MFC after: 1 week
Reviewed by: ngie
Differential Revision: https://reviews.freebsd.org/D60192
(cherry picked from commit 3f2f6bb8f7b562276bffd04a9ae4c05a351b4435)
hastd: Remove pidfile on exit
Make hastd remove its pidfile before exit after catching a signal or a
stop control message, not just on failure to start.
MFC after: 1 week
Reviewed by: ngie
Differential Revision: https://reviews.freebsd.org/D60192
(cherry picked from commit 3f2f6bb8f7b562276bffd04a9ae4c05a351b4435)
