www/immich: Switch to jellyfin-ffmpeg
Immich builds its HDR filter chain around tonemapx, which only the
Jellyfin patch set provides. The rc script points FFMPEG_PATH and
FFPROBE_PATH at it.
PR: 298378
Requested by: several people
Sponsored by: Netzkommune GmbH
hastd: Use fixed-length protocol names
All communication between hastd nodes and internally between hastd and
its worker children passes through the same pair of send / receive
functions. The receive function uses recv(2) with the MSG_WAITALL flag,
which in theory means we should never get a short read. However, when
handing off a socket to a worker child, we also pass a variable-length
string identifying the type of socket we're passing, and reading this
string relies on a short read. This used to work because the arrival of
the descriptor would interrupt the recv(2) call, but this bug was fixed
when the AF_UNIX code was rewritten a while ago and hastd has been
broken ever since.
Fixing the length of the protocol name to four characters including the
terminating null solves the short-read bug by never requiring a short
read (nothing else in hastd requires one).
Note that this issue appears to have been reported independently first
by Alessandro Sagratini in PR 292322 and then by Martin Vidovic in
[11 lines not shown]
hastd: Ensure nvpair padding is initialized
The proto-libnv implementation embedded in hastd pads names and values
out to the nearest multiple of eight bytes, but leaves the padding
uninitialized, leaking up to 14 bytes of recycled heap per pair in a
message.
While here, switch from bcopy() to memcpy().
MFC after: 3 days
Reviewed by: kevans, emaste
Differential Revision: https://reviews.freebsd.org/D59343
(cherry picked from commit 911bda7cffbf358c4e83ea05cfe980d429aff61c)
tests: Fix graid3 insert tests
The script was passing the wrong device name to `graid3 insert` and
didn't notice that the command was failing.
MFC after: 1 week
Event: EuroBSDcon 2026 DevSummit
Reviewed by: delphij
Differential Revision: https://reviews.freebsd.org/D59564
(cherry picked from commit 4cc85d1f00fa1938923fe8d6fc2934593d4303b4)
graid3: Restore lock acquisition
The lock acquisition in g_raid3_ctl_insert() was improperly dropped a
while ago, making it impossible to add or replace a device in an
existing graid3. This went unnoticed because the tests are broken.
MFC after: 1 week
Fixes: fcf69f3dbce6 ("Consistently use gctl_get_provider instead of home-grown variants.")
Event: EuroBSDcon 2026 DevSummit
Reviewed by: delphij
Differential Revision: https://reviews.freebsd.org/D59563
(cherry picked from commit 9094f86b57a7e4b356cae83f35c8d41c842b42a2)
hastd: Ensure nvpair padding is initialized
The proto-libnv implementation embedded in hastd pads names and values
out to the nearest multiple of eight bytes, but leaves the padding
uninitialized, leaking up to 14 bytes of recycled heap per pair in a
message.
While here, switch from bcopy() to memcpy().
MFC after: 3 days
Reviewed by: kevans, emaste
Differential Revision: https://reviews.freebsd.org/D59343
(cherry picked from commit 911bda7cffbf358c4e83ea05cfe980d429aff61c)
hastd: Use fixed-length protocol names
All communication between hastd nodes and internally between hastd and
its worker children passes through the same pair of send / receive
functions. The receive function uses recv(2) with the MSG_WAITALL flag,
which in theory means we should never get a short read. However, when
handing off a socket to a worker child, we also pass a variable-length
string identifying the type of socket we're passing, and reading this
string relies on a short read. This used to work because the arrival of
the descriptor would interrupt the recv(2) call, but this bug was fixed
when the AF_UNIX code was rewritten a while ago and hastd has been
broken ever since.
Fixing the length of the protocol name to four characters including the
terminating null solves the short-read bug by never requiring a short
read (nothing else in hastd requires one).
Note that this issue appears to have been reported independently first
by Alessandro Sagratini in PR 292322 and then by Martin Vidovic in
[11 lines not shown]
tests: Fix graid3 insert tests
The script was passing the wrong device name to `graid3 insert` and
didn't notice that the command was failing.
MFC after: 1 week
Event: EuroBSDcon 2026 DevSummit
Reviewed by: delphij
Differential Revision: https://reviews.freebsd.org/D59564
(cherry picked from commit 4cc85d1f00fa1938923fe8d6fc2934593d4303b4)
graid3: Restore lock acquisition
The lock acquisition in g_raid3_ctl_insert() was improperly dropped a
while ago, making it impossible to add or replace a device in an
existing graid3. This went unnoticed because the tests are broken.
MFC after: 1 week
Fixes: fcf69f3dbce6 ("Consistently use gctl_get_provider instead of home-grown variants.")
Event: EuroBSDcon 2026 DevSummit
Reviewed by: delphij
Differential Revision: https://reviews.freebsd.org/D59563
(cherry picked from commit 9094f86b57a7e4b356cae83f35c8d41c842b42a2)
net/linphone: Distribute distfiles via distcache.FreeBSD.org
Linphone GitLab instance seems a bit unstable at times, so let's keep a
copy of the 6.1.2 archive on LOCAL.
Approved by: portmgr (blanket)
mail/maildrop: Fix INOTIFY option
- FreeBSD 14.5 and up include inotify implementation in libc, so update checks to not depend on the ports implementation ion this case
- When using the ports provided libinotify link using the dynamic library
- Also add one file that needs patching for a successful build
While here, pet portclippy/portfmt.
Reported by: Ewout1 (Excite/BlueTie) <ewout1 at bluetiehome.com> (via mailing list)
MFH: 2026Q3
(cherry picked from commit 307b943e636e53d0c11f408014d01754ae42adb9)
mail/courier-imap: Update version check for INOTIFY option
FreeBSD 14.5 includes the inotify implementation in libc. Update
the version check to avoid linkingg to the ports provided library
in this case.
MFH: 2026Q3
(cherry picked from commit a9309a59e3b7c12e964d99fd94195598845ad9cf)
mail/maildrop: Fix INOTIFY option
- FreeBSD 14.5 and up include inotify implementation in libc, so update checks to not depend on the ports implementation ion this case
- When using the ports provided libinotify link using the dynamic library
- Also add one file that needs patching for a successful build
While here, pet portclippy/portfmt.
Reported by: Ewout1 (Excite/BlueTie) <ewout1 at bluetiehome.com> (via mailing list)
MFH: 2026Q3
mail/courier-imap: Update version check for INOTIFY option
FreeBSD 14.5 includes the inotify implementation in libc. Update
the version check to avoid linkingg to the ports provided library
in this case.
MFH: 2026Q3
