[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#856433: marked as done (unblock: influxdb-python/3.0.0-2)

Your message dated Sun, 12 Mar 2017 11:32:18 +0100
with message-id <b5e37533-2d2b-4899-628a-e267ad7f1df4@debian.org>
and subject line Re: Bug#856433: unblock: influxdb-python/3.0.0-2
has caused the Debian Bug report #856433,
regarding unblock: influxdb-python/3.0.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 owner@bugs.debian.org
immediately.)


-- 
856433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856433
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock influxdb-python 3.0.0-2. If fixes 841559 which caused FTBFS.

It failed to build because of an introduced FutureWarning which we don't
have to solve right now because the method is not yet deprecated. The
warnings were set to cause build failures by the devs to spot things
like this, but its not necessary for us. The fix is simply to ignore the
warning.

I have attached the debdiff to this email.

unblock influxdb-python/3.0.0-2

Cheers,

-- 
Alexandre Viau
aviau@debian.org

diff -Nru influxdb-python-3.0.0/debian/changelog influxdb-python-3.0.0/debian/changelog
--- influxdb-python-3.0.0/debian/changelog	2016-06-26 15:56:28.000000000 -0400
+++ influxdb-python-3.0.0/debian/changelog	2017-02-28 15:44:10.000000000 -0500
@@ -1,3 +1,9 @@
+influxdb-python (3.0.0-2) unstable; urgency=medium
+
+  * Disable FurureWarnings (Closes: #841559)
+
+ -- Alexandre Viau <aviau@debian.org>  Tue, 28 Feb 2017 15:44:10 -0500
+
 influxdb-python (3.0.0-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru influxdb-python-3.0.0/debian/patches/ignore-future-warning.patch influxdb-python-3.0.0/debian/patches/ignore-future-warning.patch
--- influxdb-python-3.0.0/debian/patches/ignore-future-warning.patch	1969-12-31 19:00:00.000000000 -0500
+++ influxdb-python-3.0.0/debian/patches/ignore-future-warning.patch	2017-02-28 15:44:10.000000000 -0500
@@ -0,0 +1,22 @@
+--- a/influxdb/tests/dataframe_client_test.py
++++ b/influxdb/tests/dataframe_client_test.py
+@@ -28,7 +28,7 @@
+ 
+     def setUp(self):
+         # By default, raise exceptions on warnings
+-        warnings.simplefilter('error', FutureWarning)
++        warnings.simplefilter('ignore', FutureWarning)
+ 
+     def test_write_points_from_dataframe(self):
+         now = pd.Timestamp('1970-01-01 00:00+00:00')
+--- a/influxdb/tests/influxdb08/dataframe_client_test.py
++++ b/influxdb/tests/influxdb08/dataframe_client_test.py
+@@ -24,7 +24,7 @@
+ 
+     def setUp(self):
+         # By default, raise exceptions on warnings
+-        warnings.simplefilter('error', FutureWarning)
++        warnings.simplefilter('ignore', FutureWarning)
+ 
+     def test_write_points_from_dataframe(self):
+         now = pd.Timestamp('1970-01-01 00:00+00:00')
diff -Nru influxdb-python-3.0.0/debian/patches/series influxdb-python-3.0.0/debian/patches/series
--- influxdb-python-3.0.0/debian/patches/series	1969-12-31 19:00:00.000000000 -0500
+++ influxdb-python-3.0.0/debian/patches/series	2017-02-28 15:44:10.000000000 -0500
@@ -0,0 +1 @@
+ignore-future-warning.patch

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
On 01/03/17 00:59, Alexandre Viau wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock influxdb-python 3.0.0-2. If fixes 841559 which caused FTBFS.
> 
> It failed to build because of an introduced FutureWarning which we don't
> have to solve right now because the method is not yet deprecated. The
> warnings were set to cause build failures by the devs to spot things
> like this, but its not necessary for us. The fix is simply to ignore the
> warning.
> 
> I have attached the debdiff to this email.
> 
> unblock influxdb-python/3.0.0-2

Sorry but your package got removed from testing on December 21st (so almost 3
months ago) and you missed the deadlines for testing re-entry (February 5th).
Thus this will have to go in stretch-backports, unless you can give a convincing
argument to grant this package a freeze exception.

Cheers,
Emilio

--- End Message ---
Reply to: