[Debian-med-packaging] Bug#753809: Bug#753809: ginkgocadx, orthanc and sending/receiving data

[Gert Wollny]

Hi, 

it seems is is a threading and locking problem and has nothing to do
with the actual dicom code, i.e. Orthanc is sending the move request
answer, but Ginkgo timeouts somewhere with a lock hold, and when it
finally reads the answer, Orthanc already hung up. 

My bad, because I tried to clean up threading. It will be fun to debug
this ... 

On the other hand, within Debian/jessie the dicom I used survived the
round-trip Ginkgo-Orthanc server without adding any bogus tag, i.e.
these versions seem to be okay.

Best, 
Gert