From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 61684@debbugs.gnu.org
Subject: bug#61684: can't compose 'with-patch' with 'with-source'
Date: Fri, 03 Mar 2023 10:43:04 +0100 [thread overview]
Message-ID: <87h6v2187r.fsf@gnu.org> (raw)
In-Reply-To: <877cw7go5k.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 24 Feb 2023 08:59:19 -0500")
Hi Maxim,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> Unfortunately the source derivation fails because it attempts to apply a
> patch (a single one?) to a tarball:
>
> (begin
> (use-modules
> (guix build utils))
> (setenv "PATH" "/gnu/store/mp0syh29rjknflaiv0hkpdlb2mjk0rlx-patch-2.7.6/bin")
> (copy-recursively "/gnu/store/ig8awlxbzrasp9p4f9vq8fqcidrma5qj-jami-20230224.0.tar.gz"
> ((@
> (guile)
> getenv)
> "out"))
> (chdir
> ((@
> (guile)
> getenv)
> "out"))
> (for-each
> (lambda
> (patch)
> (invoke "patch" "-p1" "--batch" "-i" patch))
> (quote
> ("/gnu/store/iq7hd3f9kr2kvz7lvnygq51yxp85gxbn-jami-libjami-headers-search.patch"))))
That’s a bug we should fix (and indeed, ‘patched-source’ has an XXX
comment about it…).
Ludo’.
prev parent reply other threads:[~2023-03-03 9:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 18:08 bug#61684: can't compose 'with-patch' with 'with-source' Maxim Cournoyer
2023-02-21 19:05 ` Simon Tournier
2023-02-23 14:08 ` Ludovic Courtès
2023-02-23 22:27 ` Maxim Cournoyer
2023-02-24 12:02 ` Simon Tournier
2023-02-24 13:21 ` Maxim Cournoyer
2023-02-24 13:43 ` Simon Tournier
2023-02-24 13:52 ` Maxim Cournoyer
2023-02-25 12:29 ` Simon Tournier
2023-02-25 19:43 ` Maxim Cournoyer
2023-02-27 14:12 ` Ludovic Courtès
2023-02-27 16:29 ` Maxim Cournoyer
2023-02-27 14:09 ` Ludovic Courtès
2023-02-28 10:00 ` Simon Tournier
2023-03-01 15:49 ` Ludovic Courtès
2023-02-24 13:59 ` Maxim Cournoyer
2023-03-03 9:43 ` Ludovic Courtès [this message]
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=87h6v2187r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=61684@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.