Bug#864650: transition: mumps
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 jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Reply to: