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

Karsten Hilbert Karsten.Hilbert at gmx.net
Wed Apr 8 09:34:03 BST 2020


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 "orthanc" package:
> https://salsa.debian.org/med-team/orthanc/-/commit/9f004236c6190a4b3137d358b8de9d0cae498f90

Thanks for that. Do note that those haven't actually been
tested while the attached script *has* been.

Any chance that script can be integrated ?

(just put it in /usr/sbin/ and add a note about it into README.Debian)

Of course, that's a wishlist item, not a request.

Best,
Karsten


> HTH,
> Sébastien-
>
>
> On 7/04/20 23:22, Karsten 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, my mistake: Preventing Orthanc from starting after an upgrade of the
> >>>> database schema was on my TODO list... it is not implemented yet. I have
> >>>> just added an issue on the upstream bug tracker to avoid forgetting it:
> >>>> https://bitbucket.org/sjodogne/orthanc/issues/29
> >>>>
> >>>> This feature will be part of forthcoming 1.2.1 release.
> >>>
> >>> Thanks a lot for confirming. I will test when 1.2.1 is out
> >>> and provide a script users can run updating the database
> >>> schema if needed.
> >>
> >> Hello Karsten,
> >>
> >> Debian stable now has version 1.5.6 [1] and the upstream bug report is
> >> marked as resolved [2].  Is a separate update script still needed?  If
> >> not, can this bug report be closed?
> >
> > A separate script is never needed because Orthanc itself can
> > upgrade it's database -- if manually invoked in the right
> > environment.
> >
> > The (attached) script makes it a lot easier for users to do
> > so and it proves (on my machine) that the surprising behaviour
> > (Orthanc being started after a run with --upgrade) is fixed.
> >
> > So, the bug can be closed, regardless of the attached script
> > -- but the attached script is useful to users whenever
> > another database upgrade comes along (which there will,
> > eventually).
> >
> > Best,
> > Karsten
> > --
> > GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B
> >

--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



More information about the Debian-med-packaging mailing list