On Mon, 2016-11-21 at 09:54 +0100, Emilio Pozuelo Monfort wrote: > On 18/11/16 05:01, Drew Parsons wrote: > > > > dolfin doesn't seem to have gotten identified for autobuild against > > the new versions of swig and boost. Please binNMU. > > > It is built against boost 1.62, and I don't see any swig transition. > Why is a > rebuild needed for swig?
Oh yeah, you're right about boost. My system was unable to upgrade to boost 1.62 and wanted to remove dolfin if I try to force it. So I thought the problem was a a dolfin dependency, but the actual conflict was with libboost-1.61-dev. There must have been a lag when the 1.62 upload wasn't complete so I couldn't replace 1.61. So I've got the boost upgrade completed now, thanks for the clarification. The swig dependency is real. dolfin has a tight dependency on swig because of bug#675207. So python-dolfin Depends: swig3.0 (>= 3.0.7), swig3.0 (<< 3.0.8~) We need that tight dependency updated. Is there a way to declare the tight dependency so that it gets picked up by the autobuilders automatically? I gather it's not as straightforward as normal library dependencies, since it's not a question of SONAME compatibility. Drew
