Package: dcmtk
Version: 3.5.4-2
Severity: important
Tags: patch

According to the dcmdk faq
(http://forum.dcmtk.org/viewtopic.php?t=994&sid=614b4bd476b4bec363bcefcb586279cd),
DCMTK 3.5.4 contains a bug in findscu and movescu when using the
--add-override-key (-k) option, which causes these tools to abort
with the error message

   error: bad key format or dictionary name not found in dictionary: 

I resdiscovered this error when using the findscu from the debian
dcmtk package.  A fixed version of the source for findscu and
movescu is available from the dcmtk ftp server at
ftp://dicom.offis.de/pub/dicom/offis/software/dcmtk/dcmtk354/patch/

Compiling these patched versions seems to have elimited the error
message.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages dcmtk depends on:
ii  adduser                   3.102          Add and remove users and groups
ii  libc6                     2.3.6.ds1-13   GNU C Library: Shared libraries
ii  libdcmtk1                 3.5.4-2        The OFFIS DICOM toolkit runtime li
ii  libgcc1                   1:4.1.1-21     GCC support library
ii  libjpeg62                 6b-13          The Independent JPEG Group's JPEG 
ii  libpng12-0                1.2.15~beta5-1 PNG library - runtime
ii  libssl0.9.8               0.9.8c-4       SSL shared libraries
ii  libstdc++6                4.1.1-21       The GNU Standard C++ Library v3
ii  libtiff4                  3.8.2-7        Tag Image File Format (TIFF) libra
ii  libwrap0                  7.6.dbs-13     Wietse Venema's TCP wrappers libra
ii  libxml2                   2.6.27.dfsg-1  GNOME XML library
ii  zlib1g                    1:1.2.3-13     compression library - runtime

dcmtk recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to