From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54611-done@debbugs.gnu.org
Subject: bug#54611: [WIP PATCH] gnu: Update libgit2 to 1.4.2
Date: Wed, 11 May 2022 23:56:45 +0200 [thread overview]
Message-ID: <87o803n36q.fsf_-_@gnu.org> (raw)
In-Reply-To: <e27cb0a8f0f19970fd0440df16b49634d1dbf989.camel@telenet.be> (Maxime Devos's message of "Thu, 31 Mar 2022 19:11:08 +0200")
Hi Maxime,
Maxime Devos <maximedevos@telenet.be> skribis:
> From a7df2fe70f38cfb53084e1bea14e90836fa8caa5 Mon Sep 17 00:00:00 2001
> From: Maxime Devos <maximedevos@telenet.be>
> Date: Thu, 31 Mar 2022 16:34:47 +0000
> Subject: [PATCH] gnu: libgit2: Update to 1.4.2.
>
> * gnu/packages/version-control.scm (libgit2)
> [version]: Update to 1.4.2.
> [arguments]<#:configure-flags>: Explicitly enable SSH support.
> [arguments]<#:phases>{check}: Adjust to new test runner name.
> [arguments]<#:phases>{fix-hardcoded-paths}: Remove obsolete phase.
I started from this patch, bumped to 1.4.3, adjusted for the
time-dependent test, adjusted ‘libgit2-1.1’, introduced ‘libgit2-1.3’
for use in packages that can’t switch to 1.4, etc.
Pushed as e764b89a52171fd5ff6d22fdb562ceb60ec6a50a.
Let me know if you notice anything wrong!
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-05-11 21:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 13:12 [bug#54611] [WIP PATCH] gnu: Update libgit2 to 1.4.2 Maxime Devos
2022-03-29 20:30 ` Maxime Devos
2022-03-31 17:11 ` Maxime Devos
2022-04-01 14:43 ` Maxime Devos
2022-04-01 14:57 ` Maxime Devos
2022-04-02 4:23 ` Thiago Jung Bauermann via Guix-patches via
2022-04-01 15:05 ` Maxime Devos
2022-04-01 15:09 ` Maxime Devos
2022-04-02 4:07 ` Thiago Jung Bauermann via Guix-patches via
2022-05-11 21:56 ` Ludovic Courtès [this message]
2022-05-12 6:44 ` Maxime Devos
2022-04-02 1:59 ` Reviewing the diff when updating a package? Thiago Jung Bauermann
2022-04-02 8:27 ` Maxime Devos
2022-04-02 21:48 ` Thiago Jung Bauermann
2022-04-05 12:34 ` Ludovic Courtès
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=87o803n36q.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=54611-done@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.