On Sun, Dec 21, 2014 at 12:41:19AM +0100, Pietro Battiston wrote: > Il giorno sab, 20/12/2014 alle 10.37 +0000, Olly Betts ha scritto: > > On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote: > > > So using wx 2.8 is not an option in jessie, and the original bug must be > > > solved. > > > > Or we don't release jessie with fontypython - you say in #765487 that it > > "seems pretty abandoned upstream". It does seem like people are > > actually still using it though, judging from the comments in that > > ticket. > > I'm reluctant for three reasons: > 1) I and other people (a niche, but a stable niche, and if I don't > misinterpret popcon, its 0.03% of active users locate it in the top 10% > of debian packages) use it
I think you must be misinterpreting - popcon doesn't report data about how much people use the packages they have installed (only if they've used each package "recently"). > 2) to the best of my knowledge, there are no alternatives (i.e. programs > allowing to install a font without admin powers or messing with > shell/hidden files), > 3) it works flawlessly with wx 2.8, and I expect the fix for 3.0 to be > easy. Sounds like it is still useful. > > > Olly, in #757886 you state that "everything seems to be fine... can you > > > confirm > > > with wxpython3.0 3.0.1.1+dfsg-2 ? > > > > Will retest it when I have a suitable machine in front of me. > > > > But the error messages in #765487 do seem to indicate how to solve the > > problem: > > > > .../src/common/stdpbase.cpp(62): assert "traits" failed in Get(): create > > wxApp before calling this > > > > i.e. make sure that the wxApp object is created before this code gets > > called. > > This is easily fixed.¹ I will try to also fix the rest,¹ but since you > reported fontypython working with wx 3.0, and since I am not a wx > expert, I was wondering whether only some systems were affected, and > why. I tried to test the latest fontypython version (your NMU) but the package seems to be missing any actual python code: $ dpkg -L fontypython /. /usr /usr/share /usr/share/doc /usr/share/doc/fontypython /usr/share/doc/fontypython/copyright /usr/share/doc/fontypython/changelog.gz /usr/share/doc/fontypython/README.gz /usr/share/doc/fontypython/changelog.Debian.gz /usr/share/man /usr/share/man/man1 /usr/share/man/man1/fontypython.1.gz /usr/share/menu /usr/share/menu/fontypython /usr/share/man/man1/start_fontypython.1.gz With the version I NMUed, I do see the assertion failures. Not sure if that means I messed up testing, or that something has changed in wxwidgets3.0 or wxpython3.0 since. It looks like the assertions are due to trying to create wx.Locale objects before the wx.App object. It doesn't need to create one in every file - just creating one should be enough. It then runs into the wx.ListCtrl issue you mention in the other bug. The simple fix is to just disable all such assertions (as happens by default with wx 2.8): http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README With that, fontypython runs for me - I'll send an nmudiff in a moment. It would be better to try to fix them, but I don't have time to dig in deeper. If you want to, please do - or let me know if you'd like me to just upload my NMU. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
