Github messages for voidlinux
 help / color / mirror / Atom feed
From: furryfixer <furryfixer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] xdm.pam: update for elogind support
Date: Sat, 12 Dec 2020 06:54:58 +0100	[thread overview]
Message-ID: <20201212055458.lZ_DBrWFCMlhgoLCCyYi1LaIaKevFUONmfoYJy4uFTU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27099@inbox.vuxu.org>

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

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

https://github.com/furryfixer/void-packages patch-1
https://github.com/void-linux/void-packages/pull/27099

xdm.pam: update for elogind support
Add optional access to "pam_elogind.so" to prevent polkit agent malfunction in multiple Desktop Environments if started from xdm.

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

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

From bcc285499f76baf3e4e5704279fe7f6a86d45082 Mon Sep 17 00:00:00 2001
From: William Rueger <spammer.victim@gmail.com>
Date: Fri, 11 Dec 2020 22:22:49 -0500
Subject: [PATCH 1/2] xdm.pam: update for elogind support

Add optional access to "pam_elogind.so" to prevent polkit agent malfunction in multiple Desktop Environments if started from xdm.
---
 srcpkgs/xdm/files/xdm.pam | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/xdm/files/xdm.pam b/srcpkgs/xdm/files/xdm.pam
index 06f88746d3d..8c243370d68 100644
--- a/srcpkgs/xdm/files/xdm.pam
+++ b/srcpkgs/xdm/files/xdm.pam
@@ -6,3 +6,4 @@ password	required	pam_unix.so
 session		required	pam_unix.so
 session		required	pam_limits.so
 session		required	pam_loginuid.so
+session        optional        pam_elogind.so

From fefd0c45008bc24c771f25ecc329096f0c3c68d5 Mon Sep 17 00:00:00 2001
From: William Rueger <spammer.victim@gmail.com>
Date: Sat, 12 Dec 2020 00:53:25 -0500
Subject: [PATCH 2/2] xdm: Add elogind support to xdm.pam file

Add optional access to "pam_elogind.so" to prevent polkit agent malfunction in multiple Desktop Environments if started from xdm.
---
 srcpkgs/xdm/template | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/srcpkgs/xdm/template b/srcpkgs/xdm/template
index 2c723ddd5d4..cf3d1de3f8d 100644
--- a/srcpkgs/xdm/template
+++ b/srcpkgs/xdm/template
@@ -1,7 +1,7 @@
 # Template file for 'xdm'
 pkgname=xdm
 version=1.1.12
-revision=3
+revision=4
 build_style=gnu-configure
 configure_args="--with-random-device=/dev/urandom
  --with-utmp-file=/var/run/utmp

  parent reply	other threads:[~2020-12-12  5:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12  3:27 [PR PATCH] " furryfixer
2020-12-12  3:54 ` [PR REVIEW] " ericonr
2020-12-12  3:55 ` ericonr
2020-12-12  5:13 ` furryfixer
2020-12-12  5:53 ` [PR PATCH] [Updated] " furryfixer
2020-12-12  5:54 ` furryfixer [this message]
2020-12-17 18:44 ` [PR REVIEW] xdm: update xdm.pam file with " ericonr
2020-12-17 19:05 ` furryfixer
2020-12-17 19:15 ` ericonr
2020-12-17 23:57 ` furryfixer
2020-12-19  6:21 ` [PR PATCH] [Closed]: " ericonr

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=20201212055458.lZ_DBrWFCMlhgoLCCyYi1LaIaKevFUONmfoYJy4uFTU@z \
    --to=furryfixer@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).