Your message dated Mon, 29 Jun 2020 09:34:13 +0000
with message-id <e1jpqb3-000ade...@fasolo.debian.org>
and subject line Bug#963487: fixed in mitmproxy 5.1.1-2
has caused the Debian Bug report #963487,
regarding mitmproxy: New updated mitmproxy does not work as per #963067
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 ow...@bugs.debian.org
immediately.)
--
963487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 5.1.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
As per comments added to #963067 , new mitmproxy seemingly cannot be used via
debian dependencies.
Relates to bugs #963181 #963114 that probably should be attended to first.
Copy details below:-
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,
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 later without
needless version-bumps.
-- System Information:
Debian Release: 10.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500,
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mitmproxy depends on:
ii dpkg 1.19.7
ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-1
ii python3 3.7.3-1
ii python3-blinker 1.4+dfsg1-0.2
ii python3-brotli 1.0.7-2
ii python3-certifi 2020.4.5.1-1
ii python3-click 7.0-1
ii python3-cryptography 2.8-4
ii python3-flask 1.1.2-1
ii python3-h11 0.8.1-1
ii python3-h2 3.2.0-2
ii python3-hyperframe 5.1.0-1
ii python3-kaitaistruct 0.8-1
ii python3-ldap3 2.7-2
ii python3-openssl 19.1.0-2
ii python3-passlib 1.7.1-1
ii python3-pkg-resources 40.8.0-1
ii python3-protobuf 3.6.1.3-2
ii python3-publicsuffix2 2.20191221-2
ii python3-pyasn1 0.4.2-3
ii python3-pyparsing 2.4.7-1
ii python3-pyperclip 1.6.4-1
ii python3-ruamel.yaml 0.15.34-1+b1
ii python3-sortedcontainers 2.1.0-2
ii python3-tornado 5.1.1-4
ii python3-wsproto 0.15.0-3
mitmproxy recommends no packages.
mitmproxy suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 5.1.1-2
Done: Andrej Shadura <andre...@debian.org>
We believe that the bug you reported is fixed in the latest version of
mitmproxy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrej Shadura <andre...@debian.org> (supplier of updated mitmproxy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 29 Jun 2020 11:21:51 +0200
Source: mitmproxy
Architecture: source
Version: 5.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team
<python-apps-t...@lists.alioth.debian.org>
Changed-By: Andrej Shadura <andre...@debian.org>
Closes: 963487
Changes:
mitmproxy (5.1.1-2) unstable; urgency=medium
.
* Team upload.
* Remove zstd dependency from setup.py as well (Closes: #963487).
Checksums-Sha1:
4089eb5be37a81aa42b194a37dc06c4a3c6d2757 2683 mitmproxy_5.1.1-2.dsc
a8d63b5a6bf04453a42f30d84d737f9c71453b63 28276 mitmproxy_5.1.1-2.debian.tar.xz
Checksums-Sha256:
7ef4941b324eb08328619e28ef18f4fb2989c607742ea85039c96c16452ad927 2683
mitmproxy_5.1.1-2.dsc
7655d312e101a5a8bf308eb16efc4f4e543a219615d54b6c90ab31f314277297 28276
mitmproxy_5.1.1-2.debian.tar.xz
Files:
46a47ec0efc0ad4f392ffbe510e98c5c 2683 net optional mitmproxy_5.1.1-2.dsc
746f1e06ad49735fb941a921f7bf6c52 28276 net optional
mitmproxy_5.1.1-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl75sugACgkQXkCM2RzY
OdL99ggAn8waHplen4kER0LRy1IIyVV1kOS0PMWL2lqglWOHBaqL5dePko7x3BnQ
5yDoyXCp9YKRoDy6qrKROExdZO3jLLH38k2vdDHQxk967pRyUpWN2MXqhQe+4J77
tLqj+4P0/oK+YyAB7Aephg0da17lS1nBoOX5aRNlxOq0odaXWZAqhxKs3Rjlt06O
hFHE1fkuUm/xX/X4InGl3WBSobuE35gEGW8EykfEH/YB1xpj+jswWDqEywfF00S3
pADmPqy1gwBuRI15g7Y52Qok8PsCtxhZIlX3k9QpP+tz96uRcSjhsT7MLX07719v
WhHXNlpGCo5kTktbxjEf5q1+NZUpMA==
=QdR+
-----END PGP SIGNATURE-----
--- End Message ---
