Control: tags 827068 + patch
Control: tags 827068 + pending

Dear maintainer,

I've prepared an NMU for m2crypto (versioned as 0.24.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer. I am also going to switch m2ext to
libssl1.0-dev.

Regards.
Sebastian
diff -Nru m2crypto-0.24.0/debian/changelog m2crypto-0.24.0/debian/changelog
--- m2crypto-0.24.0/debian/changelog	2016-03-29 21:16:43.000000000 +0200
+++ m2crypto-0.24.0/debian/changelog	2017-02-05 14:37:04.000000000 +0100
@@ -1,3 +1,10 @@
+m2crypto (0.24.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build depend on openssl 1.0 for Stretch (Closes: #827068)
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc>  Sun, 05 Feb 2017 14:37:04 +0100
+
 m2crypto (0.24.0-1) unstable; urgency=medium
 
   * New upstream release (Closes: #818986):
diff -Nru m2crypto-0.24.0/debian/control m2crypto-0.24.0/debian/control
--- m2crypto-0.24.0/debian/control	2016-03-29 21:10:30.000000000 +0200
+++ m2crypto-0.24.0/debian/control	2017-02-05 14:35:40.000000000 +0100
@@ -5,7 +5,7 @@
 Build-Depends:
  debhelper (>= 9),
  dh-python,
- libssl-dev (>= 1.0.1e),
+ libssl1.0-dev | libssl-dev (<< 1.1),
  python-all-dev,
  python-setuptools,
  swig (>= 1.3.40),

Reply via email to