From: Ian Eure <ian@retrospec.tv>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 67512@debbugs.gnu.org, andrew@trop.in, guix-devel@gnu.org,
Mark H Weaver <mhw@netris.org>,
guix-security@gnu.org
Subject: Re: bug#67512: [PATCH v7 0/3] Add LibreWolf
Date: Sat, 27 Apr 2024 10:19:46 -0700 [thread overview]
Message-ID: <87r0eqww7t.fsf@meson> (raw)
In-Reply-To: <87il03gk24.fsf@lassieur.org>
Clément Lassieur <clement@lassieur.org> writes:
> On Fri, Apr 12 2024, Andrew Tropin via Guix-patches via wrote:
>
>> On 2024-04-06 08:04, Ian Eure wrote:
>>
>>> Moves nss update to nss-3.98 / nss-certs-3.98 to avoid
>>> rebuilding thousands of packages.
>>>
>>> Rebases.
>>>
>>> Ian Eure (3):
>>> gnu: Add nss-3.98.
>>> gnu: Add nss-certs-3.98.
>>> gnu: Add librewolf.
>>>
>>> gnu/packages/certs.scm | 16 +
>>> gnu/packages/librewolf.scm | 621
>>> +++++++++++++++++++++++++++++++++++++
>>> gnu/packages/nss.scm | 45 +++
>>> 3 files changed, 682 insertions(+)
>>> create mode 100644 gnu/packages/librewolf.scm
>>>
>>>
>>> base-commit: ade6845da6cec99f3bca46faac9b2bad6877817e
>>
>> Hi Ian,
>>
>> tested those patches, didn't notice any issues.
>>
>> Added pipewire to LD_LIBRARY_PATH to make screensharing on
>> wayland to
>> work.
>>
>> Added librewolf.scm to gnu/local.mk.
>>
>> Pushed as
>> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3dc26b4eae
>>
>> Thank you very much for you work!
>
> Thank you Andrew for reviewing.
>
> Now that this is pushed, is there anyone maintaining this
> "librewolf"
> package? This is serious work, with security updates quite
> often.
>
Hi Clement,
I’m planning to continue sending patches for updates and the like.
Getting a working updater is close to the top of my list.
> Right now the package is subject to
>
> 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)
>
The version in Guix is the latest available. I’ll send in a patch
when the next release happens; I’m waiting on upstream for that.
Thanks,
— Ian
next prev parent reply other threads:[~2024-04-27 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1701186634.git.ian@retrospec.tv>
[not found] ` <cover.1712415593.git.ian@retrospec.tv>
[not found] ` <87jzl27ml2.fsf@trop.in>
2024-04-27 10:46 ` [bug#67512] [PATCH v7 0/3] Add LibreWolf Clément Lassieur
2024-04-27 17:19 ` Ian Eure [this message]
2024-04-27 18:21 ` Ian Eure
2024-04-28 8:59 ` Clément Lassieur
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=87r0eqww7t.fsf@meson \
--to=ian@retrospec.tv \
--cc=67512@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=guix-security@gnu.org \
--cc=mhw@netris.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).