Bug#868355: nmu: ceres-solver_1.12.0+dfsg0-1+b3
On 28/12/17 11:44, Jochen Sprickerhof wrote:
> Hi Emilio,
>
> * Emilio Pozuelo Monfort <pochu@debian.org> [2017-12-27 10:25]:
>> Now, it'd be a different case if your project exposed part of the Eigen ABI, and
>> given there's no shared library, there can't be a SONAME bump so the only way to
>> ensure there are no ABI mismatches is to ensure all projects are built with the
>> same Eigen version.
>
> That's the case for Ceres and PCL. The headers and shared objects shows numerous
> references to Eigen.
>
>> BTW I was going to schedule this binNMU for the time being in order to have a
>> working ceres-solver, but it seems there was an upload since this request was
>> opened. Do you need a binNMU now? If so I'll schedule it. Otherwise let's
>> continue this conversation to clarify whether these binNMUs are required or they
>> could be prevented.
>
> Ceres was, but if you could schedule one for pcl, that would be great. And yes,
> let's use this Bug to continue the discussion.
pcl binNMUed.
If you can come up with an example that shows why building two packages with
different versions of eigen would cause problems, that'd be good.
Cheers,
Emilio
Reply to: