libifconfig: Fix table size
Tables that have one element per protocol or address family were
previously sized by AF_MAX + 1 since AF_MAX was off by one. Now that
AF_MAX has been corrected, we need to apply the opposite correction to
these tables.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
MFC after: 3 days
Sponsored by: Klara, Inc.
Sponsored by: NetApp, Inc.
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D58827
(cherry picked from commit 79a6ad63e6afdfa00d0e625996bddf91e9f217c3)
routing: Fix table sizes
Tables that have one element per protocol or address family were
previously sized by AF_MAX + 1 since AF_MAX was off by one. Now that
AF_MAX has been corrected, we need to apply the opposite correction to
these tables.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
MFC after: 3 days
Sponsored by: Klara, Inc.
Sponsored by: NetApp, Inc.
Reviewed by: pouria, kevans, glebius
Differential Revision: https://reviews.freebsd.org/D58826
(cherry picked from commit 6c41d928bcd763ec60d55bec2886c05b03cf9e6a)
ifnet: Restore previous size of if_afdata
Struct ifnet contains an array if_afdata of AF_MAX pointers to address
information for each possible address family. Since 2013, when AF_MAX
was inadvertently changed to be equal to the highest possible value,
instead of one more than the highest possible value, this array has been
too small in theory, but this never mattered in practice because the
higher address families were not assignable to interfaces.
My recent commit which corrected the value of AF_MAX had the side effect
of breaking the KBI by changing the size and layout of struct ifnet.
This manifested itself as kernel panics when using third-party network
drivers and went unnoticed in main because if_afdata no longer exists
there. Address the issue for stable/15 and stable/14 by keeping the
correct value of AF_MAX but deliberately making if_afdata off by one,
restoring its previous size.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
Sponsored by: Klara, Inc.
[3 lines not shown]
ifnet: Restore previous size of if_afdata
Struct ifnet contains an array if_afdata of AF_MAX pointers to address
information for each possible address family. Since 2013, when AF_MAX
was inadvertently changed to be equal to the highest possible value,
instead of one more than the highest possible value, this array has been
too small in theory, but this never mattered in practice because the
higher address families were not assignable to interfaces.
My recent commit which corrected the value of AF_MAX had the side effect
of breaking the KBI by changing the size and layout of struct ifnet.
This manifested itself as kernel panics when using third-party network
drivers and went unnoticed in main because if_afdata no longer exists
there. Address the issue for stable/15 and stable/14 by keeping the
correct value of AF_MAX but deliberately making if_afdata off by one,
restoring its previous size.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
Sponsored by: Klara, Inc.
[3 lines not shown]
libifconfig: Fix table size
Tables that have one element per protocol or address family were
previously sized by AF_MAX + 1 since AF_MAX was off by one. Now that
AF_MAX has been corrected, we need to apply the opposite correction to
these tables.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
MFC after: 3 days
Sponsored by: Klara, Inc.
Sponsored by: NetApp, Inc.
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D58827
(cherry picked from commit 79a6ad63e6afdfa00d0e625996bddf91e9f217c3)
routing: Fix table sizes
Tables that have one element per protocol or address family were
previously sized by AF_MAX + 1 since AF_MAX was off by one. Now that
AF_MAX has been corrected, we need to apply the opposite correction to
these tables.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
MFC after: 3 days
Sponsored by: Klara, Inc.
Sponsored by: NetApp, Inc.
Reviewed by: pouria, kevans, glebius
Differential Revision: https://reviews.freebsd.org/D58826
(cherry picked from commit 6c41d928bcd763ec60d55bec2886c05b03cf9e6a)
zonectl: Consistently report ZAC conv. zones WP LBA
On ZAC drives, conventional zones conventionally report a write pointer
LBA of 0xffffffffffff. This field is 48 bits wide, unlike ZBC's 64 bits.
Recognize both ZAC and ZBC all-ones behaviour in the WRITE POINTER LBA
field to indicate non-valid information.
Tested by: fuz
Discussed with: fuz, asomers, ken
Fixes: 4735ef6196bc ("zonectl: display conventional zones better")
MFC after: 2 weeks
Sponsored by: Google Summer Of Code 2026
Reviewed by: asomers
Pull Request: https://github.com/freebsd/freebsd-src/pull/2345
mail/mailman3: Update rc.d script
Fix the exit code of "service mailman status". Mailman's own status
command exits 0 when it is not running and 1 when it is, which is the
inverse of the rc.subr convention. Wrap it so that a running master
yields 0, as service(8) consumers such as Ansible expect.
Also add a start_precmd that detects an already running master via the
pidfile, so that "service mailman start" no longer dumps a full click
usage block on a second invocation.
PR: 292404
Sponsored by: Netzkommune GmbH
(cherry picked from commit ae15f89980dff827563056d876641f942a70c6dd)
mail/mailman3: Update rc.d script
Fix the exit code of "service mailman status". Mailman's own status
command exits 0 when it is not running and 1 when it is, which is the
inverse of the rc.subr convention. Wrap it so that a running master
yields 0, as service(8) consumers such as Ansible expect.
Also add a start_precmd that detects an already running master via the
pidfile, so that "service mailman start" no longer dumps a full click
usage block on a second invocation.
PR: 292404
Sponsored by: Netzkommune GmbH
games/robocode-naval: Ignore portscout
robocode-naval and robocode share the same SourceForge project, so
portscout keeps reporting games/robocode versions as new releases for
this port. Naval Robocode has its own versioning scheme (0.9.2 being
the latest), so just ignore it.
epair: allow disabling receive checksum offloading
Allow disabling RXCSUM and RXCSUM6 on an epair interface. If disabled,
epair unsets the mbuf flags that indicate a valid checksum when
transferring a packet from one epair end to the other. This gives a
user in a jail the power to control whether the user wants to use the
result of a previous validation (by a physical interface) or not.
Reviewed by: kp, tuexen
MFC after: 1 month
MFC to: stable/15
Differential Revision: https://reviews.freebsd.org/D58786
doc: Update source files (en .po), for translations
The changes are mostly from a po4a upgrade. Comments don't need
translator review.
Only a few lines losing line breaks need review. This affects only some
strings.
www/immich-ml: Add New Port
Machine-learning service for Immich providing smart search (CLIP),
duplicate detection and facial recognition via onnxruntime on the
CPU. Models are downloaded on first use into the cache directory.
OCR is not yet available as rapidocr has no FreeBSD port.
WWW: https://immich.app/
Sponsored by: Netzkommune GmbH
www/immich: Add New Port
High performance self-hosted photo and video management solution.
This port contains the Immich server including the bundled web
frontend, built natively with node22/pnpm against the system
libvips. Requires PostgreSQL with the pgvector and vchord
extensions and a Redis-compatible cache such as valkey. Smart
search, duplicate detection and facial recognition additionally
require the machine-learning service from www/immich-ml.
WWW: https://immich.app/
Sponsored by: Netzkommune GmbH
misc/py-insightface: Add New Port
Open source 2D and 3D face analysis library based on ONNX models
executed with onnxruntime. Required by www/immich-ml for facial
recognition. The upstream pretrained models are downloaded at
runtime and licensed for non-commercial research use only.
WWW: https://insightface.ai/
Sponsored by: Netzkommune GmbH
devel/py-aiocache: Add New Port
Multi backend asyncio cache framework for Python. Required by the
upcoming Immich machine-learning service (www/immich-ml).
WWW: https://github.com/aio-libs/aiocache
Sponsored by: Netzkommune GmbH
security/putty*: Security update 0.84 => 0.85
While here, add USE_XORG+=xrender since pterm seems to be linked to it.
Changelog: https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
PR: 297593
Reported by: mandree (maintainer)
Approved by: osa, vvd (Mentors, implicit)
MFH: 2026Q3
devel/py-pytest-cov: Update to 6.3.0
Adjust the dependencies to what upstream now requires and drop the six
test dependency, which is no longer used. The sdist was renamed to use
an underscore, so set DISTNAME accordingly.
Newer versions require devel/py-coverage 7.10.6 or later, which is not
in the tree yet.
Changes: https://github.com/pytest-dev/pytest-cov/blob/v6.3.0/CHANGELOG.rst
devel/py-itemloaders: Update to 1.4.0
Switch to PEP 517, upstream now builds with hatchling and no longer
ships setup.py. Drop the w3lib run dependency, it is no longer
required.
Changes: https://github.com/scrapy/itemloaders/blob/v1.4.0/docs/news.rst
Reported by: portscout
