On 24/02/16 19:16, Graham Inggs wrote:
> On 24 February 2016 at 19:33, Emilio Pozuelo Monfort wrote:
>> This is now blocked by #814183 (aka #813722). Any plan to look at that so
>> openmpi can migrate to testing?
>
> I'm happy for #814183 / #813722 to be downgraded so that openmpi can migrate.
>
On 24 February 2016 at 19:33, Emilio Pozuelo Monfort wrote:
> This is now blocked by #814183 (aka #813722). Any plan to look at that so
> openmpi can migrate to testing?
I'm happy for #814183 / #813722 to be downgraded so that openmpi can migrate.
There is an issue on powerpc, but it's not repro
On 01/02/16 15:38, Emilio Pozuelo Monfort wrote:
> On 01/02/16 12:41, Alastair McKinstry wrote:
>>
>> The upload of openmpi1.10 triggered an auto-openmpi transition, as
>> expected and wanted.
>> The rest, is premature.
>
> The problem is that you uploaded the package directly to unstable, without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: mpi-default-dev
Version: 1.2
Severity: wishlist
It has been discussed in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813128
that some MPI packages build in two flavours (openmpi and mpich) and
need to know at upload time for which a
On 13/02/16 14:16, Mattia Rizzolo wrote:
> Ok, This part of the transition is going well enough, modulo #814183.
> As you may know, I switched the mpi-defaults in s390x and x32 to use
> openmpi instead of mpich, now that openmpi builds there too.
> No the default MPI implementation is the same in a
On 16/02/16 11:37, Thibaut Paumard wrote:
> This discussion getting off-topic for this bug, should we move
> somewhere else?
Yes please.
Emilio
On Tue, Feb 16, 2016 at 11:37:19AM +0100, Thibaut Paumard wrote:
> > then mpi-defaults would need a sourceful uploads every single time
> > a new architecture is added (and we want to support MPI there and
> > openmpi builds), and also suddenly file a dozen RC bugs (as all
> > packages using such a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 15/02/2016 21:57, Mattia Rizzolo a écrit :
> On Mon, Feb 15, 2016 at 09:31:43PM +0100, Thibaut Paumard wrote:
>> Le 15/02/2016 19:27, Matthias Klose a écrit :
>>> On 15.02.2016 19:21, Mattia Rizzolo wrote:
On Mon, Feb 15, 2016 at 07:02:06PM +
On Mon, Feb 15, 2016 at 09:31:43PM +0100, Thibaut Paumard wrote:
> Le 15/02/2016 19:27, Matthias Klose a écrit :
> > On 15.02.2016 19:21, Mattia Rizzolo wrote:
> >> On Mon, Feb 15, 2016 at 07:02:06PM +0100, Matthias Klose wrote:
> >>> For this, /usr/share/mpi-default-dev/debian_defaults
> >>> would
On 15.02.2016 21:31, Thibaut Paumard wrote:
Le 15/02/2016 19:27, Matthias Klose a écrit :
On 15.02.2016 19:21, Mattia Rizzolo wrote:
On Mon, Feb 15, 2016 at 07:02:06PM +0100, Matthias Klose wrote:
For this, /usr/share/mpi-default-dev/debian_defaults
would need a new macro
openmpi_archs = ...
Le 15/02/2016 19:27, Matthias Klose a écrit :
> On 15.02.2016 19:21, Mattia Rizzolo wrote:
>> On Mon, Feb 15, 2016 at 07:02:06PM +0100, Matthias Klose wrote:
>>> For this, /usr/share/mpi-default-dev/debian_defaults
>>> would need a new macro
>>> openmpi_archs = ...
>>
>> that's not possible, since
On 15.02.2016 19:21, Mattia Rizzolo wrote:
On Mon, Feb 15, 2016 at 07:02:06PM +0100, Matthias Klose wrote:
For this, /usr/share/mpi-default-dev/debian_defaults
would need a new macro
openmpi_archs = ...
that's not possible, since the current mpi-defaults structure is "use
openmpi everywhere, e
On Mon, Feb 15, 2016 at 07:02:06PM +0100, Matthias Klose wrote:
> well, even if you need to have these hard-coded, then have a control.in
some do (blacs-mpi for example).
> generating a control file, and fails when the control file changes. So you
> regenerate it during the build, but fail if it
On 15.02.2016 18:49, Mattia Rizzolo wrote:
On Mon, Feb 15, 2016 at 06:16:27PM +0100, Matthias Klose wrote:
On 15.02.2016 15:00, Mattia Rizzolo wrote:
On Mon, Feb 15, 2016 at 02:17:02PM +0100, Thibaut Paumard wrote:
Yorick therefore is not broken by the current transition, but requires a
source
On Mon, Feb 15, 2016 at 06:16:27PM +0100, Matthias Klose wrote:
> On 15.02.2016 15:00, Mattia Rizzolo wrote:
> >On Mon, Feb 15, 2016 at 02:17:02PM +0100, Thibaut Paumard wrote:
> >>Yorick therefore is not broken by the current transition, but requires a
> >>source-full rebuilt to get the openmpi fl
On 15.02.2016 15:00, Mattia Rizzolo wrote:
On Mon, Feb 15, 2016 at 02:17:02PM +0100, Thibaut Paumard wrote:
Yorick therefore is not broken by the current transition, but requires a
source-full rebuilt to get the openmpi flavour on s390x, that I can do
right away.
well, turns out there are seve
On Mon, Feb 15, 2016 at 02:17:02PM +0100, Thibaut Paumard wrote:
> Yorick therefore is not broken by the current transition, but requires a
> source-full rebuilt to get the openmpi flavour on s390x, that I can do
> right away.
well, turns out there are several packages in this situation, and i'm
c
Dear Mattia,
Sorry, my first comment was too hasty, I had misread most of your message.
I fully support rebuilding the rdeps of openmpi. gyoto indeed needs to
be recompiled after boost1.58.
Rebuilding Yorick will not help: it actually provides an openmpi and
mpich flavour, and hard-codes the arc
On Sat, 13 Feb 2016 13:16:35 + Mattia Rizzolo wrote:
> Ok, This part of the transition is going well enough, modulo #814183.
> As you may know, I switched the mpi-defaults in s390x and x32 to use
> openmpi instead of mpich, now that openmpi builds there too.
> No the default MPI implementation
Ok, This part of the transition is going well enough, modulo #814183.
As you may know, I switched the mpi-defaults in s390x and x32 to use
openmpi instead of mpich, now that openmpi builds there too.
No the default MPI implementation is the same in all release
architectures, which is nice per se.
> > That's considering only packages in testing, I haven't looked at those
> > in sid, but looks like most of them were not binNMUed, could you please
> > trig some more binNMUs?
>
> Things that are only in sid aren't an issue at this stage.
What needs to happen to petsc? It is only in sid, but i
On Sun, Feb 07, 2016 at 05:44:49PM +, Mattia Rizzolo wrote:
> On Sun, Feb 07, 2016 at 05:22:12PM +, Jonathan Wiltshire wrote:
> > On 2016-02-02 14:59, Alastair McKinstry wrote:
> > >-BEGIN PGP SIGNED MESSAGE-
> > >Hash: SHA256
> > >
> > >I'm enabling a test build (ie with tests ena
On Sun, Feb 07, 2016 at 05:22:12PM +, Jonathan Wiltshire wrote:
> On 2016-02-02 14:59, Alastair McKinstry wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA256
> >
> >I'm enabling a test build (ie with tests enabled) for experimental.
> >I'll see if the tests pass ...
>
> You did it in
On 2016-02-02 14:59, Alastair McKinstry wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm enabling a test build (ie with tests enabled) for experimental.
I'll see if the tests pass ...
You did it in unstable again, but it seems to have gone well. Still
fails to build on s390x, but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/02/2016 00:09, Michael Banck wrote:
> On Tue, Feb 02, 2016 at 12:19:10AM +0100, Matthias Klose wrote:
>> On 01.02.2016 15:38, Emilio Pozuelo Monfort wrote:
>>> On 01/02/16 12:41, Alastair McKinstry wrote:
The upload of openmpi1.10
On Tue, Feb 02, 2016 at 02:40:11PM +, Mattia Rizzolo wrote:
> On Tue, Feb 02, 2016 at 08:44:46AM +0100, Alastair McKinstry wrote:
> > On 01/02/2016 16:34, Michael Banck wrote:
> > > On Mon, Feb 01, 2016 at 11:41:17AM +, Alastair McKinstry wrote:
> > >> Its not fully ready for transition, an
On Wed, Feb 03, 2016 at 12:09:18AM +0100, Michael Banck wrote:
> On Tue, Feb 02, 2016 at 12:19:10AM +0100, Matthias Klose wrote:
> > On 01.02.2016 15:38, Emilio Pozuelo Monfort wrote:
> > >On 01/02/16 12:41, Alastair McKinstry wrote:
> > >>
> > >>The upload of openmpi1.10 triggered an auto-openmpi
On Tue, Feb 02, 2016 at 12:19:10AM +0100, Matthias Klose wrote:
> On 01.02.2016 15:38, Emilio Pozuelo Monfort wrote:
> >On 01/02/16 12:41, Alastair McKinstry wrote:
> >>
> >>The upload of openmpi1.10 triggered an auto-openmpi transition, as
> >>expected and wanted.
> >>The rest, is premature.
> >
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm enabling a test build (ie with tests enabled) for experimental.
I'll see if the tests pass ...
regards
Alastair
On 02/02/2016 15:40, Mattia Rizzolo wrote:
> On Tue, Feb 02, 2016 at 08:44:46AM +0100, Alastair McKinstry wrote:
>> On 01/02/2016
On Tue, Feb 02, 2016 at 08:44:46AM +0100, Alastair McKinstry wrote:
> On 01/02/2016 16:34, Michael Banck wrote:
> > On Mon, Feb 01, 2016 at 11:41:17AM +, Alastair McKinstry wrote:
> >> Its not fully ready for transition, and I need to put a blocker on it.
> >> Small fixes for kFreeBSD, Hurd: (c
On 02/02/16 08:34, Alastair McKinstry wrote:
>
>
>
> On 01/02/2016 15:38, Emilio Pozuelo Monfort wrote:
>> On 01/02/16 12:41, Alastair McKinstry wrote:
>>>
>>> The upload of openmpi1.10 triggered an auto-openmpi transition, as
>>> expected and wanted.
>>> The rest, is premature.
>
>> The proble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/02/2016 16:34, Michael Banck wrote:
> Hi,
>
> On Mon, Feb 01, 2016 at 11:41:17AM +, Alastair McKinstry wrote:
>> The upload of openmpi1.10 triggered an auto-openmpi transition, as
>> expected and wanted.
>> The rest, is premature.
>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/02/2016 15:38, Emilio Pozuelo Monfort wrote:
> On 01/02/16 12:41, Alastair McKinstry wrote:
>>
>> The upload of openmpi1.10 triggered an auto-openmpi transition, as
>> expected and wanted.
>> The rest, is premature.
>
> The problem is that y
On 01.02.2016 15:38, Emilio Pozuelo Monfort wrote:
On 01/02/16 12:41, Alastair McKinstry wrote:
The upload of openmpi1.10 triggered an auto-openmpi transition, as
expected and wanted.
The rest, is premature.
The problem is that you uploaded the package directly to unstable, without
asking for
On 01/02/16 16:10, Mattia Rizzolo wrote:
> On Mon, Feb 01, 2016 at 03:38:21PM +0100, Emilio Pozuelo Monfort wrote:
>> The problem is that you uploaded the package directly to unstable, without
>> asking for a transition slot and without fixing those problems you mention
>> beforehand. It'd have bee
Hi,
On Mon, Feb 01, 2016 at 11:41:17AM +, Alastair McKinstry wrote:
> The upload of openmpi1.10 triggered an auto-openmpi transition, as
> expected and wanted.
> The rest, is premature.
>
> Its not fully ready for transition, and I need to put a blocker on it.
> Small fixes for kFreeBSD, Hurd
On Mon, Feb 01, 2016 at 03:38:21PM +0100, Emilio Pozuelo Monfort wrote:
> The problem is that you uploaded the package directly to unstable, without
> asking for a transition slot and without fixing those problems you mention
> beforehand. It'd have been better to upload it to experimental until th
On 01/02/16 12:41, Alastair McKinstry wrote:
>
> The upload of openmpi1.10 triggered an auto-openmpi transition, as
> expected and wanted.
> The rest, is premature.
The problem is that you uploaded the package directly to unstable, without
asking for a transition slot and without fixing those pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The upload of openmpi1.10 triggered an auto-openmpi transition, as
expected and wanted.
The rest, is premature.
Its not fully ready for transition, and I need to put a blocker on it.
Small fixes for kFreeBSD, Hurd: (conditional use of --verbs in
co
39 matches
Mail list logo
