Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

Dear Emmanuele and Mathieu, On 3/19/24 08:51, Mathieu Malaterre wrote: On Tue, Mar 19, 2024 at 8:44 AM Emanuele Rocca wrote: Hi, On 2024-03-19 06:24, Sébastien Jodogne wrote: Because of bug #1060104, a large majority of the packages related to medical imaging have just disappeared from

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

Dear all, Because of bug #1060104, a large majority of the packages related to medical imaging have just disappeared from Debian Unstable. But, if I correctly understand #1060104, it is specific to one single platform (armel). My question is: Rather than penalizing all platforms (including

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

Dear all, Because of bug #1060104, a large majority of the packages related to medical imaging have just disappeared from Debian Unstable. But, if I correctly understand #1060104, it is specific to one single platform (armel). My question is: Rather than penalizing all platforms (including

Bug#1062404: [Debian-med-packaging] Bug#1062404: orthanc-python: flaky autopkgtest: Test failed with

Hello, Even if I'm tagged as the maintainer of "orthanc-python", I don't know how autopkgtest/flaky works (I haven't implemented such tests by myself). I consequently forward your message to the Debian Med mailing list, as I cannot help on this bug by myself. Regards, Sébastien- > I looked at

Bug#1054914: orthanc-dicomweb: An unknown command in CMakeLists.txt encountered while attempting to build the orthanc-dicomweb_1.15 package.

error with latest upstream > version[1]. I really hope Sebastian can clarify this. > > Kind regards > Andreas. > > > [1] https://salsa.debian.org/med-team/orthanc-dicomweb/-/jobs/4867398#L2591 > > -- > http://fam-tille.de -- Sébastien Jodogne Web: https://www.info.ucl.ac.be/~sjodogne/ Twitter: https://twitter.com/sjodogne

Bug#1041813: orthanc: test failing on s390x

Dear Étienne, Thanks for your investigation! I confirm that you have found the proper way of fixing this issue. I have just committed an adapted patch in the upstream project, which provides better compatibility with non-GNU/Linux environments:

Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1

and GNU Health... sorry for the delay, I got feedback yesterday that required a rework for this application. Cheers, Sébastien- -- Sébastien Jodogne Mail: s.jodo...@orthanc-labs.com Web: http://www.orthanc-labs.com/ Twitter: https://twitter.com/sjodogne

Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1

Dear Étienne and Nilesh, On 24/11/22 17:25, Étienne Mollier wrote: Control: tags -1 - patch Hi Nilesh, Nilesh Patra, on 2022-11-24: On Fri, 18 Nov 2022 22:48:42 +0100 =?utf-8?Q?=C3=89tienne?= Mollier wrote: orthanc-dicomweb is currently affected by a failure to build from source

Bug#1015234: RM: orthanc-dicomweb [armel] -- RoM; transient dependency issue

Package: ftp.debian.org Severity: normal The explanation for this removal request is detailed in Bug#1015187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015187

Bug#1000222: [Debian-med-packaging] Bug#1000222: orthanc force gnuc++11 reason

Dear Mathieu, I confirm that this is an acceptable patch, except that it could be applied only to "JsonCppConfiguration.cmake" (the "DownloadOrthancFramework.cmake" is part of the skeleton that is copied in each Orthanc official plugin). It was on my plan to do this patch by myself, once I

Bug#989128: [Debian-med-packaging] Bug#989128: package statically links without using a Built-Using attribute

This issue has been escalated on the Debian Med mailing list: https://lists.debian.org/debian-med/2021/06/msg00014.html

Bug#989126: [Debian-med-packaging] Bug#989126: package statically links without using a Built-Using attribute

This issue has been escalated on the Debian Med mailing list: https://lists.debian.org/debian-med/2021/06/msg00014.html

Bug#989127: [Debian-med-packaging] Bug#989127: package statically links without using a Built-Using attribute

This issue has been escalated on the Debian Med mailing list: https://lists.debian.org/debian-med/2021/06/msg00014.html

Bug#981753: [Debian-med-packaging] Bug#981753: COPY cannot find "/usr/share/nodejs/axios/dist/axios.min.js"

Hello Mathieu, This issue comes from the fact that many JavaScript packages have recently changed their installation paths. I guess that your issue can be fixed by reverting the following changeset:

Bug#975069: [Pkg-javascript-devel] Bug#975069: emscripten: Incompatibilities with LLVM 11

> That log was using the experimental package and local config, right? > It would be helpful if you could share how far you got using the package > in unstable instead, and no custom config. I.e. using llvm-11. No, this log was generated using only the packages from unstable, simply by running

Bug#975069: [Pkg-javascript-devel] Bug#975069: emscripten: Incompatibilities with LLVM 11

> Thanks for your bugreport - and for being the first known user of the > emscripten package in Debian (besides my own use of it for the olm > package). This is really nice to see other work on WebAssembly in Debian! :-) I think there will be other topics to be discussed, notably how to properly

