From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 40316@debbugs.gnu.org
Subject: bug#40316: core-updates nss not reproducible
Date: Tue, 31 Mar 2020 11:28:41 +0200 [thread overview]
Message-ID: <20200331112841.37c909bf@alma-ubu> (raw)
In-Reply-To: <87pncuukf6.fsf@devup.no>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Mon, 30 Mar 2020 13:55:09 +0200
Marius Bakke <mbakke@fastmail.com> wrote:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
> > Hi,
> >
> > core-updates' nss is not reproducible (commit
> > aebcbb27bc2f192cc06163251bab66a4ceb7b7d6).
>
> Is this issue only present on the 'core-updates' branch? There
> haven't been any changes to NSS on that branch compared to 'master'
> AFAIK.
I haven't tried it on 'master', but I think it is branch-independent,
people are only testing it on core-updates. This bug is over 2 years
old with different versions of nss affected and the same three files
not reproducible. And we had past core-updates mergers.
I found and merged these reports:
bug#30108: [core-updates] nss 3.34.1 not reproducible
bug#33507: nss 3.39 output is not deterministic
bug#40316: core-updates nss not reproducible
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-03-31 9:29 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 [this message]
2021-05-18 1:04 ` Bone Baboon via Bug reports for GNU Guix
2024-03-07 22:16 ` Vagrant Cascadian
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=20200331112841.37c909bf@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=40316@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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).