Package: gdcm Version: 2.4.4-4 Severity: grave Tags: patch Now that upstream has clarified the situation with Activiz.NET:
http://public.kitware.com/pipermail/vtk-developers/2015-September/032491.html I suggest that: 1. We revert back (temporarily for stretch) to the GDCM C# SWIG layer (this is compatible with GDCM 2.2.x debian package), 2. Apply the attached patch, 3. Leave 777765 open, 4. Leave mummy and activiz.net in current state, so they will get auto-removed 5. once upstream (=kitware) updates Activiz.NET with a CastXML based build system, revert the operations ! (I am not sure about the status of cableswig, but as above, I would not touch it). I've used the severity of grave, since otherwise GDCM will get removed simply because if Activiz.NET which would otherwise imapct lots of dependencies. Feel free to downgrade. 2cts
gdcm_dotnet.patch
Description: Binary data
