unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Aaron Covrig via Guix-patches via <guix-patches@gnu.org>
To: 74664@debbugs.gnu.org
Cc: Ashish SHUKLA <ashish.is@lostca.se>
Subject: [bug#74664] [PATCH] gnu: libgit2: Update to 1.8.4.
Date: Wed,  4 Dec 2024 22:02:08 -0500	[thread overview]
Message-ID: <20241205030401.1994615-1-aaron.covrig.us@ieee.org> (raw)
In-Reply-To: <d9b7f4576f162a5b2231895bbae008d8e3e87b11.1733221230.git.ashish.is@lostca.se>

From: Ashish SHUKLA <ashish.is@lostca.se>

* gnu/packages/version-control.scm (libgit2-1.8): Update to 1.8.4.
---
I went ahead and re-applied/rebased your commit, for some reason
it seems it looks like it was applied against a different base or
master just received a bunch of changes.

 gnu/packages/version-control.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
index 289b981911..333548d54f 100644
--- a/gnu/packages/version-control.scm
+++ b/gnu/packages/version-control.scm
@@ -1174,7 +1174,7 @@ (define-public libgit2-1.7
 (define-public libgit2-1.8
   (package
     (inherit libgit2-1.7)
-    (version "1.8.3")
+    (version "1.8.4")
     (source (origin
               (inherit (package-source libgit2-1.7))
               (uri (git-reference
@@ -1183,7 +1183,7 @@ (define-public libgit2-1.8
               (file-name (git-file-name "libgit2" version))
               (sha256
                (base32
-                "11jyxy6ckl19ayqpq5s3nlbcd0s1q4sdy8884m4pjrbzgxg6y1ds"))
+                "0jydckwn0bbrp2kbcr1ih1bz4sc6yhx7lrl22lqcgnf2v6ml6n01"))
               (patches
                (search-patches "libgit2-uninitialized-proxy-settings.patch"))
 	      (snippet

base-commit: 006679d1e6ca7acea0629b4f019c8cf89cde08be
-- 
2.47.0





  reply	other threads:[~2024-12-05  3:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 10:20 [bug#74664] [PATCH] gnu: libgit2: Update to 1.8.4 ashish.is--- via Guix-patches via
2024-12-05  3:02 ` Aaron Covrig via Guix-patches via [this message]
2024-12-06 22:25 ` [bug#74664] [PATCH v3] " Aaron Covrig via Guix-patches via
2024-12-07  1:06 ` [bug#74664] CI seems to be building against old commit Aaron Covrig via Guix-patches via
2024-12-07  1:08 ` [bug#74664] [PATCH v4] gnu: libgit2: Update to 1.8.4 Aaron Covrig via Guix-patches via
2024-12-14  0:15 ` [bug#74664] [PATCH v5] " Aaron Covrig via Guix-patches via

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=20241205030401.1994615-1-aaron.covrig.us@ieee.org \
    --to=guix-patches@gnu.org \
    --cc=74664@debbugs.gnu.org \
    --cc=aaron.covrig.us@ieee.org \
    --cc=ashish.is@lostca.se \
    /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).