From: Morgan.J.Smith@outlook.com
To: 61444@debbugs.gnu.org
Cc: Morgan Smith <Morgan.J.Smith@outlook.com>
Subject: [bug#61444] [PATCH] gnu: libnitrokey: Update to 3.8.
Date: Sat, 11 Feb 2023 22:59:26 -0500 [thread overview]
Message-ID: <CY4PR03MB3159E31EC394CE748FC2609EC5DC9@CY4PR03MB3159.namprd03.prod.outlook.com> (raw)
From: Morgan Smith <Morgan.J.Smith@outlook.com>
* gnu/packages/security-token.scm (libnitrokey): Update to 3.8.
---
I looked through the diff for 3.6 -> 3.8. It builds. nitrokey-app builds and
runs. I will admit I'm only doing this for the new udev rules though.
gnu/packages/security-token.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/security-token.scm b/gnu/packages/security-token.scm
index 619be42305..a7f5e3acf9 100644
--- a/gnu/packages/security-token.scm
+++ b/gnu/packages/security-token.scm
@@ -725,7 +725,7 @@ (define-public python-yubikey-manager
(define-public libnitrokey
(package
(name "libnitrokey")
- (version "3.6")
+ (version "3.8")
(source (origin
(method git-fetch)
(uri (git-reference
@@ -734,7 +734,7 @@ (define-public libnitrokey
(file-name (git-file-name name version))
(sha256
(base32
- "0ngrvv61d36vvfwrfg0qxmp2wg18v4aaldwvwzgxvwaysjswhn9r"))))
+ "1b95l979y353rli54a79z18iya9bza83cymcjpndr01q1pb134zm"))))
(build-system cmake-build-system)
(arguments
;; These tests do not require any device to be connected
@@ -743,7 +743,7 @@ (define-public libnitrokey
(inputs (list hidapi libusb))
(home-page "https://github.com/Nitrokey/libnitrokey")
(synopsis "Communication library for Nitrokey")
- (description "This packate provides communication library for Nitrokey.")
+ (description "This package provides a communication library for Nitrokey.")
(license license:lgpl3+)))
(define-public cppcodec
--
2.39.1
next reply other threads:[~2023-02-12 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 3:59 Morgan.J.Smith [this message]
2023-02-13 18:59 ` [bug#61444] [PATCH] gnu: libnitrokey: Update to 3.8 Christopher Baines
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=CY4PR03MB3159E31EC394CE748FC2609EC5DC9@CY4PR03MB3159.namprd03.prod.outlook.com \
--to=morgan.j.smith@outlook.com \
--cc=61444@debbugs.gnu.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.
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.