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

[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 path.


-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nodejs depends on:
ii libc6 2.33-7
ii libnode93 16.14.2+dfsg1-1+b1

Versions of packages nodejs recommends:
ii ca-certificates 20211016
ii nodejs-doc 16.14.2+dfsg1-1

Versions of packages nodejs suggests:
ii npm 8.10.0~ds1-2

-- no debconf information

[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 3.0
cp /etc/ssl/openssl.cnf deps/openssl/openssl/apps/openssl.cnf

and then removed the protocol/ sec-level override:

--- /etc/ssl/openssl.cnf 2022-05-13 21:25:01.000000000 +0000
+++ deps/openssl/openssl/apps/openssl.cnf 2022-05-25 20:58:47.602964293 +0000
@@ -52,7 +52,6 @@

[openssl_init]
providers = provider_sect
-ssl_conf = ssl_sect

# List of providers to load
[provider_sect]
@@ -389,10 +388,3 @@
# Certificate revocation
cmd = rr
oldcert = $insta::certout # insta.cert.pem
-
-[ssl_sect]
-system_default = system_default_sect
-
-[system_default_sect]
-MinProtocol = TLSv1.2
-CipherString = DEFAULT:@SECLEVEL=2

with this change the suite passed on mipsel. You could move that file to
debian/ for the testsuite and I keep thinking about not touching that
file at all.
I could keep investigating why mipsel is different here but I'm short on
time right now and eller isn't exactly a fast beast.
Side note: I built it with -j3 and I hope that the build time reduced
compared to the initial -j1 (I had to build a few times because -nc
didn't skip anything…).

Sebastian

[Jérémy Lal]

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 loading error strings.

There are builds on eller.debian.org/~kapouer that you can play with.

Help is welcome !

Jérémy

 

Sebastian

[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 <
> seba...@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 loading error strings.
>
> There are builds on eller.debian.org/~kapouer that you can play with.
> Help is welcome !

I started it to build on eller the very same you sent that update here.
It reproduced but I did have the time to look at it closer.

> Jérémy

Sebastian