all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 61583@debbugs.gnu.org, Greg Hogan <code@greghogan.com>
Subject: [bug#61583] [PATCH] gnu: git: Update to 2.39.2 [fixes CVE-2023-22490 & CVE-2023-23946].
Date: Sat, 4 Mar 2023 19:52:04 +0100	[thread overview]
Message-ID: <CAJ3okZ3dxoyHKoi0QVikKyanNz9xDCWU7b6WcF73N8J31bmLxQ@mail.gmail.com> (raw)
In-Reply-To: <ZAJtKtBBc+tZeBlX@jasmine.lan>

Hi,

On Fri, 3 Mar 2023 at 22:57, Leo Famulari <leo@famulari.name> wrote:

> Overall, git and git-minimal will cause more than 300 rebuilds, but not
> too many for the current state of the build farm.

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>.

> 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. ;-)

Anyway, I had locally built them -- it took 3-4 days on my machine,
IIRC -- and I do not remember any "big" breakage, maybe a couple of
packages -- even maybe not since some are already broken.  However, I
did not carefully tracked my process thinking to come back later --
well, I ran "guix gc" in the mean for checking stuff with SWH coverage
thinking that QA would have finished.

I do not have an opinion where or whether to push.

Cheers,
simon




  parent reply	other threads:[~2023-03-04 18:53 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 [this message]
2023-03-05 18:45       ` Leo Famulari
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=CAJ3okZ3dxoyHKoi0QVikKyanNz9xDCWU7b6WcF73N8J31bmLxQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=61583@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=leo@famulari.name \
    /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.