Bug#973612: [Debian-med-packaging] Bug#973612: I'm afrait I did some kind of sabotage by upgrading civetweb ... [karsten.hilb...@gmx.net: Bug#973612: orthanc: libcivetweb version mismatch]

hem if someone else meets a similar problem in another context. Best Regards, Sébastien- [1] https://salsa.debian.org/med-team/civetweb/-/commit/ccb62139b6139ea6efc2432c12018de6e3c16003 On 3/11/20 14:11, Andreas Tille wrote: > [including the list again] > Hi Sébastien, > > On Mon, Nov 02, 2020

Bug#966655: Orthanc and all its plugins are getting removed from testing

As suggested by Andreas, I've been in touch with the FTP team. Following this discussion, I've uploaded orthanc-1.7.2+dfsg-3 to unstable, that doesn't contain the NEW changes. For reference, here are the two changesets to revert once "liborthancframework-dev" and "liborthancframework1"

Bug#966655: Orthanc and all its plugins are getting removed from testing

Dear all, Because of the bug #966655 [1], and because of the fact that orthanc-1.7.2+dfsg-2 is pending in the NEW queue [2], I cannot commit the fix regarding the missing build dependency on tzdata until the NEW packages get accepted. But, as #966655 is tagged as serious, the entire Orthanc

Bug#966655: [Debian-med-packaging] Bug#966655: orthanc: using tzdata but missing dependency on it?

Hello, Thanks for your report. Unfortunately, as long as orthanc-1.7.2+dfsg-2 is pending in the NEW queue [1], no further patch can be applied. Kind Regards, Sébastien- [1] https://ftp-master.debian.org/new.html On 1/08/20 11:08, Gianfranco Costamagna wrote: > Source: orthanc > Version:

Bug#960639: Bug#960639: src:orthanc-imagej: Please add support to build against libjson-simple-java >= 3

Dear Gilles, I finally managed to find a few hours to finalize your patch. I had to extend it a bit so for it to work correctly [1]. Version "1.2+dfsg-2" of the package has just been uploaded accordingly. > It's not a problem doing the upload. this is the easy part :) > What I'm uncomfortable

Bug#960639: [Debian-med-packaging] Bug#960639: src:orthanc-imagej: Please add support to build against libjson-simple-java >= 3

_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > > > ___ > Debian-med-packaging mailing list &

Bug#959473: orthanc-dicomweb build-dependencies unsatisfiable on armel

Thanks for your in-depth analysis! As this problem is way too involved given my understanding of the Debian package management process, I have followed the simple path you provided by requesting the removal of the armel binaries of orthanc-dicomweb:

Bug#959776: RM: orthanc-dicomweb [armel] -- RoM; transient dependency issue

Package: ftp.debian.org Severity: normal The explanation for this removal request is detailed in Bug#959473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959473

Bug#829380: [Debian-med-packaging] Bug#829380: Orthanc 1.2.0

Sébastien- On 8/04/20 10:34, Karsten Hilbert wrote: > On Wed, Apr 08, 2020 at 07:50:06AM +0200, Sébastien Jodogne wrote: > >> Sorry for having overlooked this issue. >> >> I have migrated Karsten's instructions into the "README.Debian" file of >> the "

