Github messages for voidlinux
 help / color / mirror / Atom feed
From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] sparsehash: update to 2.0.4.
Date: Sun, 20 Sep 2020 10:44:43 +0200	[thread overview]
Message-ID: <20200920084443.Dh7VL3K_rkWomZ8T3hca4Zjgy-0ouQ1eNAlH2_D8dok@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24863@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 327 bytes --]

There is an updated pull request by ailiop-git against master on the void-packages repository

https://github.com/ailiop-git/void-packages sparsehash
https://github.com/void-linux/void-packages/pull/24863

sparsehash: update to 2.0.4.


A patch file from https://github.com/void-linux/void-packages/pull/24863.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-sparsehash-24863.patch --]
[-- Type: text/x-diff, Size: 1204 bytes --]

From 2688b0769cf7a821d244bcd97465aac0412cb99f Mon Sep 17 00:00:00 2001
From: Anthony Iliopoulos <ailiop@altatus.com>
Date: Sun, 20 Sep 2020 10:44:13 +0200
Subject: [PATCH] sparsehash: update to 2.0.4.

---
 srcpkgs/sparsehash/template | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/sparsehash/template b/srcpkgs/sparsehash/template
index b6e1725d3a3..ba9b6c009d4 100644
--- a/srcpkgs/sparsehash/template
+++ b/srcpkgs/sparsehash/template
@@ -1,16 +1,15 @@
 # Template file for 'sparsehash'
 pkgname=sparsehash
-version=2.0.3
+version=2.0.4
 revision=1
-archs=noarch
+wrksrc="${pkgname}-${pkgname}-${version}"
 build_style=gnu-configure
 short_desc="Library that contains several hash-map implementations"
 maintainer="Orphaned <orphan@voidlinux.org>"
-license="BSD"
+license="BSD-3-Clause"
 homepage="https://github.com/sparsehash/sparsehash"
 distfiles="https://github.com/sparsehash/sparsehash/archive/${pkgname}-${version}.tar.gz"
-checksum=05e986a5c7327796dad742182b2d10805a8d4f511ad090da0490f146c1ff7a8c
-wrksrc="${pkgname}-${pkgname}-${version}"
+checksum=8cd1a95827dfd8270927894eb77f62b4087735cbede953884647f16c521c7e58
 
 post_install() {
 	vlicense COPYING

  reply	other threads:[~2020-09-20  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12 17:45 [PR PATCH] " ailiop-git
2020-09-20  8:44 ` ailiop-git [this message]
2020-09-22  1:36 ` [PR PATCH] [Merged]: " ahesford

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=20200920084443.Dh7VL3K_rkWomZ8T3hca4Zjgy-0ouQ1eNAlH2_D8dok@z \
    --to=ailiop-git@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).