Processed: Re: Bug#895193: transition: openmpi

2018-04-13 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 confirmed
Bug #895193 [release.debian.org] transition: openmpi
Added tag(s) confirmed.

-- 
895193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#895193: transition: openmpi

2018-04-13 Thread Emilio Pozuelo Monfort
Control: tags -1 confirmed

On 11/04/18 11:12, Alastair McKinstry wrote:
> 
> 
> On 11/04/2018 10:07, John Paul Adrian Glaubitz wrote:
>> On 04/11/2018 10:53 AM, Alastair McKinstry wrote:
>>> As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a
>>> problem; it had been dropped upstream because of an unknown bug, now
>>> fixed).
>>
>> Oh, really, they fixed that? I already had given up hopes and
>> therefore ignored
>> the thread on github out of frustration.
>>
>>From the thread (and related PRs it references) its fixed and works as
> long as -O3 is used.
> I've implemented and tested this in ./rules.
> 
>>> The other non-release archs were failing due to missing dependencies: in
>>> particular java support (not used by any package in stable/testing) and
>>> pmix (new; not used in testing/stable; pmix enables scaling to ~100,000+
>>> nodes, which is unlikely to be needed).
>>
>> I am working on fixing the remaining OpenJDK issues. I'm an upstream
>> committer in the OpenJDK project, so I can commit all changes myself.
>>
> Ok. I've just disabled support as necessary for archs with openjdk issues.
> While a riscv64 build has not yet occurred (awaiting in queue to see),
> all issues on all other archs should now be resolved,
> making the transition possible.

Great. Please go ahead.

Cheers,
Emilio



Bug#895193: transition: openmpi

2018-04-11 Thread Alastair McKinstry


On 11/04/2018 10:07, John Paul Adrian Glaubitz wrote:
> On 04/11/2018 10:53 AM, Alastair McKinstry wrote:
>> As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a
>> problem; it had been dropped upstream because of an unknown bug, now
>> fixed).
>
> Oh, really, they fixed that? I already had given up hopes and
> therefore ignored
> the thread on github out of frustration.
>
>From the thread (and related PRs it references) its fixed and works as
long as -O3 is used.
I've implemented and tested this in ./rules.

>> The other non-release archs were failing due to missing dependencies: in
>> particular java support (not used by any package in stable/testing) and
>> pmix (new; not used in testing/stable; pmix enables scaling to ~100,000+
>> nodes, which is unlikely to be needed).
>
> I am working on fixing the remaining OpenJDK issues. I'm an upstream
> committer in the OpenJDK project, so I can commit all changes myself.
>
Ok. I've just disabled support as necessary for archs with openjdk issues.
While a riscv64 build has not yet occurred (awaiting in queue to see),
all issues on all other archs should now be resolved,
making the transition possible.

>> So, the expected changes to mpi-defaults will no longer be needed.
> Yay, thanks so much for this!
>
> Adrian
>

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 



Bug#895193: transition: openmpi

2018-04-11 Thread John Paul Adrian Glaubitz

On 04/11/2018 10:53 AM, Alastair McKinstry wrote:

As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a
problem; it had been dropped upstream because of an unknown bug, now fixed).


Oh, really, they fixed that? I already had given up hopes and therefore ignored
the thread on github out of frustration.


The other non-release archs were failing due to missing dependencies: in
particular java support (not used by any package in stable/testing) and
pmix (new; not used in testing/stable; pmix enables scaling to ~100,000+
nodes, which is unlikely to be needed).


I am working on fixing the remaining OpenJDK issues. I'm an upstream
committer in the OpenJDK project, so I can commit all changes myself.


So, the expected changes to mpi-defaults will no longer be needed.

Yay, thanks so much for this!

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#895193: transition: openmpi

2018-04-11 Thread Alastair McKinstry
As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a
problem; it had been dropped upstream because of an unknown bug, now fixed).

The other non-release archs were failing due to missing dependencies: in
particular java support (not used by any package in stable/testing) and
pmix (new; not used in testing/stable; pmix enables scaling to ~100,000+
nodes, which is unlikely to be needed).

So, the expected changes to mpi-defaults will no longer be needed.


