From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: 74780@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#74780] Request for merging "mesa-updates" branch
Date: Fri, 20 Dec 2024 20:31:57 +0000 [thread overview]
Message-ID: <87a5cqxfik.fsf@protonmail.com> (raw)
In-Reply-To: <8734iubuk1.fsf@protonmail.com>
On Wed, Dec 11, 2024 at 06:30 AM, John Kehayias wrote:
> Hi Guix,
>
> Currently the mesa-updates branch just has a few updates which seem to
> have built fine (on x86_64 at least), see
> <https://issues.guix.gnu.org/74779>.
>
> I don't know of other pending changes other than a libva update I'll
> see about. Perhaps we can do some ungrafting too?
>
> John
(CC-ing Efraim after the patch to build the asahi vulkan driver on
aarch64-linux)
I just rebased on master after further updating wayland-protocols and
mesa to their very freshest versions.
Not much else going on here, so maybe just let this build and then merge
to keep things current. Unfortunately the QA page hasn't shown a status
for this branch but I'll check later.
There are discussions about libglvnd support in Mesa I need to chime in
on, so we could tackle that, but not until the new year for me. That
will require a decent number of changes and lots more testing, so my
preference would be to merge this branch when substitutes are available
and then immediately work on libglvnd or whatever else is pending.
John
next prev parent reply other threads:[~2024-12-20 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 6:30 [bug#74780] Request for merging "mesa-updates" branch John Kehayias via Guix-patches via
2024-12-20 20:31 ` John Kehayias via Guix-patches via [this message]
2024-12-21 16:32 ` Efraim Flashner
2024-12-22 9:19 ` Efraim Flashner
2024-12-29 14:57 ` Ludovic Courtès
2024-12-30 2:46 ` John Kehayias via Guix-patches via
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=87a5cqxfik.fsf@protonmail.com \
--to=guix-patches@gnu.org \
--cc=74780@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=john.kehayias@protonmail.com \
/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).