* Ports that were pinned to a deprecated version of Go (1.23 or older)
have been unpinned.
* Ports that were pinned to a still-supported version of Go (1.24 or
newer) have been converted to requesting that as their minimum Go
version.
* Ports that had been forcibly deprecated for pinning an expired Go
version have been undeprecated.
Recent versions of gettext no longer install m4 files in
PREFIX/share/aclocal. They have to be installed in the work
directory by autopoint for aclocal to find them.
Patch devel/autoconf so autoreconf runs autopoint when gettext related
macros are used in configure.ac (e.g. AM_ICONV). Previously it only
ran autopoint when AM_GNU_GETTEXT_(REQUIRE_)VERSION was used.
The following ports now require autopoint (i.e. USES=gettext-tools):
benchmarks/sysbench, devel/libhtp, editors/fxite, filesystems/rar2fs,
graphics/gd, net/ucarp, news/fidogate, sysutils/cdrdao
Other fixes:
emulators/mednafen, misc/lifelines: Use older version of gettext macros.
ftp/axel: Patch Makefile.am and configure.ac to get gettext working and
add NLS option.
ftp/wzdftpd: Use autoreconf 2.72.
mail/sympa: Remove hack from configure.ac.
multimedia/dvdauthor: Use ports autoreconf.
net/asterisk-chan_sccp: Drop autoreconf and gettext-tools dependencies.
security/pam_pkcs11: Patch configure.ac so autoreconf can find the
custom directory with m4 files.
sysutils/grub2-efi, sysutils/grub2-pcbsd: Add patch to run autoreconf
with -f flag so it updates all files.
www/wget2: Patch configure.ac to what autopoint expects.
PR: 287167
Exp-run by: antoine
There were two problems:
* Needed to backport a newer py-libzfs PR due to a libzfs API change
* Since 15.0 is now released, its OSVERSION reset to 1500000
PR: 291393
Sponsored by: ConnectWise
Approved by: Goran Mekić <meka@tilda.center> (maintainer)
MFH: 2025Q4
There is an $(edit) function for that which was not applied for
some reason, do that explicitly. While here, adjust the GitHub
entry in the WWW knob so it points to the project, not account.
PR: 290213
Reported by: Ron Wills
The following ports are skipped because they have been updated after 786cb608216ce14e8ced27108c96a1f2c8492fca.
- chinese/fcitx5-chinese-addons
- chinese/fcitx5-mcbopomofo
- devel/fatal
- devel/fbthrift
- devel/folly
- devel/spdlog
- mail/mu
- net/fb303
- net/mvfst
- net/wangle
- science/seacas
- security/fizz
- www/proxygen
and strip all lower bounds of 3.9 or 3.10 because they are implied now.
python:3.9-X -> python:-X
python:3.9+ -> python
python:3.10-X -> python:-X
python:3.10+ -> python
(options such as ,build preserved)
Fails to build on non x86 architectures
In file included from g_nbd.c:7:
In file included from /usr/src/sys/sys/param.h:117:
In file included from /usr/src/sys/sys/types.h:43:
./machine/endian.h:5:10: fatal error: 'x86/endian.h' file not found
5 | #include <x86/endian.h>
| ^~~~~~~~~~~~~~
1 error generated.
*** [g_nbd.o] Error code 1
FreeBSD Geom NBD Client is a Network Block Device (NBD) client for
the FreeBSD kernel GEOM framework.
The project consists of a kernel driver for the NBD GEOM class in
mod/ and a user library for the geom(8) control utility in lib/.
Release notes:
KIO FUSE 5.1.1 is the first release with officially stable support for Qt6/KF6.
With the next version, support for Qt5/KF5 will likely be dropped.
It's encouraged to build KIO FUSE with the same Qt major version as Dolphin,
so that they share KIO protocol implementations.
Compared to v5.1.0, the following changed:
- rmdir no longer deletes non-empty directories (https://bugs.kde.org/482902)
- Fix that Qt 6 applications falsely report that an open file that has been
deleted in the virtual filesystem still exists by reporting st_nlink = 0.
- Fix reporting of file/directory ownership when using local KIO protocols
with KIO 6
- Fix that the event loop got stuck waiting for FUSE events on FreeBSD >= 13
(before, setting O_NONBLOCK only worked by accident:
https://bugs.freebsd.org/265736#c5)
Known issues:
- Mounts are not persistent, which means that after reboot or logout the files
are not accessible through the FS until kio-fuse is triggered for them again.
- Some applications like VLC and MPV claim support for certain protocols, which
causes KIO to not use KIO FUSE in certain cases. Please mention which URL was
actually passed to the application when reporting an issue.
- Some protocols aren't compatible with KIO FUSE. man:/ is incompatible by
design: To serve index documents, it claims directories are files.
info:/ doesn't implement directories at all.
- Poor throughput especially on high latency connections. Work is ongoing to
improve the situation:
https://invent.kde.org/system/kio-fuse/-/merge_requests/36
- KIO 6 before 6.19 fails to report chown failures, resulting in test failures
like:
Actual (chown(mirroredFile.fileName().toUtf8().data(), getuid(), 0)): 0
Expected (-1) : -1
