From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 51554-done@debbugs.gnu.org
Subject: bug#51554: [PATCH] gnu: libva: Update to 2.13.0
Date: Thu, 25 Nov 2021 01:49:46 -0500 [thread overview]
Message-ID: <87y25cafw5.fsf_-_@gmail.com> (raw)
In-Reply-To: <87y25xg05y.fsf@jpoiret.xyz> (Josselin Poiret's message of "Tue, 09 Nov 2021 09:15:21 +0000")
Hello,
Josselin Poiret <dev@jpoiret.xyz> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>> For the record, this entails lots of rebuilds, contrary to what one
>> might think:
>>
>> --8<---------------cut here---------------start------------->8---
>> $ ./pre-inst-env guix refresh -l -e '(force (@@ (gnu packages gl) libva-without-mesa))'
>> Building the following 1478 packages would ensure 2711 dependent packages are rebuilt: […]
>> --8<---------------cut here---------------end--------------->8---
>>
>> I suppose this could go to ‘core-updates’.
>
> My bad, I completely missed this. I initially wanted to upgrade libva
> because the older version doesn't work on core-updates-frozen with
> Wayland compositors, so I think it should ideally belong there if
> possible to avoid having broken hardware acceleration for a while when
> that branch is merged. If it does indeed lead to too many rebuilds,
> then maybe it could go onto core-updates-frozen-batched-changes, but
> then that'd delay its merging again. I'm not too sure between those,
> but I think it should be one of them.
I had totally missed that for the batched branch.
Too bad. I know Ludovic had concerns about a ~3K rebuilds; that's a lot
but currently only x86_64 and i686 are in a state of building the world
it seems, so that's about 6K packages.
I've bunched this with glib-networking, another similar sized rebuild,
manually built most of the dependents on berlin for x86_64, and pushed
as 0a787e67ecd0fab42c7ddfec639b53d58c15af6e.
Closing.
Maxim
prev parent reply other threads:[~2021-11-25 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 16:03 [bug#51554] [PATCH] gnu: libva: Update to 2.13.0 Josselin Poiret via Guix-patches via
2021-11-07 21:49 ` Ludovic Courtès
2021-11-09 9:15 ` Josselin Poiret via Guix-patches via
2021-11-25 6:49 ` Maxim Cournoyer [this message]
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=87y25cafw5.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=51554-done@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludo@gnu.org \
/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).