Bug#864650: transition: mumps

2017-07-14 Thread Emilio Pozuelo Monfort
Control: tags -1 confirmed

On 14/07/17 05:04, Drew Parsons wrote:
> On Tue, 2017-06-27 at 18:51 +0100, Jonathan Wiltshire wrote:
>> On Mon, Jun 26, 2017 at 09:10:17PM +0800, Drew Parsons wrote:
>>>
>>> That's right.  But it makes it simpler for stable users to just
>>> grab
>>> dolfin 2016.2.0-4 from snapshot archives if it hasn't been built
>>> against new libraries like mumps 5.1.  Minimises the number of
>>> codependent packages they'd have to pull in.
>>
>> In that case, please come back when you're ready to proceed, in case
>> there
>> is by then a collision with another transition.
> 
> I'm happy with the state of dolfin in testing now.  I'd like to proceed
> with the MUMPS 5.1 transition now.
> 
> Since petsc and slepc will be rebuilt as part of the mumps transition
> anyway, I'll also upgrade petsc 3.7.6 and slepc 3.7.4. These are not a
> true transition since their soname does not change.

Go ahead.

Emilio



Bug#864650: transition: mumps

2017-07-13 Thread Drew Parsons
On Tue, 2017-06-27 at 18:51 +0100, Jonathan Wiltshire wrote:
> On Mon, Jun 26, 2017 at 09:10:17PM +0800, Drew Parsons wrote:
> > 
> > That's right.  But it makes it simpler for stable users to just
> > grab
> > dolfin 2016.2.0-4 from snapshot archives if it hasn't been built
> > against new libraries like mumps 5.1.  Minimises the number of
> > codependent packages they'd have to pull in.
> 
> In that case, please come back when you're ready to proceed, in case
> there
> is by then a collision with another transition.

I'm happy with the state of dolfin in testing now.  I'd like to proceed
with the MUMPS 5.1 transition now.

Since petsc and slepc will be rebuilt as part of the mumps transition
anyway, I'll also upgrade petsc 3.7.6 and slepc 3.7.4. These are not a
true transition since their soname does not change.

Drew



Bug#864650: transition: mumps

2017-06-27 Thread Jonathan Wiltshire
Control: tag -1 - confirmed
Control: tag -1 moreinfo

On Mon, Jun 26, 2017 at 09:10:17PM +0800, Drew Parsons wrote:
> On Mon, 2017-06-26 at 14:01 +0100, Jonathan Wiltshire wrote:
> > On 2017-06-26 13:34, Drew Parsons wrote:
> > > 
> > > Thanks Jon.  I'll wait first for dolfin  to get out of
> > > NEW
> > > and stabilise in testing (to make it simpler for any stable users
> > > wanting to use dolfin with python3), and proceed with the mumps
> > > upgrade
> > > after that.
> > 
> > I'm not sure I understand how this affects stable. In any case, a 
> > reverse
> > dependency waiting in NEW doesn't hold up starting the transition.
> 
> That's right.  But it makes it simpler for stable users to just grab
> dolfin 2016.2.0-4 from snapshot archives if it hasn't been built
> against new libraries like mumps 5.1.  Minimises the number of
> codependent packages they'd have to pull in.

In that case, please come back when you're ready to proceed, in case there
is by then a collision with another transition.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



Bug#864650: transition: mumps

2017-06-26 Thread Drew Parsons
On Mon, 2017-06-26 at 14:01 +0100, Jonathan Wiltshire wrote:
> On 2017-06-26 13:34, Drew Parsons wrote:
> > 
> > Thanks Jon.  I'll wait first for dolfin  to get out of
> > NEW
> > and stabilise in testing (to make it simpler for any stable users
> > wanting to use dolfin with python3), and proceed with the mumps
> > upgrade
> > after that.
> 
> I'm not sure I understand how this affects stable. In any case, a 
> reverse
> dependency waiting in NEW doesn't hold up starting the transition.

That's right.  But it makes it simpler for stable users to just grab
dolfin 2016.2.0-4 from snapshot archives if it hasn't been built
against new libraries like mumps 5.1.  Minimises the number of
codependent packages they'd have to pull in.

Drew



Bug#864650: transition: mumps

2017-06-26 Thread Jonathan Wiltshire

On 2017-06-26 13:34, Drew Parsons wrote:

On Sun, 2017-06-25 at 12:23 +0100, Jonathan Wiltshire wrote:

Control: tag -1 confirmed

Hi,

On Mon, Jun 12, 2017 at 08:32:19PM +0800, Drew Parsons wrote:
> This transition request concerns mumps. It has been behaving itself
> in
> experimental and is enthusiastic to play with the big kids in
> unstable.

Time for it to graduate; please go ahead.



Thanks Jon.  I'll wait first for dolfin 2016.2.0-4 to get out of NEW
and stabilise in testing (to make it simpler for any stable users
wanting to use dolfin with python3), and proceed with the mumps upgrade
after that.


I'm not sure I understand how this affects stable. In any case, a 
reverse

dependency waiting in NEW doesn't hold up starting the transition.

Thanks,

--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 SaaS == Saunas as a Service
 broonie, more like Sauna as additional Storage



Bug#864650: transition: mumps

2017-06-26 Thread Drew Parsons
On Sun, 2017-06-25 at 12:23 +0100, Jonathan Wiltshire wrote:
> Control: tag -1 confirmed
> 
> Hi,
> 
> On Mon, Jun 12, 2017 at 08:32:19PM +0800, Drew Parsons wrote:
> > This transition request concerns mumps. It has been behaving itself
> > in
> > experimental and is enthusiastic to play with the big kids in
> > unstable.
> 
> Time for it to graduate; please go ahead.


Thanks Jon.  I'll wait first for dolfin 2016.2.0-4 to get out of NEW
and stabilise in testing (to make it simpler for any stable users
wanting to use dolfin with python3), and proceed with the mumps upgrade
after that.

Drew



Bug#864650: transition: mumps

2017-06-25 Thread Jonathan Wiltshire
Control: tag -1 confirmed

Hi,

On Mon, Jun 12, 2017 at 08:32:19PM +0800, Drew Parsons wrote:
> This transition request concerns mumps. It has been behaving itself in
> experimental and is enthusiastic to play with the big kids in unstable.

Time for it to graduate; please go ahead.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



Bug#864650: transition: mumps

2017-06-12 Thread Drew Parsons
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

With stretch released, we plan to upgrade our numerical computational
packages:
scalapack to 2.0.2
mumps to 5.1.1
scotch to 6.0
etc

This transition request concerns mumps. It has been behaving itself in
experimental and is enthusiastic to play with the big kids in unstable.

Ben file:

title = "mumps";
is_affected = .depends ~ "libmumps-4.10.0" | .depends ~ "libmumps-5.1.1";
is_good = .depends ~ "libmumps-5.1.1";
is_bad = .depends ~ "libmumps-4.10.0";


-- 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-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)