From: ardadem <ardadem@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pam_wrapper: update to 1.1.4.
Date: Wed, 16 Feb 2022 21:35:52 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35656@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
There is a new pull request by ardadem against master on the void-packages repository
https://github.com/ardadem/void-packages pr-pam-wrapper
https://github.com/void-linux/void-packages/pull/35656
pam_wrapper: update to 1.1.4.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/35656.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pr-pam-wrapper-35656.patch --]
[-- Type: text/x-diff, Size: 1143 bytes --]
From 228095957e4d0820c81d34fc548102cec34170a6 Mon Sep 17 00:00:00 2001
From: Arda Demir <ddmirarda@gmail.com>
Date: Wed, 16 Feb 2022 23:29:49 +0300
Subject: [PATCH] pam_wrapper: update to 1.1.4.
---
srcpkgs/pam_wrapper/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/pam_wrapper/template b/srcpkgs/pam_wrapper/template
index e7c7c1f97d9f..c646d1713175 100644
--- a/srcpkgs/pam_wrapper/template
+++ b/srcpkgs/pam_wrapper/template
@@ -1,7 +1,7 @@
# Template file for 'pam_wrapper'
pkgname=pam_wrapper
-version=1.1.3
-revision=2
+version=1.1.4
+revision=1
build_style=cmake
configure_args="-DCMAKE_BUILD_TYPE=None -DUNIT_TESTING=ON"
hostmakedepends="cmake python3"
@@ -11,7 +11,7 @@ maintainer="Đoàn Trần Công Danh <congdanhqx@gmail.com>"
license="GPL-3.0-or-later"
homepage="https://cwrap.org/pam_wrapper.html"
distfiles="https://www.samba.org/ftp/cwrap/pam_wrapper-${version}.tar.gz"
-checksum=4feedd788c6fa36516f6d6060482cd86455998d72849eb5f539de48915bdc5f3
+checksum=ce31bb2fb8e1dc91d8f05ce585134753e46c768fb4a614a3b97882bdee1907b2
lib32disabled=yes
python3-pypamtest_package() {
next reply other threads:[~2022-02-16 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 20:35 ardadem [this message]
2022-03-13 0:54 ` [PR PATCH] [Closed]: " ahesford
2022-03-13 0:54 ` 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35656@inbox.vuxu.org \
--to=ardadem@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).