Hi Paul, sorry for the late reply. As I said on debian-devel, I've not enough expertise nor hope on that topic. Switching to lua is the way I went a few times, instead on relying on luajit.
F. On Mon, 02 May 2022 07:55:50 +0200 Paul Gevers <elb...@debian.org> wrote: > Hi, > > On 24-04-2022 12:00, Paul Gevers wrote: > > On Sat, 29 Jan 2022 19:32:53 +0100 Paul Gevers <elb...@debian.org> wrote: > >> With a recent upload of luajit the autopkgtest of knot-resolver fails > >> in testing when that autopkgtest is run with the binary packages of > >> luajit from unstable. It passes when run with only packages from > >> testing. In tabular form: > > > > knot-resolver has been removed from testing due to this bug report, but > > can't migrate back because a newer version fails to build on ppc64el. > > Also other reverse dependencies of luajit show SEGFAULT in their > > autopkgtest on ppc64el, so this seems a problem in luajit. Unfortunately > > (Release Team member opinion) luajit is a key package so can't be > > trivially removed. Can you (maintainer and ppc64el porters) please have > > a look? > > If this issue is difficult to fix, how about removing luajit from > ppc64el? I noticed that the only reverse (build) dependent key package > of luajit (src:efl) already switched to plain lua on ppc64el (probably > because of this issue). > > Paul
signature.asc
Description: PGP signature
