Hello Sebastian,
I write you as the author of Orthanc [1] that you mentioned in your question.
> > What I would like to do: [typical imaging workflow]
>
> This can indeed be covered by Open Source tools. One well-known Open
> Source DICOM toolkit is DCMTK which is developed in Germany. [...]
>
Hello Karsten,
> > I have got two questions regarding this plugin:
> >
> > 1) Are you planning to provide something like this (pseudocode):
> >
> > curl PUT
> > SERVER:worklist/WORLIST_NAME/worklist_file?data=data_of_worklist_file.wl
> >
> > That way, external software (like GNUmed)
> When the ModalityWorkList plugin is loaded the Orthanc server
> gains the following capabilities:
>
> - watch a given path for files (which represent worklist entries in
> DICOM
> format)
> - when queried appropriately, return answers based on those files
>
> Is that correct
> > Yes. The only problem would be to remove the worklist once
> > the device has uploaded its acquisition to Orthanc
>
> How does that happen _now_ with the current ModalityWorkList
> plugin ? (without regard to anything I said would be useful
> from a GNUmed point of view)
The current plugin wi
Hi,
> first of all: I don't expect you to work on all this, much
> less _now_.
>
> I am mainly asking to further my own understanding and to
> assess what I can do or what I need to find someone to do.
OK ;)
> Ah, I see. So, assuming there _would_ be two REST calls
>
> submit_wl_entry_f
> > does any of the existing plugins show how to add a REST API
> > call to Orthanc when loaded ?
>
> Ah, I see: Samples/Basic/...
> :-)
Yes, and you can also check the following official plugins to have more
complete sample code:
http://www.orthanc-server.com/static.php?page=web-viewer
http://w
Dear all,
I am back from vacations.
I have just committed the fix for bug #818512 in the "orthanc" package ("FTBFS:
Please install libdcmtk*-dev") [1]. Some Lintian issues have been fixed as well.
The new version of the package "1.0.0+dfsg-2" is ready [2]. Andreas, would it
be possible for you
> > Indeed, I am currently running all my integration tests to be sure that
> > everything is OK.
>
> Hmmm, why not adding these tests as autopkgtest?
Actually, running these integration tests requires a network connection and a
Docker infrastructure. They are much more involved than the unit te
Dear Andreas,
> > >For me the move is not urgent if the issue above is no real problem for
> > >you.
> >
> > OK, so I propose to move the package to Git.
>
> Done.[1]
> [1] https://anonscm.debian.org/git/debian-med/orthanc-imagej.git
Great, thanks!
Regards,
Sébastien-
Thanks for all!
Sébastien-
> On Tue, Jun 28, 2016 at 04:32:39PM +0200, Sebastien Jodogne wrote:
> > In complement to yesterday's update of the main "orthanc" package, I have
> > just updated two of its companion plugins:
> >
> > - orthanc-webviewer 2.2 [1]
>
> Uploaded.
>
> > - orthanc-dicomw
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
Dear all,
I have a problem understanding what is going wrong in the attached bug
report.
If I open the "debian/control" file of the "orthanc" package, I indeed see
that the package Build-Depends on "libssl-dev":
https://anonscm.debian.org/cgit/debian-med/orthanc.git/tree/debian/control
However,
hanc-wsi_0.1+dfsg-1.html
Sébastien-
On Sat, Nov 19, 2016 at 10:30 AM, Sébastien Jodogne
wrote:
> Dear all,
>
> I have a problem understanding what is going wrong in the attached bug
> report.
>
> If I open the "debian/control" file of the "orthanc" package
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
Dear all,
I have just packaged the newest upstream version of Orthanc (1.2.0):
http://anonscm.debian.org/cgit/debian-med/orthanc.git/
Andreas, please could you sponsor the upload? Thanks in advance!
Regards,
Sébastien-
--
Sébastien Jodogne
Mail: s.jodo...@gmail.com
Web: http
n,
On Tue, Dec 13, 2016 at 09:21:01PM +0100, Sébastien Jodogne wrote:
> I have just packaged the newest upstream version of Orthanc (1.2.0):
> http://anonscm.debian.org/cgit/debian-med/orthanc.git/
>
> Andreas, please could you sponsor the upload? Thanks in advance!
Do you plan to prov
/trunk/packages/orthanc-wsi/trunk/
--
Sébastien Jodogne, PhD.
Medical Imaging Engineer
Department of Medical Physics
BAT. T1-3 RADIOTHERAPIE
C.H.U. - SART TILMAN - B35
4000 Liège
BELGIUM
Mail: s.jodo...@gmail.com
Web: http://www.montefiore.ulg.ac.be/~jodogne/
he changes? Many thanks in advance!
Warm Regards,
Sébastien-
On 29/12/16 12:54, Andreas Tille wrote:
Hi Sébastien,
On Thu, Dec 29, 2016 at 10:53:41AM +0100, Sébastien Jodogne wrote:
As this package is the first free and open-source, reference implementation
of DICOM for microscopic whole-sli
Thanks for the so fast upload, Andreas! :)
Could you please suggest task(s) inside the Debian Med scope[1]
where the package fits into?
HIS
IMAGING
LAB
ONCO
PRACTICE
Karsten
I agree with Karsten's selection.
Sébastien-
Dear Andreas,
Subsequently to two bug reports introduced by Tiago [1,2], I've just
updated the "orthanc-dicomweb" [3] and "orthanc-dicomweb" [4] packages.
Would it be possible for you to sponsor the upload?
Dear Tiago,
Thank you much for the fixes!
Regards,
Sébastien-
[1] https://bugs.
Hi Andreas,
Would it be possible for you to sponsor the upload?
Done.
Thanks!
BTW, I'd recommend considering becoming a Debian Maintainer to
enable you uploading yourself. :-)
Yes, I'm still looking for some Debian developer who could sign my key
after meeting me IRL somewhere in Wallon
Dear Andreas,
Now that I'm qualified as a new DM [1], I have tried to submit a fix to
Debian bug #865606 by myself [2]. Unfortunately, my fix has just been
rejected as I'm apparently not allowed to upload to the "orthanc"
package [3].
Please would you kindly explain what I should do now?
TIA!
Sé
Hi,
>> Now that I'm qualified as a new DM [1]
>
> Ahhh, congratulations!
:)
> DMs need to be explicitly granted permissions per package. Simply send
> me your fingerprint and I'll grant you permissions for uploading all
> orthan* packages.
Great! Here is my fingerprint:
93BE 9F19 7ED5 D0C3
> Permissions granted for orthanc orthanc-dicomweb orthanc-imagej
> orthanc-postgresql orthanc-webviewer orthanc-wsi - just let me
> know if you intend to upload other packages. Its perfectly fine
> to do so for fixing bugs or even taking over the maintenance.
>
> Happy to see you gaining more fr
Med contributors would be interested to give
a talk in such a devroom. Please could you express your interest?
Regards,
Sébastien-
[1] https://fosdem.org/2018/
[2] http://slayoo.github.io/fosdem2013/
--
Sébastien Jodogne
Mail: s.jodo...@gmail.com
Web: http://www.sjodogne.be/
Twitter: https://twitter.com/sjodogne
Dear Andreas and Cedric,
First of all, thanks to both of you for your interest and for your answers!
Unfortunately, only two persons showed an interest in showcasing some
free software in such a FOSDEM devroom. Furthermore, as I sadly don't
work for an University, my full-time daily job doesn't a
Dear all,
The Debian packages for Orthanc and its associated plugins pay attention
to the fact of *not* setting "-DCMAKE_BUILD_TYPE=Release", as requested
by the Debian policy [1].
However, the source code of the upstream Orthanc project makes many
calls to the "assert()" function of the sta
Dear Debian mentors,
I write this message as the maintainer of the Debian packages of the
Orthanc project [1].
The Debian packages for Orthanc and its associated plugins pay attention
to the fact of *not* setting "-DCMAKE_BUILD_TYPE=Release", as requested
by the Debian policy [2].
However,
Hello,
Have you tried RelWithDebInfo as the build type?
(https://cmake.org/Wiki/CMake_Useful_Variables)
This should set NDEBUG but still use -g to get debug symbols.
Thanks for the reply. However, previous discussions on Debian clearly
state that CMAKE_BUILD_TYPE must be set to None, not to
Dear Gert,
On 26/04/18 09:47, Gert Wollny wrote:
Am Mittwoch, den 25.04.2018, 12:32 +0200 schrieb Sébastien Jodogne:
cmake -DCMAKE_C_FLAGS=-DNDEBUG -DCMAKE_CXX_FLAGS=-DNDEBUG [...]
Please someone could validate this approach? TIA!
Add this at the top of d/rules:
export
Hello,
I am in the process of packaging a new set of plugins in order to bring
MySQL/MariaDB support to Orthanc [1]. An ITP has just been filled [2].
Please could someone indicate me how I can bootstrap a new GitHub
repository dedicated to this new "orthanc-mysql" package? TIA!
Kind Regards
Hi Andreas,
On 17/07/18 21:03, Andreas Tille wrote:
You have now permissions to do so yourself. I repeat my recommendation
to use inject-into-salsa-git as described here:
Great! Many thanks for your quick answer!
I'll dig into the "inject-into-salsa-git" procedure asap.
Sébastien-
Hi Andreas,
Please could someone indicate me how I can bootstrap a new GitHub repository
dedicated to this new "orthanc-mysql" package? TIA!
You have now permissions to do so yourself. I repeat my recommendation
to use inject-into-salsa-git as described here:
https://lists.debian.org/de
Hi,
Would it be possible for you to sponsor this new package?
Uploaded. BTW, **I** **personally** do not require you to do the extra
step on mentors.d.n. I do not visit this site but just sponsor from our
Git repository.
Perfect! Duly noted.
Thanks again,
Sébastien-
Hello,
I have received the following message after trying and uploading a new
release of the "orthanc-mysql" package.
Please could someone allow me to do the upload by myself? Thanks in advance!
Regards,
Sébastien-
Forwarded Message
Subject: orthanc-mysql_1.1-1_amd64.cha
Dear all,
I take the liberty of informing you that we're organizing a conference
about free software for healthcare and social medicine in Liège
(Belgium), on December 13-15, 2019.
This event is a joint organization between IWEEE/GNUHealthCon 2019, the
yearly meetings of the GNU Health community,
Dear all,
I take the liberty of informing you that we're organizing a conference
about free software for healthcare and social medicine in Liège
(Belgium), on December 13-15, 2019.
This event is a joint organization between IWEEE/GNUHealthCon 2019, the
yearly meetings of the GNU Health community,
Dear community,
A few time ago, I posted an announcement about the organization of a
conference about free software for health informatics and medical
imaging [1]. This conference will take place in Liège (Belgium), on
December 13-15, 2019 [2].
I feel having a talk about the Debian Med proje
Dear Debian Med community,
The Orthanc project has just released a free and open-source Web viewer of
medical images that integrates smoothly as a plugin to Orthanc [1]. The Web
viewer is based upon Chris Hafey's Cornerstone [2] and Mathieu Malaterre's GDCM
[3]. I feel that this plugin might ea
> > My question is the following: What is the recommended way of
> > "patching" a configuration file
>
> Debian policy strictly forbids modifying config files of
> other packages.
Thanks for your very helpful answer!
> Other than that, would it not make sense to split the config file ?
Yes, I w
> > [1] https://code.google.com/p/orthanc-webviewer/
>
> I am delighted to see (but confused by seeing) mention of
> PostgreSQL on that site ?
Whoops! Cut&paste error :)
This has just been fixed. However, please note that official PostgreSQL support
is now also available for Orthanc [2].
I wil
> > This has just been fixed. However, please note that official
> > PostgreSQL support is now also available for Orthanc [2].
>
> Is that "instead of SQLITE" ?
Yes, the PostgreSQL plugins fully replace the SQLite back-end.
Other plugins could be developed to override SQLite by other database ba
> This page mentions the need to --unlock the PG database under
> certain circumstances.
The locking of the database is just a feature to prevent two distinct instances
of Orthanc from using the same database. Nothing prevents 2 instances of
Orthanc from using the same PostgreSQL database, but t
Hi,
As announced on Wednesday, I have just created a Debian package for the Web
viewer of medical images that is based upon Orthanc [1]. The corresponding ITP
has #779325.
The code of the package is now available on the Debian Med repository [2]. It
can be built from pbduiler, provided that th
> À: debian-med@lists.debian.org
> Envoyé: Mercredi 25 Février 2015 22:18:15
> Objet: Re: Packaging of a Web viewer of medical images
>
> On Wed, Feb 25, 2015 at 04:32:17PM +0100, Sébastien Jodogne wrote:
>
> > please note that official PostgreSQL support is now also availab
Hi Andreas,
> That's OK.
Thanks for checking this!
> However, I have two remarks.
> I wonder if its really necessary to ship whole ZIP archives
> of
> not yet packaged JS libs. If I where you I would only ship the
> sources
> (= not minimised) and minimize + install them in d/rules.
As sugg
Hi,
It's me again :)
I have just created and committed a Debian package for the official plugin that
replaces the default SQLite database of Orthanc, by a PostgreSQL back-end [1].
This package turns Orthanc into a scalable vendor neutral archive for DICOM
images.
Could someone have a look at
> I have just created and committed a Debian package for the official
> plugin that replaces the default SQLite database of Orthanc, by a
> PostgreSQL back-end [1]. This package turns Orthanc into a scalable
> vendor neutral archive for DICOM images.
I have just thought about a possible problem wi
> Delightedly I have noted that PG can be used to store both of
> index _and_ the actual DICOM instances (?).
Yes, you're right: Enabling the "libOrthancPostgreSQLStorage.so" will store the
DICOM instances into PostgreSQL (and not on the filesystem).
> If so, I'd be interested to know which way
> > Orthanc will crash if it started after PostgreSQL.
>
> (you probably mean that the other way round ?)
Yes, of course :)
> Orthanc should gracefully fail if it cannot connect to
> PostgreSQL, rather than crash (but I cannot imagine you don't
> already do it that way).
Well, indeed, Orthanc
Hi again,
> I would provide the following packages:
>
> orthanc
> main binary and general infrastructure
> all the non-backend stuff
> orthanc-sqlite
> nearly empty package (?)
> only providing orthanc.init without postgresql
>
Hi Andreas,
> I'll upload as is since I think the package is fine.
>
> Thanks for your work on this
>
> Andreas.
Thanks for uploading it!
However, I have just noticed that the package is uploaded to unstable, but it
depends on orthanc >= 0.8.6 that is currently only available in experime
> You are perfectly right - this was a mistake of mine. However, I
> think
> we'll leave it as is to not fiddle around with the new queue and
> generate extra noise there. I think we can deal with it once it is
> accepted and perhaps upload the orthanc which is current at the time
> of acceptance
Hi,
> I would provide the following packages:
>
> orthanc
> main binary and general infrastructure
> all the non-backend stuff
> orthanc-sqlite
> nearly empty package (?)
> only providing orthanc.init without postgresql
>
Hi Karsten,
> > By moving orthanc.init into the newly created
> > orthanc-sqlite package, I had to move "debian/orthanc.init"
> > to "debian/orthanc-sqlite.init". In turn, after
> > installation, this renames "/etc/init.d/orthanc.init" as
> > "/etc/init.d/orthanc-sqlite.init".
>
> Whoa, really, w
> Sure, that's quite clear.
:)
> I was rather wondering what forced
> you to
>
> >>> move "debian/orthanc.init" to "debian/orthanc-sqlite.init"
>
> ? Is this Debian policy ? Did lintian tell you to do so ?
> (if so this sounds like an override is needed on that)
If I keep "debian/orthanc.in
> > move "debian/orthanc.init" to "debian/orthanc-sqlite.init"
>
> I had only a very quick look on your conversation but I'm not
> aware about the rule you are talking about and I'm aware of
> at least two counter examples:
>
> $ dpkg -S /etc/init.d/networking
> ifupdown: /etc/init.d/networking
>
> > I would provide the following packages:
> >
> > orthanc
> > main binary and general infrastructure
> > all the non-backend stuff
> > orthanc-sqlite
> > nearly empty package (?)
> > only providing orthanc.init without postgresql
> >
Once again, thanks for all your explanations!
> It would likely work for making orthanc only weakly depend on
> PG running. However, it would not guarantuee that PG is
> running when orthanc is configured to use PG.
I am unsure to understand the second part of this paragraph: Does
"Should-Start"
> The only way to usefully communicate that state is ...
>
> > If Orthanc is configured for PG but PG is not started,
> > Orthanc will stop, will *not* fallback to sqlite [, ...]
>
> ... and will loudly and clearly complain:
>
> you have configured Orthanc to connect to PG with
> $PG
> > I am unsure to understand the second part of this
> > paragraph: Does "Should-Start" only mean that when the
> > Orthanc service starts, PostgreSQL is guaranteed to start
> > during the boot process
>
> No. To my understanding it means that the boot process will
> attempt to start PG but not r
> > OK, I will thus introduce "Should-Start: postgresql" in the
> > "orthanc.init" published by the "orthanc" package. This will
> > not hurt, even if "orthanc-postgresql" is not installed.
>
> But it might hurt if PG is installed locally but Orthanc is
> configured to conenct to a remote PG. In
Hi all,
I have finally managed to package orthanc-postgresql, following all the
recommendations from Karsten and Andreas.
Everything is now committed (with lintian and pbuilder both succeeding):
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc/trunk/debian/
http://anonscm.debia
> > Everything is now committed (with lintian and pbuilder both
> > succeeding):
> > http://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc/trunk/debian/
> > http://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc/trunk/debian-postgresql/
>
> That latter URL 404's on me ATM.
> > I have not modified the "orthanc-postgresql" d/changelog, as it
> > seems that the package has not been pushed in the NEW queue yet, so
> > that this improvement to the documentation will still be part of
> > the
> > initial release "1.0-1".
>
> That's correct. I did not understand that your
Hi Yves,
> Same problem as above. Feel free to have a look into any random
> debian/changelog file. You'll find a plenty of them in
> /usr/share/doc/*
> since every package comes with the debian changelog.
Obviously, you can have a look at the 2 Orthanc plugins that have already been
packaged
> I pushed the control file with the cmake dependency.
> From what I see, Orthanc source files are not included in any
> package.
The Orthanc SDK is provided by the liborthancclient-dev package, or by
orthanc-dev starting with orthanc_0.8.6+dfsg-2 (the latter is still pending in
the NEW queue).
> Just that I can't find the OrthancCPlugin.h . The apt-file does not
> list it in any package and after installing liborthancclient-dev it
> is not in the /usr/include/orthanc.
It is well present in the current Sid package:
https://packages.debian.org/sid/amd64/liborthancclient-dev/filelist
If y
> For javascript, it seems that I either need to include debian
> packaged ones (like jquery) or provide the sources. From what I get
> that was done in the orthanc-webviewer, by javascript sources, it is
> meant non minified code? Is that correct?
Non-minified JavaScript code is indeed necessary,
Hi Karsten,
> > > Anything I can do to speed up its appearance in Debian ?
> >
> > If there is some urgent need we might ping ftpmaster for this old
> > package which should deserve a faster processing.
>
> Not really technically justifiably. I'm just eager to get my
> hands on it.
In the meant
Dear all,
I have just updated the DebianMed repository with the newest upstream version
of Orthanc (0.9.0) [1], that notably features a Web-based Query/Retrieve client
[2].
As Andreas is currently unavailable [3], please could someone else kindly
validate and sponsor the package, then upload i
Hello,
Please could someone sponsor the Orthanc 0.9.0 package?
TIA,
Sébastien-
- Mail original -
> De: "Sébastien Jodogne"
> À: debian-med@lists.debian.org
> Envoyé: Jeudi 4 Juin 2015 10:59:52
> Objet: Orthanc 0.9.0
>
> Dear all,
>
> I have jus
Hello,
I write this mail as a consequence of Debian bugs #790514 ("orthanc-dev: fails
to upgrade") [1] and #790517 ("orthanc-doc: fails to upgrade") [2]. I am unsure
of the action to be taken with respect to the Debian policy 7.6 [3].
The problem stems from the refactoring of the Orthanc packag
Hello,
Thanks for the feedback! The fix is now committed:
http://anonscm.debian.org/viewvc/debian-med?view=revision&revision=19448
Regards,
Sébastien-
> On Tue, Jun 30, 2015 at 10:19:08AM +0200, Sébastien Jodogne wrote:
> > =
> > Package: orthanc-doc
>
Hi Karsten,
Indeed, orthanc-postgresql is not yet available.
The problem is that orthanc-postgresql depends on Orthanc >= 0.8.6, so we could
not submit it before a new version of Orthanc was accepted into Debian (the
latest available version was orthanc-0.8.4+dfsg-2).
It is only now that orth
Dear all,
I have just updated the DebianMed repository with the newest upstream version
of Orthanc (0.9.1) [1].
Andreas, if the package looks OK to you, please would you kindly upload it?
Thanks in advance!
Sébastien-
[1]
http://anonscm.debian.org/viewvc/debian-med?view=revision&sortby=date&
evision=19484
> On Thu, Jul 02, 2015 at 10:28:18PM +0200, Sébastien Jodogne wrote:
> > I have just updated the DebianMed repository with the newest upstream
> > version of Orthanc (0.9.1) [1].
> >
> > Andreas, if the package looks OK to you, please would you kindly uplo
> I think it does not matter much as long as I will upload quickly
> after orthanc-postgresql will be accepted. Not requesting rejection
> by ftpmaster now will create less noise / work for them so I'll leave
> it as is.
Fine!
> > Please also note that I plan to prepare a new version of the
> >
Hi Andreas,
> > I have just updated orthanc-postgresql [1], with a newer upstream version
> > (1.1) that depends on Orthanc >= 0.9.1. I am unsure of whether it is
> > possible to cancel the upload of orthanc-postgresql_1.0 to replace it by
> > orthanc-postgresql_1.1, or if we should wait for ortha
Dear all,
I am currently packaging a new plugin to bring DICOMweb support to Orthanc [1].
When I build the plugin from upstream inside Debian sid, I get the following
error:
=
Linking CXX shared library libOrthancDicomWeb.so
CMakeFiles/OrthancDicomWeb.dir/Plugin/Dicom.cpp.o: In function
`O
> > As a consequence, I would like to know when updated versions of the
> > libgdcm2.4 and libgdcm2-dev packages built with gcc-5 will be available in
> > the repositories. Is this information available somewhere?
>
> If you read the Debian Med mailing list you might have noticed Steve's
> status
> It was only incidentally related, in that GDCM build-depends on gccxml, which
> I'm trying to replace by a wrapper around castxml. I was doing so because of
> things like the above-mentioned bugs.
OK, thanks for clarifying this :)
> I didn't try, but I was under the impression that gdcm does n
Hi,
> > > I will try hard to get the script into VCS tonight and then I will
> > > welcome
> > > help in testing the builds on dependent packages.
> >
> > Great! Let me know when things are ready.
>
> OK. The gccxml package is updated with a wrapper around castxml (the real
> binary is renamed
> Fine! With your updated version of gccxml, I was able to fix several build
> errors in the gdcm package. I had to apply one patch [1].
>
> Unfortunately, there are still build errors related to mummy that read as
> follow: [...]
Pursuing my investigations, I have just noticed that the argument
Hi Andreas,
Hi Steve,
> > As a consequence, I would like to know when updated versions of the
> > libgdcm2.4 and libgdcm2-dev packages built with gcc-5 will be available in
> > the repositories. Is this information available somewhere?
>
> If you read the Debian Med mailing list you might have no
Hi,
> But it also points out the way to simply replace gccxml by castxml. So I
> updated your patch to do that.
Yes, this is much better now!
> Unfortunately, I get a build failure with gdcm: [...]
> How did you avoid the "__int128" problem? I'm building on adm64 in an up-to-
> date sid chroot
Hi Andreas,
> I can confirm that I uploaded gdcm now to unstable. Unfortunately I
> missed the last change of your e-mail address as Uploader. I hope this
> will be no problem for you.
No problem with this: I just try and centralize all the Debian-related
automated mailing in a single mailbox,
> > BTW, thanks for uploading the package!
>
> The thank goes fully to you. Just rebuilding and calling dput is not a
> big deal.
>
> BTW, do you want to get the upload feeling yourself? You are now
> maintaining several packages and have dived into the bug squashing
> business. So applying to
Dear all,
The Orthanc 0.9.3 package is now ready. This version notably removes the
dependency over google-glog.
Andreas, please would you kindly upload it? Thanks in advance!
Regards,
Sébastien-
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". T
Dear all,
Thanks to Andreas' recent upload of the "orthanc_0.9.3+dfsg-1" package and
thanks to the fix of the "gdcm" package, new versions of the plugins
"orthanc-webviewer" [1] and "orthanc-postgresql" [2] are now ready for upload.
During my vacations, Karsten made a lot of very helpful remark
Hi Yves,
> My name is Yves, I'm developing a pure javascript DICOM viewer called dwv.
> It is released under GPL and available at https://github.com/ivmartel/dwv.
> The viewer can be used on its own but also bundled in a PACS. In the case
> of the Orthanc PACS, I created a plugin called DwvExplore
Dear all,
While upgrading the orthanc package to the newest upstream version (0.9.4), I
notice that Lintian reports new "source-is-missing" errors:
==
N: Processing source package orthanc (version 0.9.4+dfsg-1, arch source) ...
E: orthanc source: source-is-missing
OrthancExplorer/libs/jquer
> > So, the files that are reported to be missing are actually present in the
> > source package.
>
> ... and this is the problem. Lintian considers these files not as
> source package since these are minimized (or lintian considers these as
> minimized). You always need to provide non-minimised
Hello Andreas,
Thanks to your answers about lintian, I think that Orthanc 0.9.4 is now ready
for upload [1].
Regards,
Sébastien-
[1]
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc/trunk/debian/
Hi,
> g++ -ggdb -O6 -DNDEBUG -I./protoobj -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -o obj-opt-x86_64/test_spectrum_preprocess.o -c
> src/test_spectrum_preprocess.cc
> In file included from src/test_spectrum_preprocess.cc:8:0:
> src/records.h: In destructor 'RecordWriter::
Hello,
In the improbable case you missed the information, please note that the FOSDEM
2016 call for participation is available [1]. The deadlines for submissions are
as follows:
- Developer rooms: October 9th.
- Main tracks: October 16th.
- Stands: November 13rd.
- Lightning talks: November 27t
Hello,
I have just updated the repositories with the latest upstream version of the
PostgreSQL plugins for Orthanc [1]. This minor release notably fixes build
problems against orthanc-dev 0.9.4.
Andreas, please would you consider this update for upload?
Thanks,
Sébastien-
[1] http://anonscm
Hi Andreas,
I have just fixed bug #804571 that was reported yesterday on Orthanc [1,2].
Would it be possible for you to upload this new version (0.9.4+dfsg-2)?
TIA,
Sébastien-
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804571
[2] http://anonscm.debian.org/viewvc/debian-med?view=revi
Dear all,
I have just updated the DebianMed repository with the newest upstream version
of Orthanc (0.9.5) [1].
Andreas, if the package looks OK to you, please would you kindly upload it?
Thanks in advance!
Cheers,
Sébastien-
[1]
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/or
Hi Andreas,
> > I have just updated the DebianMed repository with the newest upstream
> > version of Orthanc (0.9.5) [1].
>
> Uploaded.
Thanks!
> Remark: My personal policy is to migrate those packages that are using
> orig.tar.?z archives which are not byte identical with what is
> downloaded
1 - 100 of 159 matches
Mail list logo
