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
