Services: Kea: DHCPv4/6: Add type system with validation and encoding for supported DHCP options (#9995)
* Services: Kea: DHCPv4/6: Add type system with validation and encoding for supported DHCP options
This adds a type framework using MAPS extracted from data inside the KEA documentation.
Most flat options have a validator and encoder added. Users are guided via validation messages which types are correct choices for each code selection.
Advanced options (structured, nested, encapsulated) do not have an own validator or encoder yet, they fall back to hex.
Unknown options that are valid in the IANA lists, but maybe not inside KEA yet, also fallback to hex.
The user can always bail out of the type system and always use hex instead for any option.
* CodeSource was missing, preventing match_code and code to be evaluated independently upon instantiation of the field type
* Clean up some failguards since if those conditions would be true I don't want to fail silently
* Turn encoding into a map so the code is easier readable, add missing uint length validation
* Do not hide this error silently
[33 lines not shown]
net/gerbera: Update to 3.2.1 and mark BROKEN on i386
Fails to build on i386,
error: non-constant-expression cannot be narrowed from type 'rep' (aka 'long long') to 'time_t' (aka 'int') in initializer list
Changelog: https://github.com/gerbera/gerbera/releases/tag/v3.2.1
multimedia/livego: update 0.0.15 -> 0.0.20 and take maintainership
Changelog: https://github.com/gwuhaolin/livego/releases/tag/0.0.20
Major changes:
* Fix Memory leak
* Update ignore rules
* Add RTMPS support
* added hls via https support
Port changes:
go-redis package don't fit GH_TUPLE expectations by creating the wrong
directory structure (create a ${WRKDIR}/go-redis directory where
${WRKDIR}/redis is expected) leading to post-extract move errors, so it
must be handled separately.
textproc/ruby-review: update to 5.11.0
This is a leaf package.
5.11.0 (2026-03-15)
Bug fixes
* Fixed errors occurring with ruby-zip v3.x (#1941, #1942).
* LATEXBuilder: Fixed an issue where internal anchor links starting with
#... in @<href> op would break (#1955).
* Fixed a build error when using review-jsbook in combination with TeXLive
2026 or later (#1960, #1961).
Enhancements
* Added support for Ruby 3.4 (#1933, #1939).
* Enabled support for //firstlinenum in PLAINTEXTBuilder and TOPBuilder
(#1931).
[25 lines not shown]
devel/php-xdebug: update to 3.5.1
3.5.1 (2026-03-17)
Fixed bugs:
* Fixed issue #2391: Code Coverage times out on random tests
* Fixed issue #2395: Severe performance degredation on Windows
* Fixed issue #2397: Very slow with Xdebug 3.5.0
lang/ruby40: update to 4.0.2
This release contains security fix for zlib gem version 3.3.2 which fixes
CVE-2026-27820.
Quote from release announce:
This is a routine update that includes a bugfix in YJIT for NoMethodError on
Puma. Please see the GitHub Releases for further details.
Release Schedule
We intend to release the latest stable Ruby version (currently Ruby 4.0)
every two months following the most recent release. Ruby 4.0.3 will be
released in May, 4.0.4 in July, 4.0.5 in September, and 4.0.6 in November.
If a change arises that significantly affects users, a release may occur
earlier than planned, and the subsequent schedule may shift accordingly.
[59 lines not shown]
xml2doc: Various build fixes.
- Fix implicit function decls.
- Let infra take care of stripping. It uses an argument to strip
that is unsupported on some systems.
zfs: fix "slow rm" issue
* stop commiting zil in zfs_netbsd_reclaim and other operations
in vnode reclaim path.
* retire zfs_zget_cleaner/VN_RELE_CLEANER.
instead, just use normal zfs_zget and vrele_async.
note that these two changes depend on each other:
* zfs_zget_cleaner relies on zil_commit in zfs_netbsd_reclaim to
ensure that the znode referenced by TX_WRITE itx is always in-core.
* otoh, zfs_zget_clear makes zil_commit in the vnode reclaim path
possible. that is, zfs_netbsd_reclaim (VOP_RECLAIM) is called with
the vnode in VS_RECLAIMING state, which would make vcache_vget
block.
if the vnode being reclaimed happened to have TX_WRITE itx on the
zil, it deadlocks.
[20 lines not shown]
