From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [NOMERGE] libgit2: update to 1.1.0.
Date: Thu, 04 Feb 2021 06:52:47 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28456@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
There is a new pull request by ericonr against master on the void-packages repository
https://github.com/ericonr/void-packages libgit2
https://github.com/void-linux/void-packages/pull/28456
[NOMERGE] libgit2: update to 1.1.0.
Latest release from October, 2020, but it had some regressions regarding unaligned access, which I believe affect us.
See https://github.com/libgit2/libgit2/issues/5745
PR is open so hopefully anyone who searches for it is aware that it's not fully working right now. We could backport the specific patch for that issue, but I don't fully fancy it.
@q66 since your name is here :P
A patch file from https://github.com/void-linux/void-packages/pull/28456.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libgit2-28456.patch --]
[-- Type: text/x-diff, Size: 1131 bytes --]
From 36e42bf4e1065c9e6b1f04a9640b50fd203a3447 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Thu, 4 Feb 2021 02:49:45 -0300
Subject: [PATCH] libgit2: update to 1.1.0.
---
srcpkgs/libgit2/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libgit2/template b/srcpkgs/libgit2/template
index 16b611692eb..3dada2245c7 100644
--- a/srcpkgs/libgit2/template
+++ b/srcpkgs/libgit2/template
@@ -1,7 +1,7 @@
# Template file for 'libgit2'
pkgname=libgit2
-version=1.0.1
-revision=2
+version=1.1.0
+revision=1
build_style=cmake
hostmakedepends="python3 git pkg-config"
makedepends="zlib-devel libressl-devel http-parser-devel libssh2-devel"
@@ -10,7 +10,7 @@ maintainer="q66 <daniel@octaforge.org>"
license="custom:GPL-2.0-or-later WITH GCC-exception-2.0"
homepage="https://libgit2.org"
distfiles="https://github.com/libgit2/libgit2/archive/v${version}.tar.gz"
-checksum=1775427a6098f441ddbaa5bd4e9b8a043c7401e450ed761e69a415530fea81d2
+checksum=41a6d5d740fd608674c7db8685685f45535323e73e784062cf000a633d420d1e
post_install() {
vlicense COPYING
next reply other threads:[~2021-02-04 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 5:52 ericonr [this message]
2021-02-04 13:39 ` [PR PATCH] [Updated] " ericonr
2021-02-04 13:39 ` ericonr
2022-05-03 2:14 ` github-actions
2022-05-17 2:14 ` [PR PATCH] [Closed]: " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28456@inbox.vuxu.org \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).