Control: tags 792631 + patch
Control: tags 792631 + pending
Dear maintainer,
I've prepared an NMU for python-librtmp (versioned as 0.2.2-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
SR
diff -Nru python-librtmp-0.2.2/debian/changelog python-librtmp-0.2.2/debian/changelog
--- python-librtmp-0.2.2/debian/changelog 2015-05-12 19:38:08.000000000 +0200
+++ python-librtmp-0.2.2/debian/changelog 2015-08-21 12:55:23.000000000 +0200
@@ -1,3 +1,12 @@
+python-librtmp (0.2.2-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Build-Depend on python{,3}-cffi-backend-dbg instead of
+ python{,3}-cffi-dbg, it was renamed without a transition package
+ (Closes: #792631).
+
+ -- Stefano Rivera <stefa...@debian.org> Fri, 21 Aug 2015 12:54:19 +0200
+
python-librtmp (0.2.2-1) unstable; urgency=low
* New upstream version
diff -Nru python-librtmp-0.2.2/debian/control python-librtmp-0.2.2/debian/control
--- python-librtmp-0.2.2/debian/control 2015-05-12 19:38:08.000000000 +0200
+++ python-librtmp-0.2.2/debian/control 2015-08-21 12:54:16.000000000 +0200
@@ -12,8 +12,8 @@
python3-all-dbg,
python-cffi,
python3-cffi,
- python-cffi-dbg,
- python3-cffi-dbg,
+ python-cffi-backend-dbg,
+ python3-cffi-backend-dbg,
python-setuptools,
python3-setuptools,
python-singledispatch,
