db5 has been marked DEPRECATED and in terms databases/py-bsddb3 has also been marked DEPRECATED. Currently this port depends on py-bsddb3. In this state there are two options which can be checked. Whether if this port builds/runs with databases/py-berkeleydb or in other terms chase upstream to support for databases/py-berkeleydb which is the next generation implementation of py-bsddb3. For reference please see here: https://www.jcea.es/programacion/pybsddb.htm. If none of the options are viable please mark the port DEPRECATED with the following: DEPRECATED= Requires upstream py-bsddb3 which requires upstream EOLd db5 EXPIRATION_DATE= 2022-06-30
https://github.com/google/nsscache/issues/135
(In reply to Kevin Bowling from comment #1) Thanks.
Created attachment 233720 [details] Update DEPS to py-berkeleydb Updated dependency and changed some sources to use berkeleydb instead of bsddb3. At least the commandline script generates some viable output. root@MAIN-default:~ # nsscache help nsscache synchronises a local NSS cache against a remote data source. Usage: nsscache [global options] command [command options] commands: update update the cache. verify verify the cache and configuration. help show per-command help. repair repair the cache. status show current cache status. Options: --version show program's version number and exit -h, --help show this help message and exit -v, --verbose enable verbose output -d, --debug enable debugging output -c FILE, --config-file=FILE read configuration from FILE And here the buildlogs: https://pdr.bofh.network/data/latest-per-pkg/nsscache/0.44_1/
(In reply to Muhammad Moinur Rahman from comment #3) Hi Moin, Unfortunately this isn't sufficient for BDB, although I may be wrong and some more test output showing a non-BDB backend working may sway me. I tried similarly before filing the upstream bug and gave up when I realized the API for py-berkeleydb had changed a bit and I don't have any near term priority to work on this. I think there are two viable paths forward for your consideration: 1) Optionalize BDB support within nsscache and we fully disable it on FreeBSD. This is likely the easiest and IMO sufficient (one would have to pair nsscache with sysutils/nss_ndb to use the result on FreeBSD and you might as well use net/libnss-cache) 2) Update nsscache to use the new py-berkeleydb APIs. This will require a bit more thinking but there is a test suite and I did run it to realize I didn't have time to digest everything before opening the upstream bug. I would guess upstream will act when Debian follows a similar upgrade fate so a third option would be some variant of waiting.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=827afb1759885006e4b8cf0fff60f37d8a366ff8 commit 827afb1759885006e4b8cf0fff60f37d8a366ff8 Author: Kevin Bowling <kbowling@FreeBSD.org> AuthorDate: 2022-08-26 06:23:50 +0000 Commit: Kevin Bowling <kbowling@FreeBSD.org> CommitDate: 2022-08-26 06:27:59 +0000 net/nsscache: Update to 0.47 Drops BDB support, so remove expiry PR: 262203 net/nsscache/Makefile | 6 +----- net/nsscache/distinfo | 6 +++--- net/nsscache/files/patch-nsscache.conf | 13 ++----------- 3 files changed, 6 insertions(+), 19 deletions(-)