From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libnitrokey: update to 3.8.
Date: Wed, 01 Mar 2023 02:30:35 +0100 [thread overview]
Message-ID: <20230301013035.j4rzfbVXW0R_AWN6nLBaWDK09ZFSXH9X-thyGXr0wZ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42412@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
There is an updated pull request by sgn against master on the void-packages repository
https://github.com/atisharma/void-packages libnitrokey-v3.8
https://github.com/void-linux/void-packages/pull/42412
libnitrokey: update to 3.8.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv6l
A patch file from https://github.com/void-linux/void-packages/pull/42412.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libnitrokey-v3.8-42412.patch --]
[-- Type: text/x-diff, Size: 1273 bytes --]
From 046a1b5e611f7d25efc7bbc235e92595d825e1d7 Mon Sep 17 00:00:00 2001
From: Ati Sharma <ati@agalmic.ltd>
Date: Thu, 23 Feb 2023 15:54:40 +0000
Subject: [PATCH] libnitrokey: update to 3.8.
---
srcpkgs/libnitrokey/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/libnitrokey/template b/srcpkgs/libnitrokey/template
index 16860572431d..da0c2c49137c 100644
--- a/srcpkgs/libnitrokey/template
+++ b/srcpkgs/libnitrokey/template
@@ -1,16 +1,16 @@
# Template file for 'libnitrokey'
pkgname=libnitrokey
-version=3.5
+version=3.8
revision=1
build_style=cmake
hostmakedepends="pkg-config"
makedepends="hidapi-devel"
short_desc="Communicate with Nitrokey devices in a clean and easy manner"
maintainer="Julio Galvan <juliogalvan@protonmail.com>"
-license="LGPL-3.0"
+license="LGPL-3.0-only"
homepage="https://github.com/Nitrokey/libnitrokey"
-distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=d836f2f20c5b24088542da445893ef0a04834dca7dd8eef020e793de0601bb5a
+distfiles="https://github.com/Nitrokey/libnitrokey/releases/download/v${version}/libnitrokey-v${version}.tar.gz"
+checksum=3b7ebcfc47b2c45313bc5f17842f0160cbaf87f41d2621af18c5b56837e393a1
libnitrokey-devel_package() {
short_desc+=" - development files"
next prev parent reply other threads:[~2023-03-01 1:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 16:01 [PR PATCH] " atisharma
2023-02-23 16:02 ` atisharma
2023-02-23 16:41 ` [PR PATCH] [Updated] " atisharma
2023-02-23 16:44 ` atisharma
2023-02-23 19:12 ` [PR REVIEW] " mhmdanas
2023-02-23 19:52 ` [PR PATCH] [Updated] " atisharma
2023-02-23 19:54 ` atisharma
2023-02-24 11:16 ` atisharma
2023-02-24 13:43 ` mhmdanas
2023-02-24 14:47 ` [PR PATCH] [Updated] " atisharma
2023-03-01 1:30 ` sgn [this message]
2023-03-01 1:30 ` [PR PATCH] [Merged]: " sgn
2023-03-01 7:44 ` paper42
2023-03-01 11:21 ` atisharma
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=20230301013035.j4rzfbVXW0R_AWN6nLBaWDK09ZFSXH9X-thyGXr0wZ8@z \
--to=sgn@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).