2011/11/5 PICCA Frédéric-Emmanuel <frederic-emmanuel.pi...@synchrotron-soleil.fr>: >> Ok, upgrading python-qt4, libqtwebkit4 and a bunch of qt4 libs spyder >> it's now starting. Anyhow, given it's a recurring problem, and it >> seems spyder needs QT4 stuff to work, you might need to "tune" > > yes everythings is in "tune" :) > My problem is that I do not know which version of python-qt4 is ok ? with > which combination of libqt4... > > it seems that the python-qt4 maintainer started a thread [1] about this > python-qt4, python-sip compatibility etc.. > I am not even convince that this is the same issue.
infact I don't think it is: I first upgraded the QT4 stack, and still segfault, then python-qt4, still segfault, only after upgradng also libqtwebkit4 the segfault gone away. > Is it a API breakage in the qt4 library which cause this segfault ? I don't know, maybe ask the QT4 maint? >> dependencies of spyder package. Leaving this bug opened to let remind >> of doing that. > > ok, do you think that I can downgrad it to unblock the testing migration ? Well, you'd have to check if the version in testing of qt4/python-qt/libwebkitqt don't make spyder segfault. Else, I think it's better not to transit to testing until it's working correctly out-of-the-box (which currently doesn't). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
