# Updating DCMTK to 3.6.5

**URL:** <https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888>\
**Category:** Development\
**Tags:** dicom\
**Created:** [January 21, 2020, 3:33am UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888 "2020-01-21T03:33:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [January 21, 2020, 3:33am UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888/1 "2020-01-21T03:33:42Z")

</div>

Last time Slicer DCMTK was updated was over a year ago, and I would like to update to the latest 3.6.5 release. Currently, Slicer is using a [patched version of DCMTK](https://github.com/commontk/DCMTK/commits/patched-DCMTK-3.6.3_20180621), but the only patch applied is this, as I understand: [https://github.com/commontk/DCMTK/commit/e79118cd2f40b77654630a56bbb17fe0bccc354c](https://github.com/commontk/DCMTK/commit/e79118cd2f40b77654630a56bbb17fe0bccc354c).

It looks like DCMTK 3.6.5 already has this policy applied, see [http://git.dcmtk.org/?p=dcmtk.git;a=commit;h=09d352dd240f36451107665ddece85f9809f4d01](http://git.dcmtk.org/?p=dcmtk.git;a=commit;h=09d352dd240f36451107665ddece85f9809f4d01).

Any objections to trying this out? Should we just update Slicer to check out 3.6.5 from [http://git.dcmtk.org/](http://git.dcmtk.org/), or there is a good reason to keep a fork on GitHub?

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [January 21, 2020, 7:21pm UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888/2 "2020-01-21T19:21:39Z")

</div>

PR submitted and is green on CircleCI:

[https://github.com/Slicer/Slicer/pull/1308](https://github.com/Slicer/Slicer/pull/1308) (corrected)

---

<div class="post-metadata">

**Author:** ![dzenanz](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/dzenanz/32/1992_2.png) [@dzenanz](https://discourse.slicer.org/u/dzenanz)\
**Post date:** [January 21, 2020, 9:46pm UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888/3 "2020-01-21T21:46:43Z")

</div>

Correct PR number is [1308](https://github.com/Slicer/Slicer/pull/1308).

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [January 22, 2020, 12:57am UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888/4 "2020-01-22T00:57:16Z")

</div>

Thank you @fedorov. We are very busy with many things at the project week now but if it’s not that urgent then I would test it on Windows next week.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [January 22, 2020, 1:14am UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888/5 "2020-01-22T01:14:12Z")

</div>

Andras, that sounds good, thank you!

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [February 4, 2020, 4:26pm UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888/6 "2020-02-04T16:26:49Z")

</div>

Any updates on this topic and the corresponding PR? Anything else I can do to expedite this?

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [February 11, 2020, 1:38pm UTC](https://discourse.slicer.org/t/updating-dcmtk-to-3-6-5/9888/7 "2020-02-11T13:38:17Z")

</div>

Thank you @lassoan for testing on Windows and merging! 👍