From: Ian Eure <ian@retrospec.tv>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 74070-done@debbugs.gnu.org
Subject: [bug#74070] [PATCH v2 0/2] gnu: librewolf: Update to 132.0-1 [security fixes].
Date: Sat, 09 Nov 2024 09:32:57 -0800 [thread overview]
Message-ID: <87a5e82ty8.fsf@meson> (raw)
In-Reply-To: <87cyj8uhy0.fsf@gnu.org>
Hi Ludo’
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Ian Eure <ian@retrospec.tv> skribis:
>
>> New patch for the new upstream version. vs. the previous
>> patch, this series:
>>
>> - Updates nss to 3.105, the minimum version required by
>> LibreWolf/Firefox
>> 132.0. I attempted to update to 3.106, but there's a
>> regression causing
>> test failures[1].
>> - Updates LibreWolf to 132.0-1. Simple version/hash update.
>> - Removes the `patch/' prefix of the locale patch.
>>
>> [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1927096
>>
>> Ian Eure (2):
>> gnu: nss-rapid: Update to 3.105.
>> gnu: librewolf: Update to 132.0-1 [security fixes].
>
> Applied after building locally.
>
> It’s unfortunate that qa.guix hasn’t been able to pick it up in
> a timely
> fashion—it’ll be several hours before substitutes are available.
> But I
> thought we’d rather go ahead and apply these upgrades and
> security fixes
> without waiting any longer.
>
Makes sense, thank you for pushing this!
— Ian
prev parent reply other threads:[~2024-11-09 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 22:20 [bug#74070] [PATCH] gnu: librewolf: Update to 131.0.3-1 [security fixes] Ian Eure
2024-11-01 18:28 ` [bug#74070] QA review for 74070 Noé Lopez via Guix-patches via
2024-11-06 14:25 ` [bug#74070] [PATCH v2 0/2] gnu: librewolf: Update to 132.0-1 [security fixes] Ian Eure
2024-11-06 14:25 ` [bug#74070] [PATCH v2 1/2] gnu: nss-rapid: Update to 3.105 Ian Eure
2024-11-06 14:26 ` [bug#74070] [PATCH v2 2/2] gnu: librewolf: Update to 132.0-1 [security fixes] Ian Eure
2024-11-06 22:16 ` bug#74070: [PATCH v2 0/2] " Ludovic Courtès
2024-11-09 17:32 ` Ian Eure [this message]
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=87a5e82ty8.fsf@meson \
--to=ian@retrospec.tv \
--cc=74070-done@debbugs.gnu.org \
--cc=ludo@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).