On Mon, May 20, 2019 at 4:50 PM Mathieu Malaterre wrote:
>
> Gert,
>
> On Mon, May 20, 2019 at 3:31 PM Andreas Tille wrote:
> >
> > Hint, hint, hint: Feel free to do an NMU / team upload of RC buggy
> > package.
>
> What's your opinion on this ? Revert to charls 1.x as suggested or
>
Gert,
On Mon, May 20, 2019 at 3:31 PM Andreas Tille wrote:
>
> Hint, hint, hint: Feel free to do an NMU / team upload of RC buggy
> package.
What's your opinion on this ? Revert to charls 1.x as suggested or
investigated actual regression ?
Hint, hint, hint: Feel free to do an NMU / team upload of RC buggy
package. That's really welcome and will speed up the release.
Thanks a lot, Andreas.
On Mon, May 20, 2019 at 02:38:23PM +0200, Mathieu Malaterre wrote:
> Control: severity -1 grave
> Justification: Debian patches are introducing
Control: severity -1 grave
Justification: Debian patches are introducing regression compared to upstream
Steps:
$ cd /tmp/
$ wget
ftp://dicom.offis.de/pub/dicom/offis/software/dcmtk/dcmtk364/bin/dcmtk-3.6.4-linux-x86_64-static.tar.bz2
$ tar xf dcmtk-3.6.4-linux-x86_64-static.tar.bz2
$ cd
Control: severity -1 important
Control: tags -1 patch
Turns out that every single DICOM instance that I tried seems to
produce the exact same SEGFAULT.
Running in valgrind show something like this for me (*).
I would suggest the following trivial patch to have a stable
DCMTK+JPEGLS encoder in
5 matches
Mail list logo