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

Bug#814936: marked as done (transition: mpi-defaults)

Your message dated Thu, 17 Mar 2016 00:55:53 +0100
with message-id <56E9F289.50405@debian.org>
and subject line Re: Bug#814936: transition: mpi-defaults
has caused the Debian Bug report #814936,
regarding transition: mpi-defaults
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.)


-- 
814936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814936
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: transition
Tags: confirmed

Last week I switched the default openmpi implementation on s390x from
mpich to openmpi.

Now the default MPI implementation is the same in all release
architectures, which is nice per se.

From what I can see in the past there were no rebuilds for this, but (as
also others pointed out elsewhere) it would only make sense.
There are also packages already failing to build due to dependencies
being built against mpich but now building against openmpi.

According to my grepping the packages affected are a strict subset of
the ones doing the openmpi transition.
Though maybe a ben tracker is better for this job.  I try here to forge
a valid thing, but I'm not sure of what I'm writing:

is_affected = .build-depends ~ /mpi-default-dev/ & ( .depends ~ /libmpich.*/ | /libopenmpi.*/ )
is_good = .depends ~ /libopenmpi.*/
is_bad = .depends ~ /libmpich.*/

I expect at least the packages listed in the attachment in #813128#135.


A handful need sourceful changes, I already done a couple and I'll do
the rest too.

I welcome any comments on the plan, or please schedule the
appropriated rebuilds.


I'm sorry this caused more mess and noise than what I originally
planned, but from what I can see everything goes smoothly, at least
(except for the noise itself).

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 01/03/16 00:04, Emilio Pozuelo Monfort wrote:

On 29/02/16 20:10, Mattia Rizzolo wrote:


ok, it looks good.
Except for mpi4py and nwchem that FTBFS, I find this transition to be
cool.

Do you notice something that should be take care of?
Otherwise I'd call this over.


Those are the remaining ones yes.
As discussed on IRC, mpi4py is now good, and nwchem is sid only. So let's close this. 

Cheers,
Emilio

--- End Message ---
Reply to: