Dear Python3 application packagers team,
Please re-open the bug because Mitmproxy update 5.1.1 does not, in
fact, work, so far as I can see it cannot even work on a debian
'unstable' chroot due to internal dependencies as provided.
Despite 'patching out zstandard' done by packager, mitmproxy contains
some internal dependency on zstandard and so won't start. There is
also a python3-cryptography internal dependency that isn't satisfied.
Both of the following internal dependency-errors may appear, for
example:-
pkg_resources.DistributionNotFound: The 'zstandard<0.14,>=0.11'
distribution was not found and is required by mitmproxy
pkg_resources.DistributionNotFound: The 'cryptography<3.0,>=2.9'
distribution was not found and is required by mitmproxy
I'm fairly sure the right thing to do is to complete debian bugs
#963181 #963114, getting zstandard available and cryptography updated,
then rebuild 5.1.1 package with:-
1) debian python3-zstandard dependency added
2) patch-out-zstandard change reverted
3) debian python3-cryptography dependency bumped to need at least 2.9
Hope that helps.
--Simon
p.s. not convinced the dependency bump on other parts are necessarily
correct, e.g. urwid 2.1.0 ... be helpful if package is
backportable with not so many other packages.
