Closed kev009 closed 2 years ago
@jaqx0r any thoughts on what to do here? ports is set on removal of the older BDB which means the nsscache port will be deleted transitively on 30 September.
A PR to remove the dependency is OK with me. Or if you need to go faster, can you, in ports, patch out the bsddb3 handler in the config module to print an error instead, and remove the dep from packaging?
I'd thought perhaps we need a migration tool too, but I actually recommend users use libnss-cache instead anyway; in the absence of anyone complaining then I think we can remove it and prefer to ask forgiveness if we need to.
On Thu, 25 Aug 2022 at 03:50, Kevin Bowling @.***> wrote:
@jaqx0r https://github.com/jaqx0r any thoughts on what to do here? ports is set on removal of the older BDB which means the nsscache port will be deleted transitively on 30 September.
— Reply to this email directly, view it on GitHub https://github.com/google/nsscache/issues/135#issuecomment-1226048551, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXFX644J6KEBVQ4UNF65BTV2ZOHNANCNFSM5POAWCEA . You are receiving this because you were mentioned.Message ID: @.***>
Removal here https://github.com/google/nsscache/pull/155
According to https://www.jcea.es/programacion/pybsddb.htm bsddb3 is deprecated and replaced by the PyPI berkeleydb package. It seems a somewhat simple name change, but there is also this:
The main change you need to be aware is that in berkeleydb keys and values are now bytes, while in bsddb3 they were strings
. One other difficulty will be Debian packaging, Debian has not yet packaged python3-berkeleydb.X-ref: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262203