Dear Etienne, > We're almost there with getting dcmtk and the Orthanc ecosystem > to migrate to trixie. The remaining issues[1] only affect > orthanc-wsi, and on a particular set of CPU architectures > (arm64, riscv64, ppc64el and s390x). > [...] > Per chance, do you have an idea what the root cause would be? > > If not, then in order to facilitate dcmtk transition, I plan to > disable affected architecture in autopkgtest control file, and > reduce the severity of the present bug to important.
I suspected an error related to big endian architectures. But, I have just manually compiled orthanc and orthanc-wsi on a qemu Debian Buster MIPS (my environment for the release process of Orthanc), and the test passes. I don't have the time to install a full qemu environment for another distribution, which will take me hours. As a consequence, unless someone can provide me with a SSH connexion to a arm64, riscv64, ppc64el, or s390x computer for interactive testing, I am unable to investigate this issue by myself. Regards, Sébastien-
