Hi Mathieu, Clearly, there is a bug.
On February 8, 2014 03:35:58 PM Mathieu Malaterre wrote: > Your point is correct, importing *solely* ITK 4.0 does work. However > what does not work is clearly indicated at > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728121#10 > > This is a ~4 lines demonstration which makes the package unusable for > a lot of us. It's true that any given bug will often render the package unusable for some purposes. It's clear in this case that it is usable for some use cases, but not those that include GDCM. In my reading of bug severities [1], I would not have chosen 'grave', but maybe 'important' ("has a major effect on the usability ..."). That's why I raised the question. Note also that the policy violation you pointed out is a "should" not a "must", so I would not choose "serious" either. But I'm not hung up on getting the severity right. More important is to fix the bug. [1] https://www.debian.org/Bugs/Developer#severities: grave makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. serious is a severe violation of Debian policy (roughly, it violates a "must" or "required" directive), or, in the package maintainer's or release manager's opinion, makes the package unsuitable for release. important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. > As explained in ยง4.13: > > https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles > > "Debian packages should not make use of these convenience copies > unless the included package is explicitly intended to be used in this > way." > > You are required to explicitely state why ITK 4.0 package is using > it's convienient GDCM copy. I think I switched to the internal GDCM because ITK fails to build on some architectures using the system gdcm. But I could be mis-remembering. If you want to do the experiment, be sure to compile on both amd64 and i386. I should note that I always intended this change to be temporary and now that things are settled down, I agree that the system libraries should be used as appropriate and possible. I'd also like to invite any interested debian-med maintainer to go ahead and address this. I simply lack the time right now to tackle this myself. Regards, -Steve
signature.asc
Description: This is a digitally signed message part.
