New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bsddb3 is deprecated #135
Comments
@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
<#135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXFX644J6KEBVQ4UNF65BTV2ZOHNANCNFSM5POAWCEA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Removal here #155 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: