From: Ricardo Wurmus <rekado@elephly.net>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org, Raghav Gururajan <rg@raghavgururajan.name>
Subject: Re: GNOME 3.34 in GNU Guix and security
Date: Thu, 11 Mar 2021 09:08:54 +0100 [thread overview]
Message-ID: <87im5yqfhl.fsf@elephly.net> (raw)
In-Reply-To: <4720e347b48bd6ca4710b461cadecf0b65aa6442.camel@zaclys.net>
Léo Le Bouter <lle-bout@zaclys.net> writes:
> I must come to the conclusion that using GNOME 3.34 in GNU Guix right
> now is just straight out insecure. I would advise we either, get rid of
> GNOME, backport all individual security patches (they can be
> numerous..), or upgrade GNOME to latest and keep up over time.
>
> I don't think we can afford to spend time backporting security fixes to
> the numerous GNOME packages with CVEs, not with current resources, it
> is time-consuming.
No, GNOME should be upgraded. I upgraded it twice in the past, and it’s
a lot of work, but certainly not impossible.
I don’t know if anyone is working on it right now, though. I was told
months ago that Raghav Gururajan was working on GNOME upgrades as part
of the wip-desktop branch, but my occasional questions for a status
upgrade have gone unanswered. Raghav, please correct me if I’m
mistaken. It would be good to clarify what is and isn’t the scope of
wip-desktop.
We™ should upgrade GNOME as soon as possible. It’s been stuck on 3.34
for much too long.
--
Ricardo
next prev parent reply other threads:[~2021-03-11 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 3:19 GNOME 3.34 in GNU Guix and security Léo Le Bouter
2021-03-11 8:08 ` Ricardo Wurmus [this message]
2021-03-11 8:23 ` Raghav Gururajan
2021-03-11 9:11 ` Ricardo Wurmus
2021-03-11 9:17 ` Raghav Gururajan
2021-03-18 21:32 ` Danny Milosavljevic
2021-03-19 0:10 ` Ricardo Wurmus
2021-03-19 9:13 ` Guillaume Le Vaillant
2021-03-11 8:24 ` Jonathan Brielmaier
2021-03-11 8:18 ` Mark H Weaver
2021-03-11 8:28 ` Léo Le Bouter
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=87im5yqfhl.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
--cc=rg@raghavgururajan.name \
/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).