Bug#715029: Fixed minor bug in DICOM upper layer FSM.

2021-11-18 Thread Mathieu Malaterre
Control: retitle -1 DICOM upper layer FSM bug Control: fixed -1 3.6.4-2.1 Control: tags -1 upstream patch fixed-upstream confirmed According to upstream, this bug is solved: % git show --oneline 7a000a8bc84d58fab5368964d49757f7e33036b2 | head -1 7a000a8bc Fixed minor bug in DICOM upper layer FSM.

Bug#715029: Fwd: dcmnet/libsrc/dulfsm.cc

2017-03-17 Thread Jörg Riesmeier
The following commit fixes this issue: http://git.dcmtk.org/?p=dcmtk.git;a=commit;h=7a000a8bc84d58fab5368964d49757f7e33036b2

Bug#715029: Fwd: dcmnet/libsrc/dulfsm.cc

2013-09-04 Thread Mathieu Malaterre
severity 715029 minor tags 715029 + wontfix tags 715029 + upstream tags 715029 + confirmed thanks > -{A_ASSOCIATE_RQ_PDU_RCV, STATE5, AE_4, STATE1, "", "", NULL}, back to at least February 1995 (CEN/DICOM Toolkit V1.5), and probably this bug has been in there right from the very beginning

Bug#715029:

2013-08-02 Thread Mathieu Malaterre
Looks like an issue in the standard itself. Need to create a CP, and have it corrected upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#715029: Fwd: dcmnet/libsrc/dulfsm.cc

2013-07-05 Thread Mathieu Malaterre
Package: dcmtk While doing some QA with DCMTK, here is what I found out. It looks as if DCMTK uses a custom transition table compared to the one defined in PS 3.8 - 2011: @@ -285,7 +285,7 @@ static FSM_ENTRY StateTable[DUL_NUMBER_OF_EVENTS][DUL_NUMBER_OF_STATES] = { {A_ASSOCIATE_RQ_PDU