1 of 4 on in the package: DOCSShow the 3 options that are off
KERBEROSMYSQLPGSQL
pkg-message
Shown after upgrading
Please visit https://kb.isc.org/docs/things-to-be-aware-of-when-upgrading-to-kea-300 for upgrade instructions.
Packages by version and architecture
latest
FreeBSD version
amd64
aarch64
i386
FreeBSD 16
3.2.1_1
3.2.1_1
–
FreeBSD 15
3.2.1_1
3.2.1_1
–
FreeBSD 14
3.2.1_1
3.2.1_1
3.2.1_1
quarterly (2026Q4)
FreeBSD version
amd64
aarch64
i386
FreeBSD 15
3.2.1
3.2.1
–
FreeBSD 14
3.2.1
3.2.1
3.2.1
version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by pkg audit for the packaged version 3.2.1_1.
Fixed (5)
Show 5 fixed
VuXML entries whose affected range the packaged version has left.
maintainer-feedback? net/kea [2.6.3_1]: After upgrade: Unable to open database: invalid path specified - only /var/db as folder allowed
New
2025-06-25
Commits (112)
Xin LI (delphij) · 3.2.1_1
devel/log4cplus: update to 2.2.1
The shared library version changed from 9 to 11, so bump
PORTREVISION of net/kea and net/kea-devel.
Upstream's new pkg-config install code, once rewritten by
USES=pathfix, installed a second log4cplus.pc under a doubled
prefix; patch CMakeLists.txt to correct the path.
net/kea: prepare for Boost-1.89, do not link with stub Boost::system
Backport upstream MR2771 (https://gitlab.isc.org/isc-projects/kea/-/merge_requests/2771)
Approved by: portmgr blanket
net/kea: Fix shebangfix QA error
QA flags a shebang in kea-shell. Unfortunately USES=shebangfix
fails to resolve the issue because the shebang it sees is unexpected.
net/kea: Fix two QA issues
Fix extraneous /var/lib creation. It is not used.
Fix python3 duplicate BUILD_DEPENDS. QA flags this when USES=python
should be used.
python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.
Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.
PR: 274671
Event: Kitchener-Waterloo Hackathon 202506
net/kea-devel: Welcome kea-devel, tracking the development branch
The kea 2.7.X branch tracks kea development. We are importing 2.7.6
here. The development branch includes many fixes not in the 2.6.X
(stable) branch such as LLVM 19 and boost 1.87 support.
Note that just like bind9, also developed by ISC (isc.org), even version
numbers, i.e. 2.6, are stable branch while odd numbered version numbers,
i.e. 2.7, are development branch.
net/kea: mark as BROKEN with Boost>=1.87 (+)
Since 1.87 release some long-time-ago deprecated Boost.asio facilities was dropped off
Sponsored by: Future Crew, LLC
net/kea: update patch for building with libc++ 19
In https://gitlab.isc.org/isc-projects/kea/-/merge_requests/2410,
Francis Dupont noted there were some errors in the unit tests.
These were due to mistakes on my side, so I now made sure all the unit
tests pass (they silently require GoogleTest!), and updated the upstream
merge request. I hope this goes in soon, but it all seems to take a long
time.
PR: 281124
Approved by: apevnev@me.com (maintainer)
MFH: 2024Q3
net/kea: fix build with libc++ 19
As noted in the libc++ 19 release notes [1], std::char_traits<> is now
only provided for char, char8_t, char16_t, char32_t and wchar_t, and any
instantiation for other types will fail.
This causes net/kea to fail to compile with clang 19 and libc++ 19,
resulting in errors similar to:
In file included from edns.cc:9:
In file included from ../../../src/lib/exceptions/exceptions.h:11:
/usr/include/c++/v1/string:820:42: error: implicit instantiation of undefined template 'std::char_traits<unsigned char>'
820 | static_assert(is_same<_CharT, typename traits_type::char_type>::value,
| ^
../../../src/lib/dns/name.h:727:16: note: in instantiation of template class 'std::basic_string<unsigned char>' requested here
727 | NameString ndata_;
| ^
/usr/include/c++/v1/__fwd/string.h:23:29: note: template is declared here
23 | struct _LIBCPP_TEMPLATE_VIS char_traits;
| ^
`NameString` is defined as `std::basic_string<unsigned char>`, which is
no longer possible. So redefine it as a `std::vector<unsigned char>`
instead.
This requires a few adjustments in other places: adjusting the arguments
for the `assign()` method, which for `std::vector` takes a begin and end
iterator, instead of a begin iterator and a size, and replacing the
`append()` method with an equivalent `insert()`.
These changes have also been sent upstream [2].
[1] https://libcxx.llvm.org/ReleaseNotes/19.html#deprecations-and-removals
[2] https://gitlab.isc.org/isc-projects/kea/-/merge_requests/2410
PR: 280696
Approved by: apevnev@me.com (maintainer)
MFH: 2024Q3
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++ -DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable -Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi -Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings -Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x -MT _quickfix_la-QuickfixPython.lo -MD -MP -MF .deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o .libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)