GNU bug report logs - #36747
Official MesCC bootstrap binaries differ from my locally built ones

Previous Next

Full log

Message #73 received at 36747 <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: 36747 <at> debbugs.gnu.org
Subject: Re: bug#36747: Official MesCC bootstrap binaries differ from my
 locally built ones
Date: Wed, 14 Aug 2019 16:43:49 -0400

Hi Marius,

Marius Bakke <mbakke <at> fastmail.com> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.