[Debian-med-packaging] [sanvila at debian.org: Bug#817163: camitk: FTBFS when built with dpkg-buildpackage -A (191 tests failed out of 191)]

Mon Mar 21 06:40:56 UTC 2016

Dear Andreas,

Thank you for your email. Sorry about not keeping in touch about 
everything. I was about to contact you very soon (with some good news), 
but I now seize this opportunity to communicate a bit better!

Here are the state of the CamiTK development upstream:
- version 3.5 was released a few weeks ago. It was mainly a bug fixing 
release for version 3.4, using the same dependencies as version 3.4 
(Qt4, Vtk5, Itk3)
- we are currently working on camitk 4.0, that should be released 
hopefully very soon (the target is before the end of March).
CamiTK 4.0 has the exact same features as CamiTK 3.5 but updates the 
dependencies to Qt5, Vtk6, Itk4 and cmake 3, and make sure it is 
compatible with gcc5/cxx-11. Code written with the 3.4 or 3.5 API would 
have to be alter a bit to take the dependency updates into account, but 
apart from few include differences, should work with 4.0
We are also moving to git for upstream development.
Moving to itk4 is not the main problem, the main problem is to move to 
Qt5 and VTK6 (moving to VTK6 implies moving to Qt5 and we package our 
own version of qtpropertybrowser from Qt Solution that need to be 
updated to Qt5 as well)
- we have noticed bug #817163 (as well as bug #816805 about Qt4 WebKit 
removal).

Here is what we are intending to do:
- leave camitk 3 branch live the end of its software life (3.3.2 on stable)
- update the camitk debian package to support the 4.0 branch

