From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, 19805@debbugs.gnu.org,
Federico Beffa <beffa@ieee.org>
Subject: bug#19805: Numpy failures
Date: Tue, 10 Feb 2015 15:41:20 +0100 [thread overview]
Message-ID: <87wq3p6d7z.fsf__33272.3052044914$1423579338$gmane$org@gnu.org> (raw)
In-Reply-To: <877fvpswko.fsf@netris.org> (Mark H. Weaver's message of "Tue, 10 Feb 2015 08:52:23 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Federico Beffa <beffa@ieee.org> skribis:
>>
>>> At some point we should fix the support for '#:substitutable?' on hydra
>>
>> That probably means that #:substitutable? should be propagated–i.e.,
>> that anything depending on ATLAS should not be substituted.
>
> As I just wrote in the "texlive failure" thread, setting
> #:substitutable? #f might make sense for texlive. However, in that case
> we certainly would not want to propagate that setting.
>
> So, instead of propagating it, how about simply arranging to not send
> such packages to the build slaves, instead forcing them to build it
> locally on their own?
I think there are two properties of interest: “substitutability”, and
“offloadability”.
What do we want for ATLAS, for NumPy, and for TeX Live?
However, note that we can’t currently distinguish between these two
properties: <http://bugs.gnu.org/18747>.
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-02-10 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 16:41 Numpy failures Andreas Enge
2015-02-09 8:30 ` Federico Beffa
2015-02-09 23:07 ` bug#19805: " Ludovic Courtès
2015-02-10 13:20 ` Federico Beffa
2015-02-10 13:20 ` Federico Beffa
2015-02-10 13:52 ` Mark H Weaver
2015-02-10 14:41 ` Ludovic Courtès
2015-09-11 19:40 ` Ludovic Courtès
2015-02-10 14:41 ` Ludovic Courtès [this message]
2015-02-10 13:52 ` Mark H Weaver
2015-02-09 23:07 ` 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='87wq3p6d7z.fsf__33272.3052044914$1423579338$gmane$org@gnu.org' \
--to=ludo@gnu.org \
--cc=19805@debbugs.gnu.org \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.