From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#36747: Official MesCC bootstrap binaries differ from my locally
 built ones
Date: Sat, 17 Aug 2019 23:38:02 +0200
Message-ID: <87v9uvbhhh.fsf@gnu.org>
References: <875znwcoo9.fsf@netris.org> <87ef2j1pgt.fsf@gnu.org>
 <87ftmy51kk.fsf@netris.org> <87muh6sib4.fsf@gnu.org>
 <877e8a79mz.fsf@netris.org> <87pnm2ufv1.fsf@gnu.org>
 <87lfwpqpb7.fsf@netris.org> <875znt2hlc.fsf@gnu.org>
 <87zhke97xj.fsf@netris.org> <87h86mdaex.fsf@gnu.org>
 <8736i5a7mb.fsf@netris.org> <87mugdbc9r.fsf@gnu.org>
 <8736i3iyas.fsf@devup.no> <87zhkbhd07.fsf@devup.no>
 <87v9uz4msh.fsf@netris.org> <87woffh66h.fsf@devup.no>
 <87o90pgzak.fsf@gnu.org> <87mug9cagh.fsf@netris.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:40323)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hz6Pf-0007sh-4a
 for bug-guix@gnu.org; Sat, 17 Aug 2019 17:39:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hz6Pe-0004kR-3n
 for bug-guix@gnu.org; Sat, 17 Aug 2019 17:39:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:48143)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1hz6Pe-0004kM-0N
 for bug-guix@gnu.org; Sat, 17 Aug 2019 17:39:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.36747.B36747.15660778909487@debbugs.gnu.org>
In-Reply-To: <87mug9cagh.fsf@netris.org> (Mark H. Weaver's message of "Fri, 16
 Aug 2019 12:59:31 -0400")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 36747@debbugs.gnu.org

Hi Mark,

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

> You can reproduce them with the following command from a git checkout at
> commit 9e6256ba0f32ab12d61c914a3fed879dac881762, which is the tip of the
> 'wip-binaries' branch, based on recent 'master':
>
>   ./pre-inst-env guix build --system=3Di686-linux bootstrap-tarballs

OK, I=E2=80=99ll give it a try and report back, probably end of next week.

>> srfi/srfi-1.scm:592:17: In procedure map1:
>> Throw to key `srfi-34' with args `(#<condition &message [message: "texin=
fo-perl-compat.patch: patch not found"] 51bb5c0>)'.
>>
>> Am I missing something?
>
> The string "texinfo-perl-compat" does not occur in the current
> 'core-updates-next' branch on Savannah, which is at commit
> 82eaac49ac983f28768d6623d802f41cbd7f779b.

Oh, I had misconfigured the =E2=80=98core-updates-next=E2=80=99 jobset: its
=E2=80=98load_path_input=E2=80=99 was '("core-updates-next"), which led the=
 host Guix to
lookup bits of the target Guix, hence the confusion.

I fixed it by setting it to the empty list as it should:

  update specifications set load_path_inputs =3D '()' where name =3D 'core-=
updates-next';

(The specs can be seen at <https://ci.guix.gnu.org/specifications>.)

It=E2=80=99s currently being evaluated:

  https://ci.guix.gnu.org/jobset/core-updates-next

Ludo=E2=80=99.