From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Tropin <andrew@trop.in>
Cc: 53468-done@debbugs.gnu.org
Subject: bug#53468: [RFC PATCH] gnu: linux-pam: Change path to unix_chkpwd helper.
Date: Thu, 10 Feb 2022 23:42:29 +0100 [thread overview]
Message-ID: <8735kq2vje.fsf_-_@gnu.org> (raw)
In-Reply-To: <878ruo60c9.fsf@trop.in> (Andrew Tropin's message of "Sun, 06 Feb 2022 08:16:54 +0300")
Hi,
Andrew Tropin <andrew@trop.in> skribis:
> From e96d3f6d82b134829fcb31777e81928c73847dcc Mon Sep 17 00:00:00 2001
> From: Andrew Tropin <andrew@trop.in>
> Date: Sun, 6 Feb 2022 08:13:49 +0300
> Subject: [PATCH v3] gnu: linux-pam: Change path to unix_chkpwd helper.
>
> * gnu/packages/patches/change-path-to-unix_chkpwd.patch: New file.
> * gnu/packages/linux.scm (linux-pam): Add patch.
> * gnu/system/pam.scm (pam-root-service-type): Add unix_chkpwd to setuid.
LGTM, minor the patch file name as reported by ‘guix lint’ and missing
‘gnu/local.mk’.
However, it looks like my brain wasn’t fully operational when I
previously replied, because:
--8<---------------cut here---------------start------------->8---
$ guix refresh -l linux-pam
Building the following 2418 packages would ensure 6038 dependent
packages are rebuilt: […]
--8<---------------cut here---------------end--------------->8---
So I went ahead, fixed up the issues above, and pushed to
‘core-updates’.
Thanks!
Ludo’.
next prev parent reply other threads:[~2022-02-10 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 18:41 [bug#53468] [RFC PATCH] gnu: linux-pam: Change path to unix_chkpwd helper Andrew Tropin
2022-01-23 14:08 ` Andrew Tropin
2022-02-04 11:07 ` Andrew Tropin
2022-02-04 22:10 ` Ludovic Courtès
2022-02-06 5:16 ` Andrew Tropin
2022-02-10 22:42 ` Ludovic Courtès [this message]
2022-02-26 7:11 ` Andrew Tropin
2022-02-27 22:03 ` Ludovic Courtès
2023-03-03 23:33 ` wolf
2023-03-07 17:57 ` Leo Famulari
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=8735kq2vje.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=53468-done@debbugs.gnu.org \
--cc=andrew@trop.in \
/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.