Your message dated Wed, 22 Feb 2017 20:41:00 +0000
with message-id <[email protected]>
and subject line Re: Bug#855875: unblock: tcpdump/4.9.0-2
has caused the Debian Bug report #855875,
regarding unblock: tcpdump/4.9.0-2
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.)


-- 
855875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855875
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock

tcpdump 4.9 is not compatible with OpenSSL 1.1 so a few months ago I
disabled crypto support altogether. However, it now appears that OpenSSL
1.0 will be officially supported in stretch, so I would like to bring
back tcpdump to feature parity with jessie and previous releases by
enabling crypto support based on OpenSSL 1.0.

Full debdiff attached. Thanks for considering.

unblock tcpdump/4.9.0-2

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (850, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diffstat for tcpdump-4.9.0 tcpdump-4.9.0

 changelog |    9 +++++++++
 control   |    3 ++-
 rules     |    2 +-
 3 files changed, 12 insertions(+), 2 deletions(-)

diff -Nru tcpdump-4.9.0/debian/changelog tcpdump-4.9.0/debian/changelog
--- tcpdump-4.9.0/debian/changelog      2017-01-26 20:04:11.000000000 +0100
+++ tcpdump-4.9.0/debian/changelog      2017-02-11 16:40:05.000000000 +0100
@@ -1,3 +1,12 @@
+tcpdump (4.9.0-2) unstable; urgency=medium
+
+  * Re-enable crypto support, targeting OpenSSL 1.0 as upstream still
+    doesn't support OpenSSL 1.1.
+  * Drop --enable-ipv6 from configure line, it has been the default for
+    years now.
+
+ -- Romain Francoise <[email protected]>  Sat, 11 Feb 2017 16:40:05 +0100
+
 tcpdump (4.9.0-1) unstable; urgency=high
 
   * New upstream security release, fixing the following:
diff -Nru tcpdump-4.9.0/debian/control tcpdump-4.9.0/debian/control
--- tcpdump-4.9.0/debian/control        2017-01-26 19:59:23.000000000 +0100
+++ tcpdump-4.9.0/debian/control        2017-02-11 16:34:29.000000000 +0100
@@ -5,7 +5,8 @@
 Build-Depends: debhelper (>= 8.9.4~),
                dh-autoreconf,
                dpkg-dev (>= 1.16.1~),
-               libpcap0.8-dev (>= 1.8)
+               libpcap0.8-dev (>= 1.8),
+               libssl1.0-dev
 Standards-Version: 3.9.8
 Homepage: http://www.tcpdump.org/
 Vcs-Browser: https://anonscm.debian.org/cgit/users/rfrancoise/tcpdump.git/
diff -Nru tcpdump-4.9.0/debian/rules tcpdump-4.9.0/debian/rules
--- tcpdump-4.9.0/debian/rules  2017-01-26 19:52:15.000000000 +0100
+++ tcpdump-4.9.0/debian/rules  2017-02-11 16:39:13.000000000 +0100
@@ -7,4 +7,4 @@
        dh $@ --parallel --with autoreconf
 
 override_dh_auto_configure:
-       dh_auto_configure -- --enable-ipv6 --with-crypto=no
+       dh_auto_configure -- --with-crypto=yes

--- End Message ---
--- Begin Message ---
Romain Francoise:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: unblock
> 
> tcpdump 4.9 is not compatible with OpenSSL 1.1 so a few months ago I
> disabled crypto support altogether. However, it now appears that OpenSSL
> 1.0 will be officially supported in stretch, so I would like to bring
> back tcpdump to feature parity with jessie and previous releases by
> enabling crypto support based on OpenSSL 1.0.
> 
> Full debdiff attached. Thanks for considering.
> 
> unblock tcpdump/4.9.0-2
> 
> [...]

Unblocked, thanks.

~Niels

--- End Message ---

Reply via email to