[Pkg-electronics-devel] Bug#913864: kicad: Backtraces on opening cvpcb
Carsten Schoenert
c.schoenert at t-online.de
Fri Nov 16 17:39:44 GMT 2018
Am 16.11.18 um 15:28 schrieb Seth Hillbrand:
> Hello Carsten-
> Am 2018-11-16 02:00, schrieb Carsten Schoenert:
>> Hello Seth,
>>
>> seems there is another issue with the RTTI implementation, now as far I
>> see on amd64.
>> Maybe this is already fixed in the current HEAD of the 5.x tree?
>
> As I recall, this issue is an incompatibility between 3.0.2 and 3.0.4 of
> the wx libraries. If Julien downgrades libwxbase and libwxgtk3.0 to the
> 3.0.2.0+dfsg-8, this issue should go away. Please let me know if it
> doesn't.
Just for the record, testing/unstable is providing 3.0.4+dfsg-4 and
stable/stretch is providing 3.0.2+dfsg-4, backports hold the same
version as testing.
> $ rmadison libwxgtk3.0-0v5 libwxbase3.0-0v5 python-wxgtk3.0
> libwxbase3.0-0v5 | 3.0.2+dfsg-4 | stable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libwxbase3.0-0v5 | 3.0.4+dfsg-4~bpo9+1 | stretch-backports | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libwxbase3.0-0v5 | 3.0.4+dfsg-4 | testing | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libwxbase3.0-0v5 | 3.0.4+dfsg-4 | unstable | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
> libwxgtk3.0-0v5 | 3.0.2+dfsg-4 | stable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libwxgtk3.0-0v5 | 3.0.4+dfsg-4~bpo9+1 | stretch-backports | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libwxgtk3.0-0v5 | 3.0.4+dfsg-4 | testing | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libwxgtk3.0-0v5 | 3.0.4+dfsg-4 | unstable | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
> python-wxgtk3.0 | 3.0.1.1+dfsg-2 | oldstable | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
> python-wxgtk3.0 | 3.0.1.1+dfsg-2 | oldstable-kfreebsd | kfreebsd-amd64, kfreebsd-i386
> python-wxgtk3.0 | 3.0.2.0+dfsg-4 | stable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> python-wxgtk3.0 | 3.0.2.0+dfsg-8 | testing | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> python-wxgtk3.0 | 3.0.2.0+dfsg-8 | unstable | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
So downgrading is a bit difficult and right now before the soft freeze
for Buster not the right way I think.
I can try to build some recent version of 5.x for experimental. But
currently don't know if I will will find to do this in the next days.
--
Regards
Carsten Schoenert
More information about the Pkg-electronics-devel
mailing list