Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] minisign: update to 0.11.
Date: Wed, 25 Jan 2023 14:32:53 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41863@inbox.vuxu.org> (raw)

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

There is a new pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages minisign
https://github.com/void-linux/void-packages/pull/41863

minisign: update to 0.11.
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture: **x86_64**

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

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

From 97fc34a67c676388e784b496898b4835c5551fbc Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Wed, 25 Jan 2023 15:20:31 +0530
Subject: [PATCH] minisign: update to 0.11.

---
 srcpkgs/minisign/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/minisign/template b/srcpkgs/minisign/template
index a96a13970599..f2ed9a6f748d 100644
--- a/srcpkgs/minisign/template
+++ b/srcpkgs/minisign/template
@@ -1,16 +1,16 @@
 # Template file for 'minisign'
 pkgname=minisign
-version=0.10
+version=0.11
 revision=1
 build_style=cmake
 hostmakedepends="pkg-config"
 makedepends="libsodium-devel"
 short_desc="Simple tool to sign files and verify signatures"
 maintainer="Orphaned <orphan@voidlinux.org>"
-license="MIT"
+license="ISC"
 homepage="https://jedisct1.github.io/minisign"
-distfiles="https://github.com/jedisct1/minisign/archive/${version}.tar.gz"
-checksum=9fe40c2bd899a91f6b62a6ff3d469ece670f155307df50c2482ddd31337ab6da
+distfiles="https://github.com/jedisct1/minisign/archive/refs/tags/${version}.tar.gz"
+checksum=74c2c78a1cd51a43a6c98f46a4eabefbc8668074ca9aa14115544276b663fc55
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2023-01-25 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 13:32 icp1994 [this message]
2023-02-14 20:07 ` [PR REVIEW] " paper42
2023-02-14 20:09 ` [PR PATCH] [Updated] " icp1994
2023-02-14 20:15 ` [PR PATCH] [Merged]: " paper42

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-41863@inbox.vuxu.org \
    --to=icp1994@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).