Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: pam-gnupg-git-20191206
Date: Thu, 16 Jan 2020 21:46:38 +0100	[thread overview]
Message-ID: <20200116204638.AgGCTsrM16ciIwwfz4EeeyY_HkreKWllPWSo4DWS2mY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18335@inbox.vuxu.org>

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

There is an updated pull request by ahesford against master on the void-packages repository

https://github.com/ahesford/void-packages master
https://github.com/void-linux/void-packages/pull/18335

New package: pam-gnupg-git-20191206
This template adds support for the pam-gnupg PAM module, which presets key passphrases in gnupg2 to the PAM authentication passphrase. Configuring PAM to load for authentication after the pam_unix module and session management after any elogind or ConsoleKit2 modules will pass the user's password through gpg-connect-agent to preset the passphrase; as a side effect, gpg-agent will be launched if it is not already running.

The template references a specific git commit, which is not allowed according to CONTRIBUTING.md; I'm hoping an exception can be made because the module author has not published specific releases but the module is very useful.

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

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

From 53913d43d75278ae7687b7ec0ce30a7a6ae2fb07 Mon Sep 17 00:00:00 2001
From: "Andrew J. Hesford" <ajh@sideband.org>
Date: Thu, 16 Jan 2020 14:38:00 -0500
Subject: [PATCH] New package: pam-gnupg-git-20191206

---
 srcpkgs/pam-gnupg-git/template | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 srcpkgs/pam-gnupg-git/template

diff --git a/srcpkgs/pam-gnupg-git/template b/srcpkgs/pam-gnupg-git/template
new file mode 100644
index 00000000000..f82b90eef5f
--- /dev/null
+++ b/srcpkgs/pam-gnupg-git/template
@@ -0,0 +1,21 @@
+# Template file for 'pam-gnupg-git'
+pkgname=pam-gnupg-git
+version=20191206
+revision=1
+_githash=fbd75b720877e4cf94e852ce7e2b811feb330bb5
+wrksrc="pam-gnupg-${_githash}"
+build_style=gnu-configure
+configure_args="--with-moduledir=/usr/lib/security"
+hostmakedepends="automake libtool gnupg2"
+makedepends="pam-devel"
+depends="gnupg2"
+short_desc="PAM module to unlock GPG agent on login"
+maintainer="Andrew J. Hesford <ajh@sideband.org>"
+license="GPL-3.0-only"
+homepage="https://github.com/cruegge/pam-gnupg"
+distfiles="${homepage}/archive/${_githash}.tar.gz"
+checksum=fe6d5874545832d9f0189f204571b19470bb090a3eac778732e5792b428cffa0
+
+pre_configure() {
+	sh autogen.sh
+}

  reply	other threads:[~2020-01-16 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 19:48 [PR PATCH] " voidlinux-github
2020-01-16 20:46 ` voidlinux-github [this message]
2020-01-18  3:24 ` [PR PATCH] [Merged]: " voidlinux-github

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=20200116204638.AgGCTsrM16ciIwwfz4EeeyY_HkreKWllPWSo4DWS2mY@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).