Your message dated Wed, 01 Apr 2020 16:06:34 +0200
with message-id <[email protected]>
and subject line Re: Bug#955444: python-etesync: use the scrypt dependency
instead of pyscrypt, or update to 0.11.1 which requires neither
has caused the Debian Bug report #955444,
regarding python-etesync: use the scrypt dependency instead of pyscrypt, or
update to 0.11.1 which requires neither
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
955444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-etesync
Version: 0.9.2-1
Hi,
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.
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.
Glad to see it in Debian, and thanks a lot for your great work!
--
Tom
--- End Message ---
--- Begin Message ---
Version: 0.11.1-1
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.
>
> 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.
This is fixed since python-etesync 0.11.1-1.
Thanks,
- 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
--- End Message ---