Bug#829380: Orthanc 1.2.0

arsten Hilbert wrote: > On Mon, Apr 06, 2020 at 01:43:57PM -0700, tony mancill wrote: > >> On Fri, Dec 30, 2016 at 12:15:45PM +0100, Karsten Hilbert wrote: >>> On Fri, Dec 30, 2016 at 10:57:56AM +0100, Sébastien Jodogne wrote: >>> >>>> Sorry,

Bug#956088: RM: orthanc-python [s390x] -- RoM; ANAIS

Package: ftp.debian.org Severity: normal The "orthanc" package for s390x was removed, because of issue #954317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954317 As this package depends on "orthanc", it must also be removed.

Bug#955495: ITP: orthanc-python -- Develop plugins for Orthanc using the Python programming language

y "orthanc-python". Regards, Sébastien- On 3/04/20 11:07, Andreas Tille wrote: > Hi Sébastien, > > I'm extremely short in time but I stumbled upon this: > > On Fri, Apr 03, 2020 at 08:39:12AM +0200, Sébastien Jodogne wrote: >> That being said, I have changed

Bug#955495: ITP: orthanc-python -- Develop plugins for Orthanc using the Python programming language

Dear Alex, Thanks so much for your careful review of the package! According to your message, I have applied several fixes to it: https://salsa.debian.org/med-team/orthanc-python/-/commits/master if this is a python module then it should follow python guidelines. The name in this case should

Bug#955032: RM: orthanc-dicomweb [s390x] -- RoM; ANAIS

Package: ftp.debian.org Severity: normal The "orthanc" package for s390x was removed, because of issue #954317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954317 As this package depends on "orthanc", it must also be removed.

Bug#955034: RM: orthanc-postgresql [s390x] -- RoM; ANAIS

Package: ftp.debian.org Severity: normal The "orthanc" package for s390x was removed, because of issue #954317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954317 As this package depends on "orthanc", it must also be removed.

Bug#955033: RM: orthanc-mysql [s390x] -- RoM; ANAIS

Package: ftp.debian.org Severity: normal The "orthanc" package for s390x was removed, because of issue #954317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954317 As this package depends on "orthanc", it must also be removed.

Bug#955035: RM: orthanc-webviewer [s390x] -- RoM; ANAIS

Package: ftp.debian.org Severity: normal The "orthanc" package for s390x was removed, because of issue #954317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954317 As this package depends on "orthanc", it must also be removed.

Bug#954317: RM: orthanc [s390x] -- RoM; ANAIS

Package: ftp.debian.org Severity: normal One unit test fails on s390x architecture: https://buildd.debian.org/status/fetch.php?pkg=orthanc=s390x=1.6.0%2Bdfsg-1=1584552281=0 [ RUN ] ParsedDicomFile.ToJsonFlags2 /<>/UnitTestsSources/FromDcmtkTests.cpp:732: Failure Expected equality of these

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

Dear Ivo, Please could you indicate where I can find information about how to remove the old armel build? some info is here: https://wiki.debian.org/ftpmaster_Removals Note that you can close this bug once the removal is done (otherwise this bug would prevent migration to testing).

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

et/cgi-bin/mailman/listinfo/debian-med-packaging -- Sébastien Jodogne Mail: s.jodo...@orthanc-labs.com Web: http://www.orthanc-labs.com/ Twitter: https://twitter.com/sjodogne Be part of OrthancCon 2019! http://conference.orthanc-server.com/

Bug#919742: [Debian-med-packaging] Bug#919742: orthanc-wsi FTBFS 'class GlobalDcmDataDictionary' has no member named 'unlock'

__ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-p > ackaging -- Sébastien Jodogne Mail: s.jodo...@orthanc-labs.com Web: http://www.orthanc-labs.com/ Twitter: https://twitter.com/sjodogne

Bug#919193: [Debian-med-packaging] Bug#919193: orthanc: FTBFS with dcmtk-3.6.4

