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: Tue, 27 Aug 2019 10:27:11 -0400
Message-ID: <874l22of8l.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>
 <874l26y9j0.fsf@gnu.org> <87d0guuwt4.fsf@netris.org>
 <87zhjw1gfm.fsf@gnu.org> <87a7bvnts4.fsf@netris.org>
 <87y2zfq746.fsf@gnu.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]:40716)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i2cS4-0000cH-1c
 for bug-guix@gnu.org; Tue, 27 Aug 2019 10:28:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i2cS2-0000Eg-Ta
 for bug-guix@gnu.org; Tue, 27 Aug 2019 10:28:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:40420)
 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 1i2cS2-0000Ea-Pa
 for bug-guix@gnu.org; Tue, 27 Aug 2019 10:28:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.36747.B36747.156691607324967@debbugs.gnu.org>
In-Reply-To: <87y2zfq746.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: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: 36747@debbugs.gnu.org

Hi Ludovic,

Ludovic Court=C3=A8s <ludo@gnu.org> wrote:

> Mark H Weaver <mhw@netris.org> skribis:
>
>> Hmm, good point.  Perhaps we should postpone the Bash fix until the next
>> core-updates cycle. [...]
>
> Your call: if you think this Bash fix can be delayed without causing
> problems, then please revert it and we=E2=80=99ll apply it on the next cy=
cle.
> That would allow us to merge =E2=80=98core-updates=E2=80=99 more quickly =
for sure!

Okay, let's delay the bash fix until the next cycle.

>> I tagged 'wip-binaries' and merged it into master, but there's an
>> undesirable side effect.  After the merge, "git describe" from 'master'
>> now returns "bootstrap-20190815-222-g32e18e9b94".
>
> I think that=E2=80=99s OK.
>
> Ideally, we=E2=80=99d have mentioned the commit used to build the binarie=
s in
> the commit that actually adds those binaries to boostrap.scm.

Agreed, that was an important omission on my part.

> Maybe that can still be done with a Git graft?

I think it's easier than that.  I personally see no need to preserve the
branch 'core-updates-next', which has a different role than usual and is
arguably misnamed.  It's only 3 commits.  Of those 3, one has a faulty
commit log, and another should be postponed.  I could simply push the
revised commits to 'core-updates' directly.

What do you think?

      Mark