Hi Andreas, On Tue, Jun 24, 2008 at 10:17 PM, Andreas Tille <[EMAIL PROTECTED]> wrote: > On Tue, 24 Jun 2008, Mathieu Malaterre wrote: > >> I have just release GDCM 2.0.6. See link for more info: >> >> http://gdcm.sourceforge.net/wiki/index.php/GDCM_Release_2.0#GDCM_2.0.6 >> >> I have completely rework the debian/* files so the package should be a >> valid debian package out of the box. > > Many thanls for keeping us informed.
np > I'll just have a look onto this. > I don not remember whether I mentioned in previous mails that keeping > the debian directory in the upstream source is depreciated for several > reasons. If you are interested I could try to assemble a list of > several postings on Debian related lists. No that's fine, I believe you. > Another problem I'm currently > facing by this approach is that Debian Med packaging policy says that > only the difference to the upstream source should be kept in Debian Med > SVN, which is in principle the debian directory. But what should I > put into SVN if debian is part of the upstream source? I have not the slightest idea. I'll post the question on debian-dev mailing list. > If you are convinced that shipping the debian dir with upstream source > is not a really clever way and want to store it rather in our SVN, just > tell me and I'll grant you access. That's a very good question too. If you do not mind, I'll try to clear a couple of things first on debian-dev. >> Let me know if you find anything wrong, > > I tried to build the package and got: > > ... > -- Looking for _stricmp > -- Looking for _stricmp - not found > -- Looking for _strnicmp > -- Looking for _strnicmp - not found > -- Looking for _snprintf > -- Looking for _snprintf - not found > CMake Error: VTK not found. Set the VTK_DIR cmake cache entry to the > directory containing VTKConfig.cmake. This is either the root of the build > tree, or PREFIX/lib/vtk for an installation. For VTK 4.0, this is the > location of UseVTK.cmake. This is either the root of the build tree or > PREFIX/include/vtk for an installation. > -- Configuring done > make: *** [debian/configure-python2.4-stamp] Fehler 255 > dpkg-buildpackage: Fehlschlag: debian/rules build gab Fehler-Exitstatus 2 > error: cannot find binary, udeb or source package *.deb in dist or lab > (skipping) In Build-Depends I have set: libvtk5-dev. There is currently an issue in debian stable that prevent the build as described here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486794 It should work on a debian testing and later though. I was not sure if I had to force to a minimal version of python-vtk, since I do not know when the bug will be solve. > I guess the reason might be a missing build depends (but this is just a wild > guess). I am not clear how in the world I manage to do it, but I used an incorrect path to UseVTK.cmake. The debian file: gdcm/debian/rules should be modified this way: $ svn di rules Index: rules =================================================================== --- rules (revision 3595) +++ rules (working copy) @@ -54,7 +54,7 @@ -DGDCM_USE_SYSTEM_UUID:BOOL=ON \ -DGDCM_USE_SYSTEM_ZLIB:BOOL=ON \ -DGDCM_USE_VTK:BOOL=ON \ - -DVTK_DIR:PATH=/usr/lib/vtk/ \ + -DVTK_DIR:PATH=/usr/lib/vtk-5.0/ \ -DPREFERRED_PYTHON_VERSION=python$* touch $@ I'll commit the patch to svn until I find a solution where to leave those debian file. > I'm really happy about your obvious and continuos interest in the Debian Med > project > and I hope that we now can really stort working on this. Even if I'm > currently > overloaded with DebConf stuff perhaps some volunteers might start working > together > with you. No problem ! Thanks for your supportive feedback, I understand you are very busy, but you still manage somehow to find time :) Regards, -- Mathieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