Hello, Thanks for the report! This is now fixed in the upstream mainline by the two following changesets: https://bitbucket.org/sjodogne/orthanc/commits/c8b75e207a82179a3f99a8bc 60b43626f8f3c34b https://bitbucket.org/sjodogne/orthanc/commits/8849677c2cbcf0b5ac990e83 8c72ace6453b059b Orthanc

Bug#829380: Orthanc 1.2.0

Hello, No: If the "--upgrade" command-line option is provided, the Orthanc server will never start. If no upgrade is required, this is a void operation that returns immediately. I would have thought so. However, why does this script: [...] producing the following log ? [...]

Bug#829380: Orthanc 1.2.0

Dear Karsten, Sorry for the delay. may I ask for confirmation of the following behaviour: If Orthanc is manually started for a DB upgrade (say, on Debian:) /usr/sbin/Orthanc --upgrade --trace /etc/orthanc/ BUT the database is already at the required version THEN Orthanc

Bug#844835: orthanc: FTBFS: build-dependency not installable: libssl-dev

Dear Gert, orthnac build depends on libdcmtk-dev, and this pulls in libssl1.0-dev (since dcmtk (a) does not yet support openssl-1.1 and (b) it is used by programs that require QT which conflicts with openssl-1.1). libssl1.0-dev conflicts with libssl-dev, and hence the build failure. The

Bug#839309: orthanc-postgresql 2.0-3

Hello, I have just updated the orthanc-postgresql package: https://anonscm.debian.org/viewvc/debian-med?view=revision=22821 This new version of the package solves the severe FTBFS Bug#839309 (orthanc-postgresql: Could NOT find PostgreSQL). In the absence of Andreas, please someone could

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

> - I would not have guessed that adding --upgrade might have made > a difference to a failure that tells me "stack smashing detected" > at the console :-) Just to be sure: Is your issue an immediate crash with "stack smashing detected", or is your issue a failure while executing the

Bug#818757: Bug#818757: orthanc-postgresql: does not start

Hello, > On Sun, Mar 20, 2016 at 06:09:15PM +0100, Karsten Hilbert wrote: > > > > > > Have you added the "--upgrade" option so that Orthanc would automatically > > > upgrade the database schema? > > I wonder whether this should be done in a postinst script. > > > Also, would Debian benefit

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

Hello, I have spent a couple of hours trying to reproduce this issue, but I was unable to do so. Here are the tests I made: * Upgrade from Orthanc 0.9.4 + PosgreSQL plugins 1.3 (database schema v5), to Orthanc mainline + PostgreSQL plugins 2.0 (database schema v6). * Upgrade from Orthanc

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

Hello, > > Is there anything else I can provide to get this bug looked at ? > > Even if I risk to be a pain in the behind - since this > package is of such importance to responsible Medical Care > I allow myself to re-inquire about the state of this bug. Unfortunately, this item is low-priority

Bug#821135: imagej: Crash running imagej

gt; LC_MONETARY = "fr_BE.UTF-8", > LC_ADDRESS = "fr_BE.UTF-8", > LC_TELEPHONE = "fr_BE.UTF-8", > LC_NAME = "fr_BE.UTF-8", > LC_MEASUREMENT = "fr_BE.UTF-8", > LC_IDENTIFICATION = "fr_BE.UT

Bug#821011: orthanc: FTBFS on powerpc/ppc64el: error: #error Support your plateform here

> > The problem is visibly that the macro "__linux" is not defined > > anymore as it used to be, maybe because of an update of gcc. > > umh, isn't this the jurisdiction of glibc, rather than gcc? *shrugs* You're of course right :) > > Reading the new version of the "Pre-defined Compiler

Bug#821011: orthanc: FTBFS on powerpc/ppc64el: error: #error Support your plateform here

Hello Andreas, > > However, I have no access to a ppc/ppc64el computer, so I cannot check by > > myself whether the patch actually solves this Debian bug. Could someone > > help by testing the patch, or by giving me access to a test computer? > > The "lazy" solution is to upload your change and

Bug#821011: orthanc: FTBFS on powerpc/ppc64el: error: #error Support your plateform here

