Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)

2023-05-02 Thread Nilesh Patra
On Sat, Apr 29, 2023 at 07:44:24PM +0530, Nilesh Patra wrote: > On Tue, Apr 18, 2023 at 03:54:23PM +0200, Andreas Tille wrote: > >2. Remove the package from testing for the moment. The only > > rdepends is currently pan-grazing-incidence which will be > > lowered to suggests once

Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)

2023-04-29 Thread Nilesh Patra
On Tue, Apr 18, 2023 at 03:54:23PM +0200, Andreas Tille wrote: > and we have other errors for other architectures which all contain > the string "numba". IMHO this is a mess we can hardly fix in hard > freeze. I see only two chances: I haven't done a thorough research but it is probably

Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)

2023-04-18 Thread Andreas Tille
Hi, I've found genx in the "Cleaner view"[1] due to missing builds[2]. It turns out that for instance for arm64[3] the build fails with tests/test_numba_equivalency.py Fatal Python error: Segmentation fault For armel[4] (and armhf) we get dh_auto_test -a -O--buildsystem=pybuild I: