From: Ian Eure <ian@retrospec.tv>
To: 70618@debbugs.gnu.org
Cc: Ian Eure <ian@retrospec.tv>
Subject: [bug#70618] [PATCH 0/3] Update LibreWolf to 125.0.2-1
Date: Sat, 27 Apr 2024 17:31:21 -0700 [thread overview]
Message-ID: <cover.1714263218.git.ian@retrospec.tv> (raw)
New upstream release. A few things to note:
- nss / nss-certs needs a bump from 3.98->3.99, as this is what LibreWolf wants in order to build.
- Clang 13.x (the Guix default) segfaulted when building LibreWolf and suggested that I file a bug report. Switching to clang/LLVM 18 resolved the issue.
LibreWolf 125.0.2-1 resolves:
CVE-2024-3852 (high)
CVE-2024-3853 (high)
CVE-2024-3854 (high)
CVE-2024-3855 (high)
CVE-2024-3856 (high)
CVE-2024-3857 (high)
CVE-2024-3858 (high)
CVE-2024-3859 (moderate)
CVE-2024-3860 (moderate)
CVE-2024-3861 (moderate)
CVE-2024-3862 (moderate)
CVE-2024-3302 (low)
CVE-2024-3864 (high)
CVE-2024-3865 (high)
Ian Eure (3):
gnu: nss/fixed: Update to 3.99.
gnu: nss-certs: Update to 3.99.
gnu: librewolf: Update to 125.0.2-1.
gnu/packages/certs.scm | 6 +++---
gnu/packages/librewolf.scm | 15 ++++++++-------
gnu/packages/nss.scm | 4 ++--
3 files changed, 13 insertions(+), 12 deletions(-)
base-commit: 8d29f416a9378d30f63c2a95f1bd1a420d9ccab4
--
2.41.0
next reply other threads:[~2024-04-28 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 0:31 Ian Eure [this message]
2024-04-28 0:31 ` [bug#70621] [PATCH 1/3] gnu: nss/fixed: Update to 3.99 Ian Eure
2024-04-28 0:31 ` [bug#70619] [PATCH 2/3] gnu: nss-certs: " Ian Eure
2024-04-28 0:31 ` [bug#70620] [PATCH 3/3] gnu: librewolf: Update to 125.0.2-1 Ian Eure
[not found] ` <handler.70620.B.171426434011402.ack@debbugs.gnu.org>
2024-04-28 0:41 ` [bug#70620] Acknowledgement ([PATCH 3/3] gnu: librewolf: Update to 125.0.2-1.) Ian Eure
2024-04-28 14:42 ` bug#70618: [PATCH 0/3] Update LibreWolf to 125.0.2-1 Maxim Cournoyer
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=cover.1714263218.git.ian@retrospec.tv \
--to=ian@retrospec.tv \
--cc=70618@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 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.