unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully via Guix-patches via <guix-patches@gnu.org>
To: 63149@debbugs.gnu.org
Cc: Brian Cully <bjc@spork.org>
Subject: [bug#63149] [PATCH] gnu: criu: Fix build
Date: Fri, 28 Apr 2023 10:04:25 -0400	[thread overview]
Message-ID: <d630b03419fa2c08cd6ccb58451ff13791f9013d.1682690665.git.bjc@spork.org> (raw)

Use python-toolchain explicitly in order to pull in our patched ZipFile
creation which ignores timestamp.

* gnu/packages/virtualization.scm (criu) [native-inputs]: Add python-toolchain.
---
 gnu/packages/virtualization.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/virtualization.scm b/gnu/packages/virtualization.scm
index 4a0d6b0096..d9fc8108dc 100644
--- a/gnu/packages/virtualization.scm
+++ b/gnu/packages/virtualization.scm
@@ -1748,7 +1748,6 @@ (define-public criu
                (for-each delete-file (find-files out "\\.a$"))))))))
     (inputs
      `(("protobuf" ,protobuf)
-       ("python" ,python)
        ("python-protobuf" ,python-protobuf)
        ("iproute" ,iproute)
        ("libaio" ,libaio)
@@ -1763,7 +1762,8 @@ (define-public criu
            asciidoc
            xmlto
            docbook-xml
-           docbook-xsl))
+           docbook-xsl
+           python-toolchain))
     (propagated-inputs
      ;; included by 'rpc.pb-c.h'
      (list protobuf-c))
-- 
2.39.2





             reply	other threads:[~2023-04-28 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 14:04 Brian Cully via Guix-patches via [this message]
2023-04-28 14:05 ` [bug#63149] [PATCH] gnu: criu: Fix build Brian Cully via Guix-patches via
2023-05-12 22:36 ` [bug#63149] [PATCH v2] " Brian Cully via Guix-patches via
2023-05-12 23:00   ` [bug#63149] [PATCH] " Brian Cully via Guix-patches via
2023-05-19 14:02   ` bug#63149: " 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

  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=d630b03419fa2c08cd6ccb58451ff13791f9013d.1682690665.git.bjc@spork.org \
    --to=guix-patches@gnu.org \
    --cc=63149@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 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).