From: Raghav Gururajan <rg@raghavgururajan.name>
To: "Ricardo Wurmus" <rekado@elephly.net>,
"Léo Le Bouter" <lle-bout@zaclys.net>,
"Danny Milosavljevic" <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: GNOME 3.34 in GNU Guix and security
Date: Thu, 11 Mar 2021 03:23:00 -0500 [thread overview]
Message-ID: <15fc2434-2a8e-2a42-1c2a-9ea0885c1c9c@raghavgururajan.name> (raw)
In-Reply-To: <87im5yqfhl.fsf@elephly.net>
[-- Attachment #1.1: Type: text/plain, Size: 1208 bytes --]
Hi Ricardo!
> 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.
wip-desktop consists of some upgrades, plus, lot of improvements to
gnome packages and it's immediate dependencies. About 50% of them not
merged directly in master. When Danny and I, were merging other 50% to
core-updates, core-updates were broken. So we tried to merge few commits
in master, which got reverted due to high re-builds. I was told by Danny
that we can only merge stuff when c-u is back to normal.
Since huge time has passed, we need to re-work some commits with
rebasing from master. This gonna require testing via huge re-builds.
Danny is working on setting-up a powerful system to do this work.
Let me speak to Danny and get back to you here. Due to the security
nature of this issue, I am willing to spend this month focusing on
GNOME/wip-desktop.
Regards,
RG.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2021-03-11 8:23 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
2021-03-11 8:23 ` Raghav Gururajan [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15fc2434-2a8e-2a42-1c2a-9ea0885c1c9c@raghavgururajan.name \
--to=rg@raghavgururajan.name \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
--cc=rekado@elephly.net \
/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.