From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: 宋文武 <iyzsong@envs.net>
Cc: 64369@debbugs.gnu.org, Sigve Sudland <sigve_sudland@hotmail.com>,
64738@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>
Subject: [bug#64369] Request for merging "mesa-updates" branch
Date: Thu, 20 Jul 2023 15:54:55 +0000 [thread overview]
Message-ID: <87ilaezigl.fsf_-_@protonmail.com> (raw)
In-Reply-To: <87o7kx6j62.fsf@protonmail.com>
Hi,
On Thu, Jul 20, 2023 at 06:58 PM, 宋文武 wrote:
>>
>> gnu: mesa: Enable zstd compression for shader cache.
>>
>> * gnu/packages/gl.scm (mesa)[inputs]: Add zstd:lib.
>> [arguments]: Add '-Dzstd=enabled' to configure-flags.
>
> Pushed to the mesa-updates branch, merging progress tracked in
> https://issues.guix.gnu.org/64369.
>
> Thanks.
I just saw this as the message only went to the bug number. I would not
have merged this yet without checking about build status after the big
texlive updates. I was hoping to avoid a full rebuild so we could merge
to master with substitutes already, after checking post-texlive and the
graft of mesa on master.
However, doesn't seem like Cuirass has picked up this change and hasn't
built yet. Any idea why?
My plan right now was going to be to merge master into mesa-updates, see
what the build status looks like, and then decide from there. If there
were not too many rebuilds (say less than 1000) from the updates on
master, we should be able to go ahead soon. And then start on the next
round of patches/updates for mesa-updates.
On the other hand, if there were lots of rebuilds there are other
patches waiting that should be used also (libdrm, libva if I remember)
as well as ungrafting the change on master. So, preventing waiting and
doing another big rebuild with the changes that have been waiting since
the first build of this branch.
What do people think? My thought right now was to revert this change
(since it rebuilds all of mesa dependents), merge master in, and check
the status. But I'm confused why Cuirass wasn't building..
John
next prev parent reply other threads:[~2023-07-20 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 15:53 bug#64369: Request for merging "mesa-updates" branch John Kehayias via Bug reports for GNU Guix
2023-07-01 10:36 ` [bug#64369] " Christopher Baines
2023-07-05 20:04 ` John Kehayias via Guix-patches via
2023-07-20 15:54 ` John Kehayias via Guix-patches via [this message]
2023-07-20 16:03 ` Christopher Baines
2023-07-20 16:23 ` John Kehayias via Guix-patches via
2023-07-20 17:04 ` Christopher Baines
2023-07-20 19:24 ` John Kehayias via Guix-patches via
2023-07-24 15:14 ` John Kehayias via Guix-patches via
2023-07-28 15:29 ` John Kehayias via Guix-patches via
2023-07-31 15:24 ` bug#64369: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilaezigl.fsf_-_@protonmail.com \
--to=guix-patches@gnu.org \
--cc=64369@debbugs.gnu.org \
--cc=64738@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=john.kehayias@protonmail.com \
--cc=mail@cbaines.net \
--cc=sigve_sudland@hotmail.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 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.