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

Bug#837688: marked as done (nmu: mpi4py_2.0.0-2)



Your message dated Tue, 13 Sep 2016 19:44:50 +0200
with message-id <c705f892-c7ab-7c86-5b14-f96dc3d24323@debian.org>
and subject line Re: Bug#837688: nmu: mpi4py_2.0.0-2
has caused the Debian Bug report #837688,
regarding nmu: mpi4py_2.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.)


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

nmu mpi4py_2.0.0-2 . ANY . unstable . -m "Rebuild against libopenmpi2"

Should resolve #837633

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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)

--- End Message ---
--- Begin Message ---
On 13/09/16 16:25, Yaroslav Halchenko wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> 
> nmu mpi4py_2.0.0-2 . ANY . unstable . -m "Rebuild against libopenmpi2"
> 
> Should resolve #837633

This needed a give back, which I had already scheduled.

Emilio

--- End Message ---

Reply to: