On 03/09/14 14:56, Steve Robbins wrote: > > > On September 3, 2014 5:44:22 AM CDT, Emilio Pozuelo Monfort > <po...@debian.org> wrote: >> On 02/09/14 07:23, Steve M. Robbins wrote: >>> The recent build failure of elastix (#759945) is caused by the >>> libhdf5.so path having changed, presumably due to #755539. The path >>> is encoded into insighttoolkit4-dev's file >>> /usr/lib/cmake/ITK-4.6/ITKTargets-none.cmake so Elastix will need a >>> binnmu as soon as insighttoolkit is rebuilt. >> >> It should build fine now, right? So why is the binNMU needed? There was >> a >> temporary problem on insighttoolkit4 that is now fixed, but no binNMUs >> on >> elastix or plastimatch should be needed AFAICS. > > Could be. I was just presenting the results of my investigation into the > build failure. > > 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. Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5407161e.4060...@debian.org
