unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: 04/09: gnu: mesa: Update to 23.0.3.
Date: Mon, 08 May 2023 08:08:07 -0400	[thread overview]
Message-ID: <87jzxjvxeg.fsf@gmail.com> (raw)
In-Reply-To: <87r0rrzjbr.fsf@cbaines.net> (Christopher Baines's message of "Mon, 08 May 2023 02:41:14 +0100")

Hi Christopher,

Christopher Baines <mail@cbaines.net> writes:

> guix-commits@gnu.org writes:
>
>> apteryx pushed a commit to branch master
>> in repository guix.
>>
>> commit 0be7838105806819f4586ec9130382a66a22880e
>> Author: Kaelyn Takata <kaelyn.alexi@protonmail.com>
>> AuthorDate: Thu May 4 20:12:46 2023 +0000
>>
>>     gnu: mesa: Update to 23.0.3.
>>
>>     * gnu/packages/gl.scm (mesa): Update to 23.0.3.
>>     [source]: Remove obsolete patch and update HTTPS url.
>>     [arguments]: Enable the crocus gallium driver.
>>     * gnu/packages/patches/mesa-fix-sporadic-test-failures.patch: Delete file.
>>     * gnu/local.mk (dist_patch_DATA): Remove it.
>> ---
>>  gnu/local.mk                                       |  1 -
>>  gnu/packages/gl.scm                                | 14 ++++-------
>>  .../patches/mesa-fix-sporadic-test-failures.patch  | 27 ----------------------
>>  3 files changed, 5 insertions(+), 37 deletions(-)
>
> → guix refresh -l mesa
> Building the following 1954 packages would ensure 4257 dependent
> packages are rebuilt ...
>
>
> I know there's been some discussion about changing processes regarding
> changes like this that impact lots of packages, but as far as I'm aware,
> the documented process hasn't changed yet. So should this have gone to
> core-updates, and not been directly pushed to master?

There isn't currently a core-updates branch, and I need to spend some
time documenting the authorization process for how to create short lived
Cuirass branches.  I think ideally we would have created a
'graphics-team' or similar branch (even the team has yet to be formed)
and let it build.

Seeing the build machines were idling in the European night, I figured I
could get away with it for this time.

But the situation will repeat; I'd like to push some xorg updates that
fix a CVE; we'll nead a 'xorg-team' branch or similar.  Should we create
these branches from the maintenance repository (permanent branches) ?

-- 
Thanks,
Maxim


  reply	other threads:[~2023-05-08 12:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168347913021.32190.10808857919894440138@vcs2.savannah.gnu.org>
     [not found] ` <20230507170531.26A00C22F14@vcs2.savannah.gnu.org>
2023-05-08  1:41   ` 04/09: gnu: mesa: Update to 23.0.3 Christopher Baines
2023-05-08 12:08     ` Maxim Cournoyer [this message]
2023-05-08 12:56       ` Christopher Baines
2023-05-08 15:01         ` Maxim Cournoyer
2023-05-08 16:33           ` Feature branches (was: 04/09: gnu: mesa: Update to 23.0.3) Andreas Enge
2023-05-08 17:01             ` Feature branches Maxim Cournoyer
2023-05-10  9:21               ` Andreas Enge
2023-05-10 13:23                 ` Maxim Cournoyer
2023-05-10 13:40                   ` Andreas Enge
2023-05-10 13:55                     ` Andreas Enge
2023-05-11  4:49                       ` Maxim Cournoyer
2023-05-08 17:15             ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-10  9:11               ` Andreas Enge
2023-05-10 11:30                 ` Christopher Baines
2023-05-08 16:39           ` 04/09: gnu: mesa: Update to 23.0.3 Christopher Baines
2023-05-09  4:37     ` John Kehayias
2023-05-09  8:39       ` Christopher Baines

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=87jzxjvxeg.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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).