net-mgmt/librenms: Remove sudo dependency
At one time it was required for running certain scripts.
Add an UPDATING entry.
While here, notice and correct the date for the previous entry
from d90f5893
Reported by: SgtMalicious
Tested by: me
˚¨# "Pull Request" and "Differential Revision" require the *full* GitHub or
java/openjdk27: version 27.0.1.0.2, incl CA fixes
Upgrade port to latest upstream, including fixes for eMudhra CA
certificate issues.
Sponsored by: The FreeBSD Foundation
(cherry picked from commit c3e71861bf8632b8037be3fe8c48d5127ccc077f)
java/openjdk27: version 27.0.1.0.2, incl CA fixes
Upgrade port to latest upstream, including fixes for eMudhra CA
certificate issues.
Sponsored by: The FreeBSD Foundation
net/stund: Update to 1.0.1 and assign maintainership
Port been forked, updated and adoped by a new maintainer.
Co-authored-by: Michael Osipov <michaelo at FreeBSD.org>
PR: 299433
cad/openscad-devel: Update and enable experimental features
Update to 2026.10.23 and enable experimental features
PR: 299642
Reported by: Arthur Chance
devel/py-evdev: Use the evdev headers from base
evdev 1.9 expects the UI_FF_* constants from uinput.h, but the port
generated its ecodes module only from devel/evdev-proto's
linux/input.h and linux/input-event-codes.h, so "import evdev" fails
with KeyError: 'UI_FF'.
files/patch-v4l_compat, added with the port in 2015 when base had no
dev/evdev headers, removes upstream's #ifdef __FreeBSD__ branches for
<dev/evdev/...> and makes the port build against evdev-proto instead.
Base now installs dev/evdev/input.h, input-event-codes.h and uinput.h,
which evdev's setup.py uses on FreeBSD by default, and build_ext
generates the ecodes module itself. Drop the patch, the evdev-proto
dependency, USES=localbase and the build_ecodes, --evdev-headers and
--include-dirs arguments, and bump PORTREVISION.
The 14.5 and 15.1 base headers define FF_MAX_EFFECTS; older ones
(13.5, 14.2, 14.3, 14.4 and 15.0) lack it, and evdev falls back for it.
[3 lines not shown]
*/wordpress*: deprecate localized variants
Localized WordPress tarballs are regenerated in place by upstream
whenever translations are updated, so the distfile checksums keep
breaking without a version change. The language packs have the same
problem, and other distributions only ship the English core and let
WordPress download language packs on its own.
Mark the localized ports deprecated, expiring on 2026-12-31. Users
should switch to www/wordpress and choose the site language in
WordPress.
{french,german,russian}/wordpress: chase upstream distfile re-roll
Upstream re-rolled the 7.1.3 de_DE, fr_FR and ru_RU tarballs again
with refreshed translations under wp-content/languages. The
WordPress core files are unchanged.
Update distinfo and bump PORTREVISION as package contents changed.