all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Leo Famulari" <leo@famulari.name>
To: "Josselin Poiret" <dev@jpoiret.xyz>, zimoun <zimon.toutoune@gmail.com>
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, 04 Mar 2023 09:41:08 -0500	[thread overview]
Message-ID: <18a9b3b3-3dc7-44bf-84a5-74cd4fab8984@app.fastmail.com> (raw)
In-Reply-To: <87ilfgreou.fsf@jpoiret.xyz>

On Sat, Mar 4, 2023, at 05:30, Josselin Poiret wrote:
> Hi Leo,
>
> Leo Famulari <leo@famulari.name> writes:
>
>> That's not a significant number of packages.
>>
>> Overall, git and git-minimal will cause more than 300 rebuilds, but not
>> too many for the current state of the build farm.
>>
>> Concretely, why can't we push this to master immediately?
>
> `guix refresh` is not great for core packages: it only detects things
> that depend on other packages through inputs. Here though, git is used
> indirectly by git-fetch origins, and would affect the dependency graph a
> lot more.  I think this should be grafted to avoid too many rebuilds,
> and ungrafted on core-updates (maybe now, maybe after the big
> core-updates merge).

Changing the Git package shouldn't affect fixed-output derivations that fetch from Git. If they do, that's a recent and very serious bug.

Git is a security critical package that we've always updated freely.

I'm AFK, only have my phone today . But, please try updating Git and check if the fixed-output source derivations change.

Leo




  reply	other threads:[~2023-03-04 14:42 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 [this message]
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
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=18a9b3b3-3dc7-44bf-84a5-74cd4fab8984@app.fastmail.com \
    --to=leo@famulari.name \
    --cc=61583@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=dev@jpoiret.xyz \
    --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.