sqlite3: Update to 3.50.4
sqlite3: Update to 3.50.4
Hmmm, I wonder if 0 is the right thing vs something like 0xdeadc0de. We have a few explicit IVAR handlers that intentionally return a default value (e.g. acpi_get_handle()) and those do tend to be zero (and in those cases we don't KASSERT). I have a patch in a branch to add a new one like that for ThunderBolt PCI bridges even. 0 is probably fine as a default, but @imp might also have an opinion.
tcp: retire do_newsack - always adhere to RFC6675 SACK
snmp_pf: use the libpfctl wrapper to retrieve astats
pf: convert DIOCRGETASTATS to netlink
pfctl: move astats query into libpfctl
www/py-django-q2: Upgrade to 1.9.0
textproc/py-zensical: Update to 0.0.11
www/apache24: Security update to 2.4.66
vvd committed
R11:94b26a67c9b8: databases/adminer: Fix distinfo (authored by Paavo-Einari Kaipila <pkaipila@gmail.com>).
databases/adminer: Fix distinfo
graphics/p5-Image-ExifTool-devel: Update 13.42 => 13.43
I've been traveling and haven't yet had time to review the latest changes, but last I looked it was moving in the right direction. Just give me a few more days.
security/lego: update to 4.29.0
xhci: Correct name of HCCPARAMS Register
xhci: Add header values for Debug Capability (DbC)
xhci: Add some Alder lake device ids
phylosophically this interface more like L2 loopback, right?
can be emulated by ng_ether somehow?
textproc/sttr: update to version 0.2.28
www/ilias: Update to 10.3
graphics/mapserver: Update to 8.6.0
www/rubygem-cssbundling-rails-gitlab: Remove expired port
cad/symbiyosys: update 0.58 → 0.60
devel/shedskin: update 0.9.10 → 0.9.11
cad/yosys: update 0.58 → 0.60
shells/nushell: update 0.108.0 → 0.109.1
sysutils/mise: update 2025.11.8 → 2025.12.0
finance/hs-hledger: update 1.50.2 → 1.50.4
devel/camp: update 2025.09.1 → 2025.12.0
ports-mgmt/pkg-devel: update to 2.4.99.1
cam: set reladr in scsi_read_capacity_16
www/py-django60: Add new port
x11/cinnamon-desktop: update to 6.4.2
security/vuxml: Out of bounds read in graphics/png
devel/cmake*: Update to 3.31.10
www/py-frappe-bench: Unbreak build
audio/mac: Update to 11.89
www/domoticz-devel: Update to 2025.2.16990
I think I'll try my luck with first and fit it into our example and once the version works, see what are the values of compared to the ones in kqueue scenario. My thinking is "if I can't fix it, move to simpler example", which I'm hoping the official docs are. Anyway, I didn't give up on this code, I just need to approach it from the different angle, for now.
freebsd-base.7: Document the optional set
x11-toolkits/como: Prepare for Qt 6.10
www/dooble: Prepare for Qt 6.10
x11/disman: Prepare for Qt 6.10
multimedia/obs-studio: Prepare for Qt 6.10
net-im/libquotient: Prepare for Qt 6.10
graphics/wrapland: Prepare for Qt 6.10
math/rkward: Prepare for Qt 6.10
x11/hyprland-qtutils: Prepare for Qt 6.10
print/scribus-devel: Prepare for Qt 6.10
net-im/nheko: Prepare for Qt 6.10
multimedia/subtitlecomposer: Prepare for Qt 6.10
finance/kmymoney: Prepare for Qt 6.10
misc/hyprqt6engine: Prepare for Qt 6.10
emulators/yuzu: Prepare for Qt 6.10
emulators/pcsx2: Prepare for Qt 6.10
games/gcompris-qt: Prepare for Qt 6.10
emulators/fbsd-duckstation: Prepare for Qt 6.10
emulators/rpcs3: Prepare for Qt 6.10
emulators/dolphin-emu: Prepare for Qt 6.10
devel/zeal: Prepare for Qt 6.10
devel/qxlsx: Prepare for Qt 6.10
deskutils/kdeconnect-kde: Prepare for Qt 6.10
deskutils/copyq: Prepare for Qt 6.10
audio/musescore: Prepare for Qt 6.10
audio/fooyin: Prepare for Qt 6.10
audio/cantata: Prepare for Qt 6.10
x11/xwaylandvideobridge: Mark for removal
math/labplot: Update to 2.12.1
misc/qt6ct: Update to 0.11
No longer immediately relevant after the revert. Worth discussing the venn diagram regarding et al since there are gotchas in C as well.
misc/grok-cli: New port: Open-source AI agent bringing Grok to your terminal
Revert "stddef.h: add unreachable() for C23 compliance"
java/bouncycastle: fix compilation with jdk11 and jdk17
devel/RStudio: Add COPILOT option; Fix fetch; Fix WITH_QUATRO option