[Debian-med-packaging] Bug#759056: dicompyler: Please update to use wxpython3.0

[Olly Betts]

Hi Andreas,

On Thu, Sep 04, 2014 at 12:26:39AM +0200, Andreas Tille wrote:
> On Sun, Aug 24, 2014 at 12:19:35PM +1200, Olly Betts wrote:
> > Source: dicompyler
> > Version: 0.4.1-1-2
> > Severity: important
> > Tags: sid jessie
> > User: freewx-maint at lists.alioth.debian.org
> > Usertags: wxpy3.0
> > Control: block 755757 by -1
> > 
> > ...
> > 
> > http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git
> > ...
> 
> I used the script I found there but if I run the patched application
> (see
> 
>   Vcs-Svn: svn://anonscm.debian.org/debian-med/trunk/packages/dicompyler/trunk/
> 
> ) I get:
> 
> $ dicompyler 
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
>     "__main__", fname, loader, pkg_name)
>   File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
>     exec code in run_globals
>   File "/usr/share/dicompyler/main.py", line 23, in <module>
>     from wx.lib.pubsub import Publisher as pub
> ImportError: cannot import name Publisher
> swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destructor found.
> 
> Any hint how to fix this?

It seems the "pubsub" stuff (which isn't in the C++ API but wxPython
bundles) changed API quite a bit.  I hit that ImportError when I tried
to rebuild bitpim, but ucko fixed it before I looked into what was going
on:

"Use a less ancient pubsub interface."

https://packages.qa.debian.org/b/bitpim/news/20140829T230338Z.html

It looks like bitpim's patches aren't split out, but a debdiff between
-3 and -4 would likely be instructive:

http://sources.debian.net/src/bitpim/1.0.7%2Bdfsg1-4/debian/

Hope that's a helpful pointer.

Cheers,
    Olly