[Debian-med-packaging] Bug#854837: Package dicompyler does not work

[Andreas Tille]

Hi again,

I need to admit we *really* need full system information to deal
with your bug report.

On Sat, Feb 11, 2017 at 11:09:59PM +0100, Vojtech Kulvait wrote:
> Hi,
> well in the file
> /usr/share/dicompyler/dicompyler-0.4.2.egg-info/requires.txt
> matplotlib>=0.99, <=1.1.0
> numpy>=1.2.1
> pil>=1.1.7
> pydicom>=0.9.5, <0.9.7

On my system I get:

 $ LC_ALL=C apt-cache policy dicompyler
dicompyler:
  Installed: 0.4.2-3
  Candidate: 0.4.2-3
  Version table:
 *** 0.4.2-3 501
        501 http://httpredir.debian.org/debian testing/main amd64 Packages
         50 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

$ cat /usr/share/dicompyler/dicompyler-0.4.2.egg-info/requires.txt
$ 

So the file you wrote above is in the Debian package empty (=has zero
bytes).  I'm afraid you are using something else than the Debian
packaged version.  I can confirm that the original tarball contains the
data you fixed but you most probably are lacking all the patches that
are contained in the Debian package.

> i had to edit it to be
> matplotlib>=0.99, <=1.3.1

That's definitely not needed.
 
> because otherwise python warns that the version of matplotlib is too new
> and can not run dicompyler
> 
> after this bugfix however dicompiler itself draw its widget but you can not
> import data or even open some dialogs, file import is grey. So the program
> is useless.

Whatever you have installed might be useless since upstream seems to
have orphaned this code and Debian is covering lots of patches to fix
it.  If you really install the Debian package you can report bugs about
the package but I have not idea how to fix your manual installation.

> I have to download windows version and then work on it.

Alternatively remove your installation and try

    apt-get install dicompyler

If you confirm you did so and there might be any remaining problems feel
free to report these here.  If not I probably need to close this bug
report since it does not concern the Debian package but something else
we do not control.

Hope this helps

       Andreas.

-- 
http://fam-tille.de