Bug#755539: Elastix needs binnmu after ITK
On 03/09/14 19:00, Steve M. Robbins wrote:
> On September 3, 2014 03:22:38 PM Emilio Pozuelo Monfort wrote:
>
>>> Since the .so file location changed, it is possible that the shared
>>> library itself changed location or soname.
>> Both the location and the SONAME of libhdf5 changed.
>>
>>> So in addition to verifying that it still builds, you need to verify that
>>> the EXISTING elastix binary continues to function.
>> If you find it breaks and a binNMU is needed, let us know.
>
> I suppose one could do some investigation -- it won't be me -- but why bother?
> The SONAME changed so clearly something changed. Why are we having this
> discussion? Just schedule a rebuild!
Not gonna happen.
If your package needs a specific version of libhdf5, then it should depend on
that. AFAICS elastix doesn't depend on hdf5 at all, so if it breaks after a
SONAME change in hdf5, then it's a serious bug in your package and a binNMU is
not the way to solve it.
Emilio
Reply to: