From: Efraim Flashner <efraim@flashner.co.il>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
Kaelyn <kaelyn.alexi@protonmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
Vivien Kraus <vivien@planete-kraus.eu>,
67875@debbugs.gnu.org
Subject: Re: xwayland security updates, to mesa- or core-updates or ?
Date: Mon, 8 Jan 2024 10:32:50 +0200 [thread overview]
Message-ID: <ZZuzMs0mdntz9ooz@3900XT> (raw)
In-Reply-To: <87mstg1it6.fsf@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2744 bytes --]
On Mon, Jan 08, 2024 at 05:43:40AM +0000, John Kehayias wrote:
> Hi all,
>
> Forgive the top post and please see below/previous messages for
> previous updates.
>
> TL;DR: I plan to merge mesa-updates into master today-ish (well,
> tomorrow for me at this point).
>
> I've been checking in with Efraim who's been very helpful at trying to
> nudge along substitute coverage on non-x86_64 platforms. Unfortunately
> looks like we have plateaued a bit on, e.g., aarch64. We haven't been
> getting stats from QA for this round, and Berlin looks good for what
> it covers (x86) but other architectures are down from what we can
> tell.
>
> I don't think there are any fundamental failures at this point but
> just lots of "missing derivation" errors (I've restarted so many
> manually for x86_64/i686) and builds not completing without restarts.
> Or unknown reasons. Given the few weeks I've given this and the risk
> of just perpetually doing rebuilds to keep catching up (with then more
> updates to push) I think it would be best to merge to master. Mesa and
> other bits will continue to move forward as well, so I think it is
> time so we can be somewhat timely.
>
> I'd rather not without complete substitute coverage, but given recent
> build farm difficulties, and the tools we do have for users (pinning,
> weather checks, etc.) I think it is best to call this branch so we can
> move on. Gnome has some updates that will need (re)building as well as
> trying to move forward with core-updates now too.
>
> This is a case where having some better sense of our users and actual
> substitute needs/wants would be helpful (yes, Guix survey!) as well as
> recognizing our current infrastructure limits. Here's another vote for
> prioritizing infrastructure and making sure QA lives and expands.
>
> Feel free to object to this merge timing, though with the relative
> silence in each previous message I take it I can make a call here.
>
> Thanks everyone and hope 2024 is off to a good start! Enjoy the new
> mesa with curl and xwayland security updates (no new grafts!).
To record here more or less what I said on IRC, we're currently at
rust-1.56 or 1.57 on the mesa-teams branch, and we're looking at
probably more than a week to build out to rust itself, and then the
packages which depend on it. Currently, on master, Berlin already is
running behind on building rust, and it wasn't until after the previous
mesa-updates merge that it caught up with building rust.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-08 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 5:43 xwayland security updates, to mesa- or core-updates or ? John Kehayias
2024-01-08 8:32 ` Efraim Flashner [this message]
2024-01-08 17:24 ` John Kehayias
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 21:18 John Kehayias
2023-12-22 7:19 ` Efraim Flashner
2023-12-25 6:44 ` Efraim Flashner
2024-01-04 5:13 ` John Kehayias
2023-12-15 6:21 John Kehayias
2023-12-15 17:25 ` Kaelyn
2023-12-18 6:02 ` John Kehayias
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=ZZuzMs0mdntz9ooz@3900XT \
--to=efraim@flashner.co.il \
--cc=67875@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=kaelyn.alexi@protonmail.com \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=vivien@planete-kraus.eu \
/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).