Hi Mathieu, On Tue, Sep 15, 2015 at 09:32:14AM +0200, Mathieu Malaterre wrote: > Package: dcmtk > Version: 3.6.1~20150629-1 > Severity: grave > Justification: causes non-serious data loss > > As describe in the previous bug report: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715011#50 > > One cannot simply upgrade dcmtk package without grave data loss > (index.dat binary format is not compatible), which should result as > -best case- index.dat corruption, or dcmqrscp to segfault and not > start. > > This correspond to the following upstream commit: > c8423ab1fcf0273061462697b8eca56f894984c7
I can n ot find this commit under git clone https://github.com/commontk/DCMTK.git Would you be able to provide a patch incorporating this commit to fix the issue? Do you think it is better to switch back to the former version of dcmtk? > This should be clearly indicated during package upgrades. Marking as > grave as I believe the DICOM file themselves are still kept as-is, so > this is IMHO not a critical `causes serious data loss`. Upstream may > have a finer understanding of the loss. You perfectly know that I have no contact to upstream and I'm quite busy with a lot of stuff. If you are interested to help it would be great to discuss the issue with upstream how to fix this issue in Debian in the best possible way. My motivation was simply to avoid the need for a migration of two dcmtk versions - one in unstable and one in experimental. I do not feel able to maintain two versions. May be also the later snapshot 3.6.1_20150924 would fix the issue? Any hint would be welcome. Kind regards Andreas. -- http://fam-tille.de
