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: Mon, 12 Aug 2019 03:08:45 -0400 Message-ID: <87zhke97xj.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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:45439) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hx4Sx-0002be-9x for bug-guix@gnu.org; Mon, 12 Aug 2019 03:10:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hx4Sw-0004wO-67 for bug-guix@gnu.org; Mon, 12 Aug 2019 03:10:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37235) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hx4Sw-0004wG-2f for bug-guix@gnu.org; Mon, 12 Aug 2019 03:10:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <875znt2hlc.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 23 Jul 2019 12:03:27 +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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 36747@debbugs.gnu.org Hi Ludovic, Ludovic Court=C3=A8s writes: > Mark H Weaver skribis: > >>> I have added a very similar set of two patches to wip-cu-binaries, >>> branched @ ef809e3ac036eccc5f9c9edd8fb661d14ae15f2f. >>> >>> They give the same md5sum for me as the wip-binaries branch that >>> branched off of master; so mine are at >>> http://lilypond.org/janneke/guix/20190722/ >> >> I built these, and here are the results: >> >> mhw@jojen /gnu/store/hd3lk0f08a0sq40qqa6yv1q9gbk7gxww-bootstrap-tarballs= -0$ sha256sum * >> b5915c71ff5ea722864e1097ce1e7ed50fd68ad7544521f2dd6969173c260276 guile-= static-stripped-2.2.4-i686-linux.tar.xz >> 1acd8f83e27d2fac311a5ca78e9bf11a9a1638b82469870d5c854c4e7afaa26a linux-= libre-headers-stripped-4.14.67-i686-linux.tar.xz >> 021543d9bb6af55f39e68d69692e3cb74646ced2cad0bb9ac0047ef81e9d7330 mescc-= tools-static-stripped-0.5.2-0.bb062b0-i686-linux.tar.xz >> fb32090071b39fc804fb9a7fba96f0bc5eb844a0efd268fb24c42e6bfa959de0 mes-mi= nimal-stripped-0.19-i686-linux.tar.xz >> 9ee954dc19db5c8d4113c73a702fd8f79f26c51024220f2617d0572c0a85e69c static= -binaries-0-i686-linux.tar.xz >> >> Do these match what you built? > > We verified things back then: > > https://lists.gnu.org/archive/html/guix-devel/2018-12/msg00046.html > > This was on commit 4ae7dc7b9af64794081b1913740b97acd89c91bc, which is > earlier than the one you=E2=80=99re looking at (commit > ef809e3ac036eccc5f9c9edd8fb661d14ae15f2f, right?) Yes. However, I just noticed a more serious problem. The "independent verification" that you and I performed at commit 4ae7dc7b9af64794081b1913740b97acd89c91bc was bogus, because at that commit, %bootstrap-inputs had already been changed to use an earlier draft of the reduced binary seed, based on unverified bootstrap tarballs downloaded from lilypond.org. In order to perform a truly independent verification, we need to build the new bootstrap binaries without using the new bootstrap binaries. Otherwise our verification is circular. It seems to me that the best way to accomplish this is to backport the new '%bootstrap-tarballs' from 'wip-cu-binaries' to the 'master' branch. What do you think? Thanks, Mark