From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark H Weaver <mhw@netris.org>
Subject: bug#36747: Official MesCC bootstrap binaries differ from my locally
 built ones
Date: Mon, 22 Jul 2019 04:31:48 -0400
Message-ID: <877e8a79mz.fsf@netris.org>
References: <875znwcoo9.fsf@netris.org> <87ef2j1pgt.fsf@gnu.org>
 <87ftmy51kk.fsf@netris.org> <87muh6sib4.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:53258)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hpTkl-0003gb-Ov
 for bug-guix@gnu.org; Mon, 22 Jul 2019 04:33:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hpTkk-0006ev-P1
 for bug-guix@gnu.org; Mon, 22 Jul 2019 04:33:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:51099)
 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 1hpTkk-0006en-M0
 for bug-guix@gnu.org; Mon, 22 Jul 2019 04:33:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.36747.B36747.156378437421274@debbugs.gnu.org>
In-Reply-To: <87muh6sib4.fsf@gnu.org>
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: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 36747@debbugs.gnu.org

Hi Janneke,

Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>> What I need is a way to build the new bootstrap tarballs without using
>> the existing 'core-updates' branch.  I need a way to build them from a
>> branch that's based upon the much older bootstrap binaries that we've
>> been using for many years.  Preferably, they should be built from
>> something close to current 'master'.
>>
>> Is this feasible?
>
> Hmm, I'm not sure how much work it would be.

Actually, I have a better idea.  How about starting a new branch at
commit ef809e3ac036eccc5f9c9edd8fb661d14ae15f2f (the commit used to
build the current bootstrap binaries for core-updates) and applying the
fixes there?  Then you can push that new branch to savannah, and we can
build it and see if we get the same thing?  Hopefully, the only
difference will be those store references in MesCC.

What do you think?

      Mark