On Tue, May 19, 2009 at 01:54:24PM +0200, Mathieu Malaterre wrote: > Ah ok, package are unrelated and one version live aside from the > other... So this means gdcm 2.0.10 links to VTK 5.2 on lenny, but a > gdcm backport package will links to VTK 5.0. > I think it makes sense now. > > I still do not understand why I have to do that manually, I thought I > was missing something...
IMHO this has to be done manually because neither dpkg-buildpackage nor dpkg have any means to "choose" a package - so you have to tell them explicitely > > Unfortunately thses do not (yet) show up on our tasks pages because > > the code which generates the tasks pages only parses Packages file of > > i386 (yes, I know this sucks and I'm working on it in all the small > > chunks of spare time). So as long as gdcm is not available for i386 > > it will not show up on our tasks pages or I finish the UDD using > > tasks pages - whatever comes first. > > Which sucks even more as GDCM cannot be build on i386 because VTK 5.2 > package has some issue: As I said: I'm working on it ... > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529193 > -> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529292 > > The bug is solved in VTK collab-maintain git repository... So chances are good that this will be solved soon. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
