From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 70693@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#70693] [PATCH v2] gnu: nss/fixed: Tweak performance test.
Date: Thu, 09 May 2024 15:52:07 +0100 [thread overview]
Message-ID: <87o79fdomg.fsf@cbaines.net> (raw)
In-Reply-To: <87a5kz3wfq.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 09 May 2024 16:13:29 +0200")
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Christopher Baines <mail@cbaines.net> skribis:
>
>> I don't think that necessarily means that patch hasn't worked, it's just
>> that we needed to build nss (because grafts, see #61363) to compute the
>> guix derivation for each system. As Ludo pointed out to me on IRC
>> though, that can probably be avoided so I've sent a v2 series that
>> includes a couple of patches to remove the link between guix and nss via
>> packages needed for the po4a tests.
>
> It would still make sense to apply the initial patch here, IMO.
Personally I'm waiting for QA to build things since I want to see if
this does fix nss on the 4 systems it's currently broken on, and so that
there's substitutes available if and when this is merged.
The large number of builds recently on the master branch might delay
this though.
> Also, we could create an ‘nss-upgrade’ branch to remove the graft and
> upgrade ‘nss’, also applying the reproducibility patches that Christina
> posted.
>
> WDYT?
I don't mind, if it doesn't happen on core-updates then that seems like
an OK approach.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2024-05-09 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 9:41 [bug#70693] [PATCH] gnu: nss/fixed: Tweak performance test Christopher Baines
2024-05-01 9:51 ` [bug#70693] [PATCH v2] " Christopher Baines
2024-05-01 16:32 ` Maxim Cournoyer
2024-05-02 8:16 ` Ludovic Courtès
2024-05-07 19:53 ` Christopher Baines
2024-05-09 14:13 ` Ludovic Courtès
2024-05-09 14:52 ` Christopher Baines [this message]
2024-05-07 19:45 ` [bug#70693] [PATCH v2 1/3] " Christopher Baines
2024-05-07 19:45 ` [bug#70693] [PATCH v2 2/3] gnu: Add po4a-minimal Christopher Baines
2024-05-09 14:11 ` Ludovic Courtès
2024-05-09 14:36 ` Christopher Baines
2024-05-07 19:45 ` [bug#70693] [PATCH v2 3/3] Use po4a-minimal for guix Christopher Baines
2024-05-09 14:09 ` Ludovic Courtès
2024-05-09 14:35 ` [bug#70693] [PATCH v3 1/3] gnu: nss/fixed: Tweak performance test Christopher Baines
2024-05-09 14:35 ` [bug#70693] [PATCH v3 2/3] gnu: Add po4a-minimal Christopher Baines
2024-05-09 14:35 ` [bug#70693] [PATCH v3 3/3] Use po4a-minimal for guix Christopher Baines
2024-05-13 8:58 ` [bug#70693] [PATCH v3 1/3] gnu: nss/fixed: Tweak performance test Ludovic Courtès
2024-05-13 12:44 ` bug#70693: " Christopher Baines
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o79fdomg.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=70693@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.