all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 61583@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>,
	Greg Hogan <code@greghogan.com>
Subject: [bug#61583] [PATCH] gnu: git: Update to 2.39.2 [fixes CVE-2023-22490 & CVE-2023-23946].
Date: Sun, 5 Mar 2023 13:45:58 -0500	[thread overview]
Message-ID: <ZATjZm3u26B1E7i6@jasmine.lan> (raw)
In-Reply-To: <CAJ3okZ3dxoyHKoi0QVikKyanNz9xDCWU7b6WcF73N8J31bmLxQ@mail.gmail.com>

On Sat, Mar 04, 2023 at 07:52:04PM +0100, Simon Tournier wrote:
> I get 546 dependent packages for git + git-minimal which need to be
> re-built.  And some are really expensive -- that what I meant by "a
> lot of rebuilds". :-)
> 
> Well, I do not know if there is an issue with QA or it is just really
> expensive but the process is still pending, if I read correctly
> <https://qa.guix.gnu.org/issue/61583>.

At the Guix Days, it was said that there is a limit to how many builds
the QA server will perform for a change. I don't recall the number, but
maybe 300 builds per change? So, if a change causes too many rebuilds,
the QA server will not perform the builds.

Aside: Chris, I'd be happy to add a FAQ page to the QA server that
answers this type of question. Let me know if I've missed that one
already exists.

For the Berlin server, I don't think that 546 builds is too many, at
least for Intel systems.

> > Concretely, why can't we push this to master immediately?
> 
> Somehow the guarantee that none of these 546 would not be broken by
> the update. ;-)

It's certainly possible that something breaks. But we can do a simple
test by trying to update our profiles and Guix System installations, and
checking that our tools still work. I think it's okay to cause a little
breakage in order to deploy important security updates.




  reply	other threads:[~2023-03-05 18:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 18:04 [bug#61583] [PATCH] gnu: git: Update to 2.39.2 [fixes CVE-2023-22490 & CVE-2023-23946] Greg Hogan
2023-02-20 11:44 ` Simon Tournier
2023-03-03 19:14   ` Simon Tournier
2023-03-03 19:33     ` Tobias Geerinckx-Rice via Guix-patches via
2023-03-04  3:39     ` Maxim Cournoyer
2023-03-04  3:44       ` Leo Famulari
2023-03-03 21:56   ` Leo Famulari
2023-03-04 10:30     ` Josselin Poiret via Guix-patches via
2023-03-04 14:41       ` Leo Famulari
2023-03-04 15:34         ` Tobias Geerinckx-Rice via Guix-patches via
2023-03-06 12:54           ` Maxim Cournoyer
2023-03-04 17:52         ` Josselin Poiret via Guix-patches via
2023-03-05 19:30           ` Leo Famulari
2023-03-04 18:52     ` Simon Tournier
2023-03-05 18:45       ` Leo Famulari [this message]
2023-03-05 19:27         ` Christopher Baines
2023-03-05 20:33         ` Simon Tournier
2023-03-06 17:23 ` bug#61583: " Leo Famulari
2023-03-08  9:50   ` [bug#61583] " Simon Tournier

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=ZATjZm3u26B1E7i6@jasmine.lan \
    --to=leo@famulari.name \
    --cc=61583@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=mail@cbaines.net \
    --cc=zimon.toutoune@gmail.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.