From: crater2150 <crater2150@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pam_yubico: update to 2.27.
Date: Tue, 24 Oct 2023 14:13:09 +0200 [thread overview]
Message-ID: <20231024121309.edFHl7I4OOkHnlcNEJwCEWUWImr0SjvFdee8jLz9z2w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46867@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
There is an updated pull request by crater2150 against master on the void-packages repository
https://github.com/crater2150/void-packages update-pam_yubico
https://github.com/void-linux/void-packages/pull/46867
pam_yubico: update to 2.27.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/46867.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-pam_yubico-46867.patch --]
[-- Type: text/x-diff, Size: 1168 bytes --]
From fe53a07c0f30d66eb69e3223de0da836d6bef2cc Mon Sep 17 00:00:00 2001
From: Alexander Gehrke <void@qwertyuiop.de>
Date: Tue, 24 Oct 2023 14:03:08 +0200
Subject: [PATCH] pam_yubico: update to 2.27.
---
srcpkgs/pam_yubico/template | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/pam_yubico/template b/srcpkgs/pam_yubico/template
index 1051f1558ec789..0c1b3a924f655a 100644
--- a/srcpkgs/pam_yubico/template
+++ b/srcpkgs/pam_yubico/template
@@ -1,6 +1,6 @@
# Template file for 'pam_yubico'
pkgname=pam_yubico
-version=2.26
+version=2.27
revision=1
build_style=gnu-configure
configure_args="--disable-static --disable-silent-rules"
@@ -11,7 +11,7 @@ maintainer="Alexander Gehrke <void@qwertyuiop.de>"
license="BSD-2-Clause"
homepage="https://developers.yubico.com/yubico-pam"
distfiles="https://developers.yubico.com/yubico-pam/Releases/${pkgname}-${version}.tar.gz"
-checksum=2de96495963fefd72b98243952ca5d5ec513e702c596e54bc667ef6b5e252966
+checksum=63d02788852644d871746e1a7a1d16c272c583c226f62576f5ad232a6a44e18c
do_check() {
# Recieves SIGKILL
@@ -21,4 +21,3 @@ do_check() {
post_install() {
vlicense COPYING
}
-
next prev parent reply other threads:[~2023-10-24 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 12:07 [PR PATCH] " crater2150
2023-10-24 12:13 ` crater2150 [this message]
2023-10-25 13:13 ` [PR PATCH] [Merged]: " Piraty
-- strict thread matches above, loose matches on Subject: below --
2021-05-15 9:36 [PR PATCH] " UsernameRandomlyGenerated
2021-05-15 9:39 ` [PR PATCH] [Updated] " UsernameRandomlyGenerated
2021-05-18 11:55 ` UsernameRandomlyGenerated
2021-05-22 10:00 ` UsernameRandomlyGenerated
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=20231024121309.edFHl7I4OOkHnlcNEJwCEWUWImr0SjvFdee8jLz9z2w@z \
--to=crater2150@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).