Bug#1011101: nodejs: FTBFS on mipsel: multiple failures with openssl 3.0

2022-05-31 Thread Sebastian Andrzej Siewior
On 2022-05-31 23:47:15 [+0200], Jérémy Lal wrote: > Le jeu. 26 mai 2022 à 09:01, Sebastian Andrzej Siewior < > sebast...@breakpoint.cc> a écrit : > > Shout out... I've tried some things but it still fails. > I think there's some bug or option activated on mipsel, > that prevents openssl from loadi

Bug#1011101: nodejs: FTBFS on mipsel: multiple failures with openssl 3.0

2022-05-31 Thread Jérémy Lal
Le jeu. 26 mai 2022 à 09:01, Sebastian Andrzej Siewior < sebast...@breakpoint.cc> a écrit : > On 2022-05-16 22:38:44 [+0200], Jérémy Lal wrote: > > Last time so many openssl-related test failures happened, > > OPENSSL_CONF env was set to a relative path, and nodejs/openssl3 > > expected an absolut

Bug#1011101: nodejs: FTBFS on mipsel: multiple failures with openssl 3.0

2022-05-26 Thread Sebastian Andrzej Siewior
On 2022-05-16 22:38:44 [+0200], Jérémy Lal wrote: > Last time so many openssl-related test failures happened, > OPENSSL_CONF env was set to a relative path, and nodejs/openssl3 > expected an absolute path. I don't understand why mipsel is different here. The init looks okay. I copied the .cnf from

Bug#1011101: nodejs: FTBFS on mipsel: multiple failures with openssl 3.0

2022-05-16 Thread Jérémy Lal
Package: nodejs Version: 16.14.2+dfsg1-1+b1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Last time so many openssl-related test failures happened, OPENSSL_CONF env was set to a relative path, and nodejs/openssl3 expected an absolute p