Re: ABI change that causes PyQwt and PyQwt3d to segfault
There were API bumps in sip4 4.14.7 and 4.15. Maybe it's a regression
caused by one of them.
I've tried to report the issue upstream, but they didn't know anything
about that. See the thread starting at
http://www.riverbankcomputing.com/pipermail/pyqt/2013-November/033428.html.
Anyway, now that you fixed that by rebuild, we can not care anymore.
On Thu, Jan 9, 2014 at 2:22 AM, Gudjon I. Gudjonsson <gudjon@gudjon.org> wrote:
> Hi list
> I got a bug report regarding PyQwt (see below). Once again
> it segfaults and when I test PyQwt3d it segfaults as well.
> The problem is fixed by a new upload but my problem is that
> I cannot request a binNMU unless I know what ABI change
> causes the problem. Does anyone know what causes it and if
> the soname of some library was not bumped this time?
>
> Regards
> Gudjon
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731437
--
Dmitry Shachnev
Reply to: