Your message dated Mon, 19 Mar 2018 12:35:19 +0000
with message-id <e1exu0v-000e8r...@fasolo.debian.org>
and subject line Bug#892500: fixed in mitmproxy 2.0.2-4
has caused the Debian Bug report #892500,
regarding mitmproxy: Doesn't start with dependency versions currently available 
in Debian
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.)


-- 
892500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 2.0.2-3
Severity: grave
Justification: renders package unusable

The package has unversioned dependencies like "python3-ruamel.yaml", and
versioned like python3-pyperclip (>= 1.5.22). However,
mitmproxy-2.0.2.egg-info/requires.txt has stricter versioning
requirements, like ruamel.yaml<0.14,>=0.13.2 and pyperclip<1.6,>=1.5.22.

Debian buster currently ships versions newer than what requires.txt
considers "too new", so mitmproxy doesn't start:

pkg_resources.ContextualVersionConflict: (ruamel.yaml 0.15.34 
(/usr/lib/python3/dist-packages), 
Requirement.parse('ruamel.yaml<0.14,>=0.13.2'), {'mitmproxy'})
pkg_resources.DistributionNotFound: The 'ruamel.yaml<0.14,>=0.13.2' 
distribution was not found and is required by mitmproxy

I downgraded python3-ruamel.yaml from 0.15.34-1 to 0.13.4-2+b1 (via 
snapshots.d.o)
and it failed again:
pkg_resources.ContextualVersionConflict: (pyperclip 1.6.0 
(/usr/lib/python3/dist-packages), Requirement.parse('pyperclip<1.6,>=1.5.22'), 
{'mitmproxy'})

After manually downgrading 5 deps I still couldn't get it to run and I gave up.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (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.0.5
ii  fonts-font-awesome        4.7.0~dfsg-3
ii  python3                   3.6.4-1
ii  python3-blinker           1.4+dfsg1-0.1
ii  python3-brotli            1.0.2-3
ii  python3-certifi           2018.1.18-2
ii  python3-configargparse    0.11.0-1
ii  python3-construct         2.8.16-0.2
ii  python3-cryptography      2.1.4-1
ii  python3-cssutils          1.0.2-1
ii  python3-flask             0.12.2-3
ii  python3-h2                3.0.1-3
ii  python3-hpack             3.0.0-2
ii  python3-html2text         2018.1.9-1
ii  python3-hyperframe        5.1.0-1
ii  python3-jsbeautifier      1.6.4-6
ii  python3-kaitaistruct      0.7-1
ii  python3-lxml              4.1.0-1
ii  python3-openssl           17.5.0-1
ii  python3-passlib           1.7.1-1
ii  python3-pil               4.3.0-2
ii  python3-pyasn1            0.4.2-3
ii  python3-pyparsing         2.2.0+dfsg1-2
ii  python3-pyperclip         1.6.0-1
ii  python3-requests          2.18.4-2
ii  python3-ruamel.yaml       0.15.34-1
ii  python3-six               1.11.0-2
ii  python3-sortedcontainers  1.5.7-1
ii  python3-tornado           4.5.3-1
ii  python3-urwid             1.3.1-2+b2
ii  python3-watchdog          0.8.3-2

mitmproxy recommends no packages.

mitmproxy suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 2.0.2-4

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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond <s...@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: SHA512

Format: 1.8
Date: Mon, 19 Mar 2018 11:46:44 +0100
Source: mitmproxy
Binary: mitmproxy
Architecture: source
Version: 2.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond <s...@debian.org>
Changed-By: Sebastien Delafond <s...@debian.org>
Description:
 mitmproxy  - SSL-capable man-in-the-middle HTTP proxy
Closes: 892500
Changes:
 mitmproxy (2.0.2-4) unstable; urgency=medium
 .
   * Rediff patches, and remove all upper-bounds on versioned conflicts
     following upstream recommendation in #846850 (Closes: #892500)
Checksums-Sha1:
 76d98076462b4d6e6b4c47444168cff21043c57a 2303 mitmproxy_2.0.2-4.dsc
 81ff615f38e6b988fb13f60fb008cb805364af44 14488 mitmproxy_2.0.2-4.debian.tar.xz
 487500dc0c605fc1d72f2165883d9affec3fd087 8325 mitmproxy_2.0.2-4_amd64.buildinfo
Checksums-Sha256:
 f799cd35696aa9ec69f8f0a45ec2c7d22ddc7e66d52a336fdc474e51b049c42d 2303 
mitmproxy_2.0.2-4.dsc
 c295763e9c64511692df12397c984841c03420257c9a1833ddcda0e112af7367 14488 
mitmproxy_2.0.2-4.debian.tar.xz
 69f17083b43de562e83fce6ee1d8ebdee8d67052b926399f1e1c76cb08f4df7c 8325 
mitmproxy_2.0.2-4_amd64.buildinfo
Files:
 dcb326ee186aa6c528b55da135b52043 2303 net optional mitmproxy_2.0.2-4.dsc
 f79b8f9be9fa31d6ff6a16f97271bcb8 14488 net optional 
mitmproxy_2.0.2-4.debian.tar.xz
 b08fc3da5c5e893826c672c716af137c 8325 net optional 
mitmproxy_2.0.2-4_amd64.buildinfo

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

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAlqvqM0ACgkQEL6Jg/PV
nWRPbggAhmHn4RmfMAdJtj3QWkbPKa8YN+gQPaxeH3WGAAO9DCeqxRwx73t9UEo4
KBr4LyOKK65Gal+2PKiFiK8bNGxwndTZ4HrM/ID100VDmpPD6uqo5Y7KMsSPhPXf
mIOdQwF2xKeSVBBiQDPMz4dZ5IemX5odytG97gsEJQZ5tDZH8eJiXrIYQMr0AVnk
B+lcSLz4aQorQlSl8+LUl0X/0aEO2H15xIFjvKesQzClk7xHUqeCm3w8VFGOOA1X
znoHFhiQ0vpKvHdDfhxTZS+6Plig13DfKqBirUW5FGirg2WJ8QPu/K1JumlImgqg
sjw/pXDL0YPUxEDOUmy7/p+dJR/z9Q==
=klUZ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to