unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 24833-done@debbugs.gnu.org
Subject: bug#24833: Hydra ignores MIPS-specific patch for Mesa on core-updates
Date: Thu, 03 Nov 2016 11:29:33 +0100	[thread overview]
Message-ID: <87zilgx3ea.fsf@gnu.org> (raw)
In-Reply-To: <87eg2ttis5.fsf@netris.org> (Mark H. Weaver's message of "Wed, 02 Nov 2016 22:10:50 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès)
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> Commit f1267c872fcaed6c53d43b3ff51abb726f7418d6 on core-updates added a
>>> patch to Mesa on MIPS only, in order to prevent unnecessary rebuilds on
>>> other systems.  'guix' running on a MIPS system generates a derivation
>>> that applies the patch, but the derivation generated for MIPS on Hydra
>>> omits the patch.
>>
>> Did it turn out to be the same issue as <http://bugs.gnu.org/24833>, or
>> is it something entirely different?
>
> Bug 24833 is this bug, so yes, by reflexivity it's the same issue, but I
> suspect that's not what you meant to ask :)

Arf, sorry, I meant to ask if this is related to
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24832>.

Commit f1267c872fcaed6c53d43b3ff51abb726f7418d6 doesn’t have the desired
effect: the ‘patches’ field is voluntarily unthunked, so it gets to see
the ‘%current-system’ value that it gets when gl.scm is loaded, hence
the problem we’re experiencing.

This is fixed in 4c93fe83e89473b2d16b93900c87e0da0ceecd6e by making the
patch an input depending on ‘%current-system’, within an ‘inputs’ field.

Thanks!

Ludo’.

      reply	other threads:[~2016-11-03 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31  6:17 bug#24833: Hydra ignores MIPS-specific patch for Mesa on core-updates Mark H Weaver
2016-11-02 22:17 ` Ludovic Courtès
2016-11-03  2:10 ` Mark H Weaver
2016-11-03 10:29   ` 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

  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=87zilgx3ea.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24833-done@debbugs.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 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).