unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: guix-devel@gnu.org, "66964@debbugs.gnu.org" <66964@debbugs.gnu.org>
Subject: Re: bug#66964: Request for merging "mesa-updates" branch
Date: Tue, 14 Nov 2023 20:11:08 +0000	[thread overview]
Message-ID: <87y1f0t7s9.fsf_-_@protonmail.com> (raw)
In-Reply-To: <m-1_kiiKXWXP4nJVxxUfx4CaLLLo-pNr7J3C4dKk0erStH8DfkrwqyQ3s1ou2ibM1cul7813G5q5znMvotRhWsVHSgkTVJqrSRO3jSgyM5w=@protonmail.com>

Hi Kaelyn,

On Sun, Nov 12, 2023 at 08:01 PM, Kaelyn wrote:

> Hi,
>
> I've just submitted a pair of patches for the mesa-updates branch:
> <https://issues.guix.gnu.org/67136> updating xorgproto and
> xorg-server-xwayland. The xorgproto is a high-impact update (guix
> refresh reports rebuilding 8710 packages would ensure 22871 dependent
> packages are rebuilt), but required to update to the latest xwayland
> as xwayland requires a newer version of presentproto than in the
> current guix xorgproto package. The updating and ungrafting of mesa
> and a number of X.org related libraries seemed like a good time (and
> place) to update xorgproto as well.
>
> Cheers,
> Kaelyn

Thanks for the patches. I think mesa-updates in this current iteration
is set on builds (ended up being a lot more due to the ungrafting but
seems done on our main architectures for several days now). I had to
make some other changes to fix some larger breakages but at this point I
think it will just be taking us back in the build queue too much.

So I think it would make more sense on the next big rebuild, either
core-updates (talk about doing that with more ungrafts right now) or
I'll do mesa-updates again when the next release of mesa hits. Or maybe
it makes sense to just do another branch for xwayland?

Open to ideas! I'll send a separate message soon on the status of
mesa-updates and see what people think, but my thought was to merge this
to master in the next day or so if there are no objections.

Thanks!
John



  reply	other threads:[~2023-11-14 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06  4:49 mesa-updates: call for patches John Kehayias
2023-11-12 20:01 ` [bug#66964] " Kaelyn via Guix-patches via
2023-11-14 20:11   ` John Kehayias [this message]
2023-11-14 20:36     ` bug#66964: Request for merging "mesa-updates" branch Kaelyn
2023-12-09 19:28       ` Kaelyn
2023-11-15  6:28     ` Efraim Flashner
2023-11-15  6:28       ` [bug#66964] " Efraim Flashner
2023-11-28  5:29       ` bug#66964: " 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=87y1f0t7s9.fsf_-_@protonmail.com \
    --to=john.kehayias@protonmail.com \
    --cc=66964@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=kaelyn.alexi@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).