Your message dated Wed, 30 Dec 2020 09:03:48 +0000
with message-id <e1kuxow-00095g...@fasolo.debian.org>
and subject line Bug#977926: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977926,
regarding Missing required dependencies
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.)


-- 
977926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 5.3.0-1
Severity: grave

Installing mitmproxy in a clean sid chroot, and running it (with no arguments)
results into a large backtrace that ends with...
  pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was 
not found and is required by mitmproxy

After installing the package python3-hyperframe, the error becomes:
  pkg_resources.DistributionNotFound: The 'h2>=4.0' distribution was not found 
and is required by mitmproxy
...in turn fixed by installing the package python3-h2.

It looks like at least those two dependencies are missing, preventing
the package from working out of the box in any configuration. Both of
these were in the Depends for the 4.0.4-5 version (buster's).

I did not check whether other features require more dependencies, as I'm
not too familiar with all of mitmproxy's operation modes.

Regards,
Faidon

--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 5.3.0-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 977...@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: Wed, 30 Dec 2020 09:51:56 +0100
Source: mitmproxy
Architecture: source
Version: 5.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Andrej Shadura <andre...@debian.org>
Closes: 977926 977927
Changes:
 mitmproxy (5.3.0-2) unstable; urgency=medium
 .
   * Pre-wrap dependencies of the binary package.
   * Fix the dependencies of the binary package (Closes: #977926, #977927)
   * Drop an explicit dependency on h11, wsproto depends on it already.
Checksums-Sha1:
 059a438544dcf617dacf26e7392cad58db4c3d92 2708 mitmproxy_5.3.0-2.dsc
 e809d69349b0137fda550ddf4e9164a37e4c8169 11856 mitmproxy_5.3.0-2.debian.tar.xz
Checksums-Sha256:
 c2fd57e9aed352ed4234e4e19711673141667ed2333a4537881c1973c00ccb85 2708 
mitmproxy_5.3.0-2.dsc
 abc1c71780480c92415e65d247896170532152b6008e90edf2c6bf6cc3831448 11856 
mitmproxy_5.3.0-2.debian.tar.xz
Files:
 aa62148b29e71506db547c46e2c3c72f 2708 net optional mitmproxy_5.3.0-2.dsc
 612cdaaa85a4bef2d3fe3a4657493911 11856 net optional 
mitmproxy_5.3.0-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/sP98ACgkQXkCM2RzY
OdJuRgf/XNw0EtFGvBWIdpZneWTRcY3LYZfsya2dC0vhZvVdC/txZtaIE48Kw+hA
m+7xqZDcn7QQZYbeGC23ShfooYGO1u/tATDMBagp0BWz9Iz+YKvDlDtgbsgNZEW7
mDeh0jVegfKbE1mcG2gtUfQ66X5cf6+pRomD8bkd1/UoZbNzuadRLzu4QVY7n0eS
4LtdfRuClCP36rKPTs3XhtFZcESTIC6BabBjBGq7rT3cfW6CC2vP2Y1TeAxdLg0C
fibekFkD8ejrRN98TgrJH6sD1TQQht5xjHuk/OYndCjVhslech/uqLq5K0b9Z8Vc
tQjoLEVIxFXUeSm0Vu+lerHMaDEaBA==
=42uc
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to