Re: "Fatal Python error: Aborted" errors for Python/Qt packages
Le 12/03/2024 à 08:09, Julian Gilbey a écrit : On Tue, Mar 12, 2024 at 07:55:55AM +0100, Roland Mas wrote: Hi Julian, Ghislain, list, I'm working on various Qt-related Python packages, and I'm seeing strange errors when building in cowbuilder chroots (with git-buildpackage). They don't seem to happen when building out-of-chroot. So far I managed to track them down to qtpy, but I'm stumped as to the why and how to fix. For instance, when building from commit b360a9defbb470fe6ab1793371d16487e52b548b, I get the following output during the testsuite: Hi Roland, I wonder whether it's related to the current t64 library changes in unstable? These are causing all sorts of issues during the transition period. Do the packages build OK in a testing chroot? I only tried python-qtpy, but I get exactly the same behaviour (failure as-is, success with dbus installed). Roland.
Re: "Fatal Python error: Aborted" errors for Python/Qt packages
On Tue, Mar 12, 2024 at 07:55:55AM +0100, Roland Mas wrote: > Hi Julian, Ghislain, list, > > I'm working on various Qt-related Python packages, and I'm seeing strange > errors when building in cowbuilder chroots (with git-buildpackage). They > don't seem to happen when building out-of-chroot. So far I managed to track > them down to qtpy, but I'm stumped as to the why and how to fix. For > instance, when building from commit > b360a9defbb470fe6ab1793371d16487e52b548b, I get the following output during > the testsuite: Hi Roland, I wonder whether it's related to the current t64 library changes in unstable? These are causing all sorts of issues during the transition period. Do the packages build OK in a testing chroot? Best wishes, Julian