Hello, Thanks for reporting this issue. Here is the problematic excerpt in the code: #if defined(_WIN32) #include #elif defined(__linux) || defined(__FreeBSD_kernel__) || defined(__APPLE__) || defined(__FreeBSD__) #include #else #error Support your platform here #endif The problem is visibly

Bug#820062: orthanc and orthanc-doc: error when trying to install together

Hi Andreas, > please double check my commits whether all files end up where they > should be. The package builds nor also for arch all binary packages. > > I also fixed some other minor issues. > > Hope this helps and let me know if it should be sponsored as it is > now. I am extremely

Bug#820062: orthanc and orthanc-doc: error when trying to install together

Dear Andreas, > > I am really sorry, but despite hours of work and readings, I am still > > totally unable to reproduce (and thus fix) this bug by myself. > > [...] > > Try > > pdebuild [pbuilder options] -- --debbuildopts -A > > This will produce the broken package. Great! The option "-A"

Bug#820062: orthanc and orthanc-doc: error when trying to install together

Dear all, > Right. I was just wondering why this was actually happening on the buildd, > until I realised that it was a source-only upload of orthonc. > > Sebastien: you can see a log of the package build for arch=all on the > package tracker, or directly on > >

Bug#820062: [Debian-med-packaging] Bug#820062: orthanc and orthanc-doc: error when trying to install together

Hello, Thank for reporting this issue. However, I need help: I am indeed unable to reproduce it... According to your report, the file "/usr/lib/orthanc/libModalityWorklists.so.1.0.0" lies both in package "orthanc" and "orthanc-doc": >

Bug#818512: orthanc: FTBFS: Please install libdcmtk*-dev

> Call Stack (most recent call first): > > CMakeLists.txt:283 (include) > > > > > > -- Configuring incomplete, errors occurred! > > -- > Martin Michlmayr > Linux for HPE Helion, Hewlett Packard Enterprise > > -- Sébastien Jodogne Mail: s.jodo...@gmail.com Web: http://www.sjodogne.be/ Twitter: https://twitter.com/sjodogne

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

Hello Karsten, > Is there anything else I can provide to get this bug looked at ? I am back from vacations. I will look at the upgrade problem as soon as possible. As a quick hack to unblock you, I would suggest to apply the "Generic replication" procedure [1]. In your case, the procedure

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

Hello, > 4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg > 2.0) Have you added the "--upgrade" option so that Orthanc would automatically upgrade the database schema? Sébastien-

Bug#753809: ginkgocadx and certain dicom files

Dear David, Note however that, in the context of Orthanc, if the DICOM file is sent >> through the REST API, then this decoding/re-encoding chain does not take >> place (accordingly to your intuition). This would also be the case if >> DICOMweb STOW-RS is used. [...] >> > > Whether the data set

Bug#753809: ginkgocadx and certain dicom files

Orthanc will not modify the file by itself, except if the input file is corrupted, which could lead to undefined behavior. Garbage in, garbage out. Regards, Sébastien- On Sun, Jan 31, 2016 at 7:45 PM, Karsten Hilbert wrote: > On Sun, Jan 31, 2016 at 07:42:26PM +0100,

Bug#753809: ginkgocadx and certain dicom files

> > > Orthanc will not modify the file by itself, except if the input file is > > corrupted > > I hadn't been made aware of this "except" so far. This means > more testing will need to be done because eventually Orthanc > _does_ modify input files sometimes. Sigh. > Well, Orthanc does not modify

Bug#788920: [Debian-med-packaging] Bug#788920: orthanc: please make the build reproducible

Dear Maria, Thanks for your report! However, this issue is already fixed in the upstream code since February 16th, 2015 [1]. Unfortunately, I am still waiting for sponsor to review/upload the latest version of the Orthanc package [2]. I have therefore tagged your bug as closed in the

Bug#689041: RFS: orthanc/0.2.1-3 [ITP] -- Lightweight, RESTful DICOM server for healthcare and medical research

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package orthanc: * Package name: orthanc Version : 0.2.1-3 Upstream Author : Sebastien Jodogne s.jodo...@gmail.com * URL : https://code.google.com/p/orthanc/ *