Quoting Tom Hacohen (2020-03-31 22:23:42) > I'm the maintainer of the upstream package. While the pip dependency > was listed as pyscrypt, we've always supported both pyscrypt and > scrypt, with the latter being the recommended choice because it's much > more efficient (and still maintained). The former was the default > because of compatibility.
Reason I went for pyscrypt was that etesync-dav is licensed GPL-3 which is incompatible with the OpenSSL licensing. > Additionally, if you update to version 0.11.1 (latest), you can even > remove both deps, because it now also supports the scrypt > implementation that's shipped in Python 3.6 and later. Oh, that's great! I will look into that. > Glad to see it in Debian, and thanks a lot for your great work! Thanks for your interest in downstream use of your project! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