On 08/04/2018 10:28, Mattia Rizzolo wrote:
> On Sun, Apr 08, 2018 at 10:03:23AM +0100, Alastair McKinstry wrote:
>> Now with openmpi 3.0.1 in the archive, we can start transtion the existing
>> packages to the archive so that the new openmpi package can transition to
>> testing. The following source packages need to be rebuilt:
> But the new openmpi builds in *a lot* fewer architectures than the
> current one (talking about ports here).
>
> If you don't plan on having openmpi fixed on all those architectures,
> please coordinate with debian-ports to:
> 1) switch mpi-defaults there and update the available archs
> 2) do the transition there (see https://bugs.debian.org/814936 and the
>README.source I committed to git after the last release)
>

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




signature.asc
Description: OpenPGP digital signature


Bug#895193: transition: openmpi

2018-04-08 Thread Mattia Rizzolo
On Sun, Apr 08, 2018 at 10:03:23AM +0100, Alastair McKinstry wrote:
> Now with openmpi 3.0.1 in the archive, we can start transtion the existing
> packages to the archive so that the new openmpi package can transition to
> testing. The following source packages need to be rebuilt:

But the new openmpi builds in *a lot* fewer architectures than the
current one (talking about ports here).

If you don't plan on having openmpi fixed on all those architectures,
please coordinate with debian-ports to:
1) switch mpi-defaults there and update the available archs
2) do the transition there (see https://bugs.debian.org/814936 and the
   README.source I committed to git after the last release)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#895193: transition: openmpi

2018-04-08 Thread Alastair McKinstry
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

(please explain about the transition: impacted packages, reason, ...
 for more info see: https://wiki.debian.org/Teams/ReleaseTeam/Transitions)
Now with openmpi 3.0.1 in the archive, we can start transtion the existing
packages to the archive so that the new openmpi package can transition to
testing. The following source packages need to be rebuilt:

aces3
adios
apbs
armci-mpi
arpack
asl
autodock-vina
blacs-mpi
boost1.62
boost1.63
calculix-ccx
camitk
cctools
choreonoid
ckon
code-saturne
coin3
coinor-ipopt
cp2k
csound
deal.ii
dnsdist
dolfin
dpuser
dune-common
dune-functions
dune-geometry
dune-grid
dune-grid-glue
dune-istl
dune-localfunctions
dune-pdelab
dune-typetree
dune-uggrid
elkcode
elpa
espresso
esys-particle
eztrace
fftw
fftw3
flann
flightcrew
freefem++
freeorion
fw4spl
ga
gammaray
gdcm
gerris
getdp
getfem++
gfsview
ghemical
ginkgocadx
gmsh
gpaw
gpsshogi
gretl
gtg-trace
gyoto
hdf-eos5
hdf5
hpcc
hyphy
hypre
ifrit
iqtree
itksnap
kido
lammps
libghemical
libgpiv
libosl
liggghts
litecoin
lizardfs
luabind
magics++
mathgl
med-fichier
meep-mpi-default
mia
molds
mpb
mpgrafic
mpi4py
mpqc
mpqc3
mrbayes
mrmpi
mumps
ncl
neuron
nifti2dicom
nwchem
oasis3
octave-mpi
odb-api
odin
open-coarrays
opencv
openfoam
openmx
orthanc
orthanc-dicomweb
orthanc-postgresql
orthanc-webviewer
orthanc-wsi
otf
p4est
palabos
paraview
pcl
pdns-recursor
performous
petsc
petsc4py
pnetcdf
prime-phylo
pysph
python-casmoothing
quickfix
r-cran-readr
ray
regina-normal
rheolef
rmpi
roboptim-core
ros-pcl-conversions
ruby-mpi
scalapack
scilab
scotch
scram
sdpa
sfcgal
silo-llnl
slepc
slepc4py
slic3r
slic3r-prusa
spooles
spring
springlobby
starpu
subcommander
sundials
superlu-dist
synfig
syrthes
tachyon
tessa
therion
tiledarray
trilinos
ui-gxmlcpp
ui-utilcpp
valgrind
vtk-dicom
vtk6
woo
xdmf
xmds2
yade
zypper

During a rebuild, there were no build failures due to openmpi changes. The 
following packages failed on pre-existing
FTBFS:

nwchem
tiledarray


Ben file:

title = "openmpi";
is_affected = .depends ~ "libopenmpi2" | .depends ~ "libopenmpi3";
is_good = .depends ~ "libopenmpi3";
is_bad = .depends ~ "libopenmpi2";

Thanks
Alastair McKinstry

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)