From: ludo@gnu.org (Ludovic Courtès)
To: Kei Kebreau <kkebreau@posteo.net>
Cc: 28384@debbugs.gnu.org
Subject: [bug#28384] [PATCH] gnu: Fix build failures caused by commit.
Date: Fri, 08 Sep 2017 22:33:27 +0200 [thread overview]
Message-ID: <87efrh9bhk.fsf@gnu.org> (raw)
In-Reply-To: <87377xdtwy.fsf@posteo.net> (Kei Kebreau's message of "Fri, 08 Sep 2017 12:41:49 -0400")
Kei Kebreau <kkebreau@posteo.net> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hi Kei,
>>
>> The subject is truncated. :-) Caused by which commit?
>>
>> Kei Kebreau <kkebreau@posteo.net> skribis:
>>
>>> * gnu/packages/bioinformatics.scm (seek)[arguments]: Modify unpack phase.
>>> * gnu/packages/ci.scm (cuirass)[arguments]: Add patch-/bin/sh phase.
>>
>> This is weird, normally the ‘patch-source-shebangs’ phase, which happens
>> right before ‘configure’, should take care of these, no?
>>
>
> Normally the 'patch-source-shebangs' does just that, but in this case
> the script needs to be patched because the bootstrapping phase depends
> on perl.
OK. I don’t understand at what point this became necessary though.
> From 87ea8addad973568d8599fb93c8df9766b96b6a1 Mon Sep 17 00:00:00 2001
> From: Kei Kebreau <kkebreau@posteo.net>
> Date: Sat, 29 Jul 2017 11:28:42 -0400
> Subject: [PATCH] gnu: Use 'modify-phases' syntax.
> To: guix-patches@gnu.org
Wrong patch. :-)
Ludo’.
next prev parent reply other threads:[~2017-09-08 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 16:43 [bug#28384] [PATCH] gnu: Fix build failures caused by commit Kei Kebreau
2017-09-08 15:43 ` Ludovic Courtès
2017-09-08 16:41 ` Kei Kebreau
2017-09-08 20:33 ` Ludovic Courtès [this message]
2017-09-08 22:10 ` Kei Kebreau
2017-09-10 12:53 ` Ludovic Courtès
2017-09-10 13:32 ` Kei Kebreau
2017-09-10 20:39 ` Ludovic Courtès
2017-09-10 22:26 ` bug#28384: " Kei Kebreau
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=87efrh9bhk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28384@debbugs.gnu.org \
--cc=kkebreau@posteo.net \
/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).