Your message dated Mon, 01 Apr 2019 18:34:00 +0000
with message-id <[email protected]>
and subject line Re: Bug#926153: unblock: mitmproxy/4.0.4-5
has caused the Debian Bug report #926153,
regarding unblock: mitmproxy/4.0.4-5
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.)
--
926153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926153
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
Dear Release Team,
#923354 describes how mitmproxy 4.0.4-4 doesn't start at all due to a
missing dependency, and as such it should probably have used
"Severity:grave".
4.0.4-5 fixes that, and has been in unstable for a little while
now. I've attached the relevant debdiff between those two versions.
Could you please consider unblocking 4.0.4-5 ?
Cheers,
--
Seb
unblock mitmproxy/4.0.4-5
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-3-amd64 (SMP w/36 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index 2227fb62..e2d46fbc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+mitmproxy (4.0.4-5) unstable; urgency=medium
+
+ * Add dependency on python3-pkg-resources (Closes: #923354)
+
+ -- Sebastien Delafond <[email protected]> Mon, 04 Mar 2019 10:49:20 +0100
+
mitmproxy (4.0.4-4) unstable; urgency=medium
* Remove references to manpage in debian/rules
diff --git a/debian/control b/debian/control
index 677d471d..f963a716 100644
--- a/debian/control
+++ b/debian/control
@@ -36,7 +36,7 @@ Homepage: https://mitmproxy.org
Package: mitmproxy
Architecture: all
Pre-Depends: dpkg (>= 1.17.14)
-Depends: ${misc:Depends}, ${python3:Depends}, fonts-font-awesome (>=
4.2.0~dfsg), python3-h11
+Depends: ${misc:Depends}, ${python3:Depends}, fonts-font-awesome (>=
4.2.0~dfsg), python3-h11, python3-pkg-resources
Conflicts: python-netlib
Description: SSL-capable man-in-the-middle HTTP proxy
mitmproxy is an SSL-capable man-in-the-middle HTTP proxy. It provides
--- End Message ---
--- Begin Message ---
Sebastien Delafond:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: unblock
>
> Dear Release Team,
>
> #923354 describes how mitmproxy 4.0.4-4 doesn't start at all due to a
> missing dependency, and as such it should probably have used
> "Severity:grave".
>
> 4.0.4-5 fixes that, and has been in unstable for a little while
> now. I've attached the relevant debdiff between those two versions.
>
> Could you please consider unblocking 4.0.4-5 ?
>
> Cheers,
>
Unblocked, thanks.
~Niels
--- End Message ---
