Dear Gianfranco,
Thanks for your report. From my understanding, this issue is related
to the creation of the "dcmtk-data" package by the following changeset
in the "dcmtk" package:
https://salsa.debian.org/med-team/dcmtk/-/commit/f0f9dfaa22ad85fe8d3cee302fb6ba766f703c8e
This changeset has the eff
Hello Adrian,
> orthanc-neuro builds and links with the shared library when I remove the
> -DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF, is there any reason why this
> would not work?
This would not work, because the libOrthancFramework.so shared library
is designed to share code between the Orthanc c
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
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 the
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
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 th
ding for Orthanc 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
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#10237
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 h
This issue has been escalated on the Debian Med mailing list:
https://lists.debian.org/debian-med/2021/06/msg00014.html
This issue has been escalated on the Debian Med mailing list:
https://lists.debian.org/debian-med/2021/06/msg00014.html
This issue has been escalated on the Debian Med mailing list:
https://lists.debian.org/debian-med/2021/06/msg00014.html
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" subpac
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 ecosy
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: 1.7.2+
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:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bu
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).
Thanks
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/
t;
> ___
> 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
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 1.5.2
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 soluti
Hello,
I have just updated the orthanc-postgresql package:
https://anonscm.debian.org/viewvc/debian-med?view=revision&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 coul
> - 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 "--upgr
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 fro
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 0.9.1
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
> > 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 Macros
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 l
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
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 gratefu
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" w
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
>
> https://buildd.debian.org/status/
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":
>
/var/cache/apt/archives/orthanc-doc_1.0.0+dfsg-2_all.d
all 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
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 woul
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-
36 matches
Mail list logo
