From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#36747: Official MesCC bootstrap binaries differ from my locally built ones Date: Wed, 14 Aug 2019 16:43:49 -0400 Message-ID: <87imqz4gv3.fsf@netris.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36944) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hy08m-0000Jx-3U for bug-guix@gnu.org; Wed, 14 Aug 2019 16:45:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hy08k-0005WW-Ul for bug-guix@gnu.org; Wed, 14 Aug 2019 16:45:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40939) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hy08k-0005Vy-Qm for bug-guix@gnu.org; Wed, 14 Aug 2019 16:45:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87woffh66h.fsf@devup.no> (Marius Bakke's message of "Wed, 14 Aug 2019 21:56:38 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Marius Bakke Cc: 36747@debbugs.gnu.org Hi Marius, Marius Bakke writes: > I wanted to check that the bootstrap-tarballs machinery still worked > after merging the branch, since it was non-trivial. Mainly to make the > commit that created them reachable forever, but maybe we don't need it. [...] > [...] I will do this in a 'core-updates-next' branch. I would also > like to merge wip-binaries into it as a final step, unless someone has > objections. I think that 'wip-binaries' (or something close to it) should be merged into 'master', rather than 'core-updates'. That would allow people to easily verify the new bootstrap binaries from 'master'. Of course, anything merged into 'master' will eventually be merged into 'core-updates' as well, but no one will be able to verify the new binaries from 'core-updates' anyway, because 'core-updates' has different versions of 'bash', 'guile', and maybe some other things. What do you think? Mark