From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 40316@debbugs.gnu.org
Cc: control@debbugs.gnu.org
Subject: bug#40316: core-updates nss not reproducible
Date: Thu, 07 Mar 2024 14:16:33 -0800 [thread overview]
Message-ID: <87zfv9n0vy.fsf@wireframe> (raw)
In-Reply-To: <87a6osdf97.fsf@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
retitle 40316 nss not reproducible
thanks
Still an issue on master as of d29e5a83e887cd2f4f459a12cbbfc40c77e55ce2:
guix challenge --verbose --diff=simple nss
guix challenge: warning: could not determine current substitute URLs; using defaults
/gnu/store/mc9gdsm0cqpyd2522f5xghdl59p1l35r-nss-3.88.1 contents differ:
no local build for '/gnu/store/mc9gdsm0cqpyd2522f5xghdl59p1l35r-nss-3.88.1'
https://ci.guix.gnu.org/nar/lzip/mc9gdsm0cqpyd2522f5xghdl59p1l35r-nss-3.88.1: 18xvq9cb7y2hajixnkk24bh969px0h5289hgby484iyg3x73sagp
https://bordeaux.guix.gnu.org/nar/lzip/mc9gdsm0cqpyd2522f5xghdl59p1l35r-nss-3.88.1: 0pnmzsy7m34v51qxpi4lrj2a9m7l19prldabwad8gx24gih4irah
differing files:
/lib/nss/libfreebl3.chk
/lib/nss/libfreeblpriv3.chk
/lib/nss/libnssdbm3.chk
/lib/nss/libsoftokn3.chk
1 store items were analyzed:
- 0 (0.0%) were identical
- 1 (100.0%) differed
- 0 (0.0%) were inconclusive
According to the notes in Debian, this is due to cryptographic
signatures performed at build time:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/nss.html
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-03-07 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 11:16 bug#40316: core-updates nss not reproducible Danny Milosavljevic
2020-03-30 6:09 ` Gábor Boskovits
2020-03-30 11:55 ` Marius Bakke
2020-03-31 9:28 ` Björn Höfling
2021-05-18 1:04 ` Bone Baboon via Bug reports for GNU Guix
2024-03-07 22:16 ` Vagrant Cascadian [this message]
2024-04-23 12:42 ` bug#40316: Update needed of NSS Steve George
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfv9n0vy.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=40316@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).