Bug#1144052: libnode137 regressed in reproducibility

Jérémy Lal <[email protected]>
Newsgroups gmane.linux.debian.devel.bugs.rc
Message-ID <178643746757.247344.5035236412140487925.reportbug__7512.04566783912$1786437555$gmane$org@lal.local>
Source: nodejs
Followup-For: Bug #1144052

Hi Jochen,

did it actually regress, or was the previous version failure ignored ?

I'm about to open an upstream bug report, because they want to make
their builds reproducible.

The source of variation is likely to come from mksnapshot.
Anyone willing to look into this will want to search for
"predictable", "random_seed".

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

Kernel: Linux 7.1.7+deb14-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

-- no debconf information
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.