Here are where all your (and everyone's!) advice and guidance are sought:
- What is the easiest way for us and safest way for the users?
It seems better to us to create a new "camitk4" project (preferably on 
git) and specify that "camitk" project is not going to be supported 
after jessie. But do you agree? And if yes, how to do that?
- Concerning bug #817163, yes, I would like some advice! I did not 
really understand what it meant exactly. It seams to me (let me know if 
I am wrong) that it is a consequence of a problematic build of 3.4 on 
sid. I tried to update d/rules to check if 3.5 can be packaged (at least 
in unstable), but, amthought it builds, there is a problem when loading 
the qt plugins that crashed any camitk application. I did not give it 
too much attention as the main idea is to let camitk3 RIP and move to 4.0.
Do you think that waiting to see if the problem remains in 4.0 is a good 
idea? Or am I mistaken with my analysis?

And last question: we noticed that VTK7 is out, do anyone knows if there 
are plans to package it, and if yes is there any targeted date for a 
package?

Thank you in advance!

Kind regards
Emmanuel

On 19/03/16 22:00, Andreas Tille wrote:
> Hi Emmanuel and Nicolas,
>
> I wonder whether you noticed this bug report and know how to deal with
> this.  Feel free to ask if something might remain unclear.
>
> I also noticed that there is a new upstream version available.  What's
> your plan to upgrade the Debian package?  I wonder whether you could
> upgrade camitk to insighttoolkit 4 since we intend to drop version 3 as
> soon as possible.  Please let me know if you see any problems with this.
>
> Kind regards
>
>        Andreas.
>
> ----- Forwarded message from Santiago Vila <sanvila at debian.org> -----
>
> Date: Tue, 08 Mar 2016 16:52:43 +0000
> From: Santiago Vila <sanvila at debian.org>
> To: Debian BTS <submit at bugs.debian.org>
> Subject: Bug#817163: camitk: FTBFS when built with dpkg-buildpackage -A (191 tests failed out of 191)
> X-Debian-PR-Message: report 817163
> X-Debian-PR-Package: src:camitk
> X-Debian-PR-Keywords:
> X-Debian-PR-Source: camitk
>
> Package: src:camitk
> Version: 3.4.0-2
> User: sanvila at debian.org
> Usertags: binary-indep
> Severity: important
>
> Dear maintainer:
>
> I tried to build this package with "dpkg-buildpackage -A"
> (i.e. only architecture-independent packages), and it failed:
>
> --------------------------------------------------------------------------------
> [...]
>   debian/rules build-indep
> # For debian build, do not authorize parallel build (too much RAM
> # needed for Imaging CEP on arch that have small memory size)
> dh build-indep --builddirectory=camitk-build
>     dh_testdir -i -O--builddirectory=camitk-build
>     dh_update_autotools_config -i -O--builddirectory=camitk-build
>     debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_configure -- -DCMAKE_SKIP_RPATH:BOOL=TRUE -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=FALSE -DCMAKE_BUILD_TYPE:STRING=None -DCEP_IMAGING:BOOL=TRUE -DCEP_MODELING:BOOL=TRUE -DAPIDOC_SDK:BOOL=TRUE -DCAMITK_DISABLE_TRANSLATION=TRUE
> 	cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_SKIP_RPATH:BOOL=TRUE -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=FALSE -DCMAKE_BUILD_TYPE:STRING=None -DCEP_IMAGING:BOOL=TRUE -DCEP_MODELING:BOOL=TRUE -DAPIDOC_SDK:BOOL=TRUE -DCAMITK_DISABLE_TRANSLATION=TRUE
> -- The C compiler identification is GNU 5.3.1
> -- The CXX compiler identification is GNU 5.3.1
>
> [... snipped ...]
>
> 	158 - application-testcomponentsitkimage_LEVEL1_7 (Not Run)
> 	159 - application-testcomponentsitkimage_LEVEL1_8 (Not Run)
> 	160 - application-testcomponentsitkimage_LEVEL1_9 (Not Run)
> 	161 - application-testcomponentsitkimage_LEVEL1_10 (Not Run)
> 	162 - application-testcomponentsitkimage_LEVEL1_11 (Not Run)
> 	163 - application-testcomponentsitkimage_LEVEL1_12 (Not Run)
> 	164 - application-testcomponentsitkimage_LEVEL1_13 (Not Run)
> 	165 - application-testcomponentsitkimage_LEVEL1_14 (Not Run)
> 	166 - application-testcomponentsitkimage_LEVEL1_15 (Not Run)
> 	167 - application-testcomponentsitkimage_LEVEL1_16 (Not Run)
> 	168 - application-testcomponentsitkimage_LEVEL1_17 (Not Run)
> 	169 - application-testactionsitkfilters1 (Not Run)
> 	170 - application-testactionsitkfilters2 (Not Run)
> 	171 - application-testactionsitkfilters3 (Not Run)
> 	172 - application-testactionsitkfilters4 (Not Run)
> 	173 - application-testactionsitkfilters5 (Not Run)
> 	174 - application-testactionsitkfilters6 (Not Run)
> 	175 - application-testactionsitkfilters7 (Not Run)
> 	176 - application-testactionsitkfilters8 (Not Run)
> 	177 - application-testactionsitkfilters9 (Not Run)
> 	178 - application-testactionsitksegmentation1 (Not Run)
> 	179 - application-testactionsitksegmentation2 (Not Run)
> 	180 - application-testactionsitksegmentation3 (Not Run)
> 	181 - application-testactionsitksegmentation4 (Not Run)
> 	182 - library-lmltest1 (Not Run)
> 	183 - library-lmltest2 (Not Run)
> 	184 - library-lmltest3 (Failed)
> 	185 - library-pmltest1 (Not Run)
> 	186 - library-pmltest2 (Not Run)
> 	187 - library-pmltest3 (Failed)
> 	188 - application-testcomponentsphysicalmodel1 (Not Run)
> 	189 - application-testcomponentsmmlcomponent1 (Not Run)
> 	190 - application-testactionsmml1 (Not Run)
> 	191 - application-testactionsmml2 (Not Run)
> Errors while running CTest
> debian/rules:80: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 8
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> debian/rules:59: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> --------------------------------------------------------------------------------
>
> Sorry not to have a fix, as I am reporting many bugs similar to
> this one. The common hints are:
>
> * If the only architecture-independent packages are dummy transitional
> ones and they were released with jessie, the easy fix is to drop them
> now.
>
> * When using "dh", it is allowed to use (independently)
> optional targets override_dh_foo-arch and override_dh_foo-indep
> (for several values of "foo").
>
>
> Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
> properly, the package would be suitable to be uploaded in source-only
> form if you wish.
>
> Thanks.
>
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>
>
> ----- End forwarded message -----
>

-- 
Emmanuel Promayon, Maitre de conférences
Univ. Grenoble Alpes / Polytech Grenoble
Laboratoire TIMC-IMAG / équipe GMCAO
Tel. +33/0 456 52 00 03

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2971 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20160321/3a763bba/attachment-0001.bin>