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

Bug#857603: marked as done (unblock: mpi4py/2.0.0-2.1)



Your message dated Mon, 13 Mar 2017 07:07:00 +0000
with message-id <19c1fb22-9674-d873-f5fc-18c5ab4266df@thykier.net>
and subject line Re: Bug#857603: unblock: mpi4py/2.0.0-2.1
has caused the Debian Bug report #857603,
regarding unblock: mpi4py/2.0.0-2.1
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.)


-- 
857603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857603
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 package mpi4py

mpi4py in testing (2.0.0-2) FTBFS due to errors in some tests (release
critical bug #856349)
.
2.0.0-2.1 fixes the FTBFS by treating test errors as warnings.

debdiff:
diff -Nru mpi4py-2.0.0/debian/changelog mpi4py-2.0.0/debian/changelog
--- mpi4py-2.0.0/debian/changelog	2016-08-02 22:42:00.000000000 +0800
+++ mpi4py-2.0.0/debian/changelog	2017-03-08 16:18:00.000000000 +0800
@@ -1,3 +1,11 @@
+mpi4py (2.0.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * In debian/rules:override_dh_auto_test, treat test errors as warnings.
+    Closes: #856349.
+
+ -- Drew Parsons <dparsons@debian.org>  Wed, 08 Mar 2017 16:18:00 +0800
+
 mpi4py (2.0.0-2) unstable; urgency=medium
 
   * Point to libm.so.6 in the test, not libm.so (Closes: #817884)
diff -Nru mpi4py-2.0.0/debian/rules mpi4py-2.0.0/debian/rules
--- mpi4py-2.0.0/debian/rules	2016-08-02 22:42:00.000000000 +0800
+++ mpi4py-2.0.0/debian/rules	2017-03-08 16:18:00.000000000 +0800
@@ -88,6 +88,7 @@
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 	set -e; for v in $(PY2VERS) $(PY3VERS); do \
      echo "I: testing using python$$v"; \
+	echo "Note: test errors here are treated as warnings"; \
 	 PYTHONPATH=`/bin/ls -d $(CURDIR)/build/lib.*-$$v` \
 	  /usr/bin/python$$v /usr/bin/nosetests -v --exclude='testPackUnpackExternal' -A "not network" || /bin/true ; \
 	done



unblock mpi4py/2.0.0-2.1

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

--- End Message ---
--- Begin Message ---
clone 856349 -1
severity -1 serious
fixed -1 2.0.0-2.1
close -1
thanks

Drew Parsons:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package mpi4py
> 
> mpi4py in testing (2.0.0-2) FTBFS due to errors in some tests (release
> critical bug #856349)
> .
> 2.0.0-2.1 fixes the FTBFS by treating test errors as warnings.
> 
> [...]
> 
> unblock mpi4py/2.0.0-2.1
> 
> [...]

Ok, Unblocked.

I have also cloned #856349 to ensure we can track that the fix migrates
to testing.

Thanks,
~Niels

--- End Message ---

Reply to: