[Debian-med-packaging] Bug#753809: Aw: Re: Bug#753809: ginkgocadx: will not display studies

[Karsten Hilbert]

> > On Wed, Nov 26, 2014 at 11:40:02PM +0100, Karsten Hilbert wrote:
> >> Is there any news regarding this bug ?
> >>
> >> It is rather serious: Because of this bug Ginkgo CADx
> >> is rather useless for serious clinical care on Debian.
> >
> > I admit I feel helpless about this issue.  However, if you think that
> > this issue is serious than you should tag the bug that way to make more
> > people aware of it.  The consequence would be that ginkgocadx will not
> > be released with Jessie if it will not be fixed.  I keep upstream in CC
> > (Carlos, feel free to read the whole story here [1]).
> 
> Here is the only technical information in this bug report:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753809#15
> 
> [...]
> > We found many issues in GDCM 2.x which is provided with debian bundled ITK version.
> [...]
> AFAIR ITK/GDCM upstream has been fairly reluctant to apply patches.
> [...]
> 
> What exactly do you expect from me ? Please stop CCing me on FUDs.
> 
> I've happily applied patch for better integration of current ITK and
> GDCM see recent changelog, so stop saying things like "fairly
> reluctant", or at least include the context.
>
> As for the so-called "many issues in GDCM 2.x", please include actual
> details to reproduce them.

Mathieu, what do you expect me to do other than the following ?

1) supply a detailed explanation of how to reproduce the problem

    I did.
    Did you try to reproduce the problem ?

2) contact upstream

    I did.

3) relay upstreams response

    I did.

3) test upstream code

    I did. It worked.

4) test other software to try to isolate the problem

    I did. Aeskulap worked. So it doesn't seem to be Orthanc.

5) ping every once in a while to reconfirm the problem and ask for status

    I did.

I lack the skillset to dig into the code. Would you like me to stop
providing problem reports to the level of detail I can manage ?

For what it is worth: This problem certainly IS serious but I have
refrained from marking the report as such because I humbly accept
the possibility that the severity may somehow be constrained to my
system or setup or whatnot and that the package might work for other
people (after all, it does display some instances of studies when
loaded from CD-ROM for the first time). Hence I don't think it
warrants tagging as serious such as to facilitate exclusion from next
Debian/Stable.

Have you tried to reproduce the problem ?

If so, did you succeed or fail to reproduce it ?

If you failed to reproduce it what other information do you need ?

Karsten