From: Brian Cully via Guix-patches via <guix-patches@gnu.org>
To: 63091@debbugs.gnu.org
Cc: Brian Cully <bjc@spork.org>
Subject: [bug#63091] [PATCH v2 2/2] gnu: sssd: Fix build
Date: Fri, 28 Apr 2023 10:03:36 -0400 [thread overview]
Message-ID: <b6cb28fab9f30744fa6d411096291901c9e824e8.1682690616.git.bjc@spork.org> (raw)
In-Reply-To: <a86a2482a648192a34f23e833644ab5a41f0b81c.1682690616.git.bjc@spork.org>
Use python-toolchain explicitly in order to pull in our patched ZipFile
creation which ignores timestamp.
* gnu/packages/sssd.scm (sssd) [native-inputs]: Add python-toolchain.
---
gnu/packages/sssd.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/sssd.scm b/gnu/packages/sssd.scm
index 4e585a62de..47f5d1e559 100644
--- a/gnu/packages/sssd.scm
+++ b/gnu/packages/sssd.scm
@@ -266,7 +266,7 @@ (define-public sssd
p11-kit ; for PKCS#11 support
pcre2
popt
- python
+ python ; for wrap-program phase
samba/pinned
talloc
tdb
@@ -286,6 +286,7 @@ (define-public sssd
libxslt
openssh ; for tests
pkg-config
+ python-toolchain
po4a
softhsm ; for tests
`(,util-linux "lib"))) ; for uuid.h, reqired for KCM
--
2.39.2
next prev parent reply other threads:[~2023-04-28 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 14:58 [bug#63091] [PATCH] gnu: sssd: Fix failing tests by using samba/pinned input Brian Cully via Guix-patches via
2023-04-26 15:02 ` Brian Cully via Guix-patches via
2023-04-28 14:03 ` [bug#63091] [PATCH v2 1/2] " Brian Cully via Guix-patches via
2023-04-28 14:03 ` Brian Cully via Guix-patches via [this message]
2023-04-28 19:02 ` [bug#63091] [PATCH] " Ludovic Courtès
2023-04-28 19:14 ` Brian Cully via Guix-patches via
2023-05-04 1:14 ` [bug#63091] [PATCH v3 1/2] " Brian Cully via Guix-patches via
2023-05-04 1:14 ` [bug#63091] [PATCH v3 2/2] gnu: sssd: Fix build Brian Cully via Guix-patches via
2023-05-19 14:14 ` bug#63091: [PATCH] gnu: sssd: Fix failing tests by using samba/pinned input Ludovic Courtès
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=b6cb28fab9f30744fa6d411096291901c9e824e8.1682690616.git.bjc@spork.org \
--to=guix-patches@gnu.org \
--cc=63091@debbugs.gnu.org \
--cc=bjc@spork.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.
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.