security/libssh: Fix build on FreeBSD 15+ with OpenSSL from base system
openssl/ml_kem.h is missing from the OpenSSL 3.5 in the base system.
Add a workaround to disable MLKEM support on such systems temporarily.
net-im/nheko: update to 0.12.1, latest upstream
Release-notes are at
https://github.com/Nheko-Reborn/nheko/releases/tag/v0.12.1
There's a couple of encoding-bugs (labeled "security") in this
release, as well as a bunch of general improvements. It's still
a release from August 2025, so the patch (in FreeBSD ports, picked
from a merged-fix upstream) for Qt 6.10 compatibility remains.
Reported-By: makc@
devel/sd-mux-ctrl: Mark DEPRECATED
- Upstream no longer maintained
- The Tizen infrastructure this port depends on has been discontinued
- Set EXPIRATION_DATE 2026-05-07
If someone needs this port feel free to undeprecate and takeover
maintainership.
devel/py-rednose: Mark DEPRECATED
- Only works with older nosetests which is in bandaid mode sinece last
decade and does not support the modern nose2
- Upstream unmaintained since 2018
- Set EXPIRATION_DATE 2026-05-07
libpam: Move to a new "pam" package
OpenPAM is a discrete, largely self-contained system component.
Users may not need PAM for many use-cases (e.g. jails, containers),
so move it to its own package.
Use LIB_PACKAGE to create a separate pam-lib package for libpam,
so that applications that support PAM don't need to bring in all
the PAM modules if PAM isn't actually in use.
Add pam to the minimal sets, since this is a core system component that
people expect to be installed. This means all supported installation
methods will install the PAM modules by default, so don't add explicit
dependencies on the PAM modules from things that use PAM (e.g. runtime),
allowing custom/embedded systems to omit these easily.
This change adds a new package to the system so, until we have a proper
policy on how to handle this in release/stable branches, it should not
be MFC'd.
[9 lines not shown]
zstd: Move to a new zstd package
Zstd is a discrete, self-contained system component. To match how we
package zlib, bzip2 and xz, move it to its own package, with a separate
lib package.
Add the new package to the minimal set, since this is a core component
that users expect to be installed.
This change adds a new package to the system so, until we have a proper
policy on how to handle this in release/stable branches, it should not
be MFC'd.
[stable/15: MFC under the re@ pkgbase policy for 15.1]
MFC after: never
Reviewed by: bapt
Sponsored by: https://www.patreon.com/bsdivy
Differential Revision: https://reviews.freebsd.org/D53603
[2 lines not shown]
