From: Simon Tournier <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
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 21:33:20 +0100 [thread overview]
Message-ID: <CAJ3okZ2topeJmVoEidBR1JAT6BmLjSDYXyhkK8vP+8cHU=nfrg@mail.gmail.com> (raw)
In-Reply-To: <ZATjZm3u26B1E7i6@jasmine.lan>
Hi Leo,
On Sun, 5 Mar 2023 at 19:46, Leo Famulari <leo@famulari.name> wrote:
> 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.
Ah thanks! I always forgot that limit. :-) I mean, since it says
"not yet processed", I still think the limit is higher. ;-) Anyway.
> For the Berlin server, I don't think that 546 builds is too many, at
> least for Intel systems.
Indeed. Just to note that the last update of Git was by commit:
--8<---------------cut here---------------start------------->8---
51f8a7aced70b7f79037bd99019dddaea07ced25
Author: Tobias Geerinckx-Rice <me@tobias.gr>
AuthorDate: Sun Jan 15 01:00:03 2023 +0100
Commit: Tobias Geerinckx-Rice <me@tobias.gr>
CommitDate: Sun Jan 15 01:00:08 2023 +0100
gnu: git: Update to 2.39.1 [fixes CVE-2022-41903 & CVE-2022-23521].
* gnu/packages/version-control.scm (git): Update to 2.39.1.
Reported by HexMachina in #guix.
--8<---------------cut here---------------end--------------->8---
and all was fine...
> > 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.
...but it was not with the previous,
--8<---------------cut here---------------start------------->8---
83ede5a02e1fc531d912eb92eb0a22a4b897997c
Author: Greg Hogan <code@greghogan.com>
AuthorDate: Wed Oct 19 20:13:15 2022 +0000
Commit: Ludovic Courtès <ludo@gnu.org>
CommitDate: Tue Nov 8 14:06:00 2022 +0100
gnu: git: Update to 2.38.1.
Fixes CVE-2022-39253 and CVE-2022-39260.
* gnu/packages/version-control.scm (git): Update to 2.38.1.
Co-authored-by: Ludovic Courtès <ludo@gnu.org>
--8<---------------cut here---------------end--------------->8---
which had broken part of the Julia ecosystem; now the same problem
cannot arise for Julia. Who knows for the others? Anyway, I did this
rebuild and I did not noticed large breaks.
> > > Concretely, why can't we push this to master immediately?
Since we agree it is fine for master, feel free to push. :-)
Cheers,
simon
next prev parent reply other threads:[~2023-03-05 20:34 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
2023-03-05 19:27 ` Christopher Baines
2023-03-05 20:33 ` Simon Tournier [this message]
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='CAJ3okZ2topeJmVoEidBR1JAT6BmLjSDYXyhkK8vP+8cHU=nfrg@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=61583@debbugs.gnu.org \
--cc=code@greghogan.com \
--cc=leo@famulari.name \
--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 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.