From: Nikita Domnitskii via Guix-patches via <guix-patches@gnu.org>
To: 73374@debbugs.gnu.org
Subject: [bug#73374] [PATCH v2 2/3] gnu: pam-mount: Remove lvm2 from inputs.
Date: Thu, 31 Oct 2024 11:59:03 +0600 [thread overview]
Message-ID: <ec84b601ed2a9199ffd63f060726ba69c1e1121a.1730355663.git.nikita@domnitskii.me> (raw)
In-Reply-To: <cover.1730355663.git.nikita@domnitskii.me>
* gnu/packages/admin.scm (pam-mount): Remove lvm2 from inputs.
[inputs]: Remove lvm2.
Change-Id: I5730a4e5767a9cd99723155e5ba4d27e92f58786
---
gnu/packages/admin.scm | 1 -
1 file changed, 1 deletion(-)
diff --git a/gnu/packages/admin.scm b/gnu/packages/admin.scm
index 74b2054e60..7669d65dce 100644
--- a/gnu/packages/admin.scm
+++ b/gnu/packages/admin.scm
@@ -4953,7 +4953,6 @@ (define-public pam-mount
(list libhx
libxml2
linux-pam
- lvm2
openssl
pcre2
`(,util-linux "lib")
--
Best Regards,
Nikita Domnitskii
next prev parent reply other threads:[~2024-10-31 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 2:43 [bug#73374] [PATCH] gnu: pam-mount: fix libcryptsetup detection nathan via Guix-patches via
2024-10-31 6:21 ` [bug#73374] [PATCH v2 0/3] Fix and update pam-mount Nikita Domnitskii via Guix-patches via
2024-09-20 2:43 ` [bug#73374] [PATCH v2 1/3] gnu: pam-mount: Fix libcryptsetup detection Nikita Domnitskii via Guix-patches via
2024-10-31 5:47 ` [bug#73374] [PATCH v2 3/3] gnu: pam-mount: Update to 2.20 Nikita Domnitskii via Guix-patches via
2024-10-31 5:59 ` Nikita Domnitskii via Guix-patches via [this message]
2024-10-31 15:17 ` [bug#73374] [PATCH v3 0/2] Nikita Domnitskii via Guix-patches via
2024-09-20 2:43 ` [bug#73374] [PATCH v3 1/2] gnu: pam-mount: Fix libcryptsetup detection Nikita Domnitskii via Guix-patches via
2024-10-31 5:47 ` [bug#73374] [PATCH v3 2/2] gnu: pam-mount: Update to 2.20 Nikita Domnitskii via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec84b601ed2a9199ffd63f060726ba69c1e1121a.1730355663.git.nikita@domnitskii.me \
--to=guix-patches@gnu.org \
--cc=73374@debbugs.gnu.org \
--cc=nikita@domnitskii.me \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).