unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 36747@debbugs.gnu.org
Subject: bug#36747: Official MesCC bootstrap binaries differ from my locally built ones
Date: Wed, 14 Aug 2019 14:43:07 -0400	[thread overview]
Message-ID: <87pnl74mg9.fsf@netris.org> (raw)
In-Reply-To: <87v9uz4msh.fsf@netris.org> (Mark H. Weaver's message of "Wed, 14 Aug 2019 14:35:47 -0400")

Earlier I wrote:

[...]
> (3) The following bootstrap packages in 'core-updates' bootstrap.scm
>     should be updated to use the new binaries above:
>
>      (a) %bootstrap-linux-libre-headers
>      (b) %bootstrap-mescc-tools
>      (c) %bootstrap-mes
>
> (4) Berlin should start rebuilding 'core-updates'.
>
> If desired, steps (3) and (4) could come before (2) if someone
> temporarily uploads the new binaries somewhere else, and adjusts
> '%bootstrap-base-urls' accordingly.  The key is for the hashes and file
> names to match what we've agreed on here, as I listed in (2) above.
>
> What do you think?

I should have inserted the following item in the TODO list above:

(3.5) I think that 'bash-4.4-linux-pgrp-pipe.patch', adapted to 5.0, should be
    applied to all 'bash' packages in 'core-updates'.  To be more precise,
    the patch should be applied to the main 'bash' package in bash.scm,
    inherited from all other bash packages, so that PGRP_PIPE is set
    unconditionally set on systems based on Linux (the kernel), regardless
    of the kernel version running on the build machine.

This change would also entail a full rebuild of core-updates, so it
should ideally be done before starting the rebuild.  It's not crucial,
but it would be nice to fix this potential source of non-determinism in
the Bash builds.

      Thanks,
        Mark

  reply	other threads:[~2019-08-14 18:44 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20 22:43 bug#36747: Official MesCC bootstrap binaries differ from my locally built ones Mark H Weaver
2019-07-21 13:34 ` Jan Nieuwenhuizen
2019-07-22  0:56   ` Mark H Weaver
2019-07-22  6:18     ` Jan Nieuwenhuizen
2019-07-22  6:26       ` Jan Nieuwenhuizen
2019-07-22  8:26       ` Jan Nieuwenhuizen
2019-07-22  8:31       ` Mark H Weaver
2019-07-22 17:41         ` Jan Nieuwenhuizen
2019-07-23  5:42           ` Mark H Weaver
2019-07-23  6:28             ` Jan Nieuwenhuizen
2019-08-12  0:21               ` Mark H Weaver
2019-08-12  4:11                 ` Mark H Weaver
2019-07-23 10:03             ` Ludovic Courtès
2019-08-12  7:08               ` Mark H Weaver
2019-08-12  9:01                 ` Jan Nieuwenhuizen
2019-08-13  6:42                   ` Mark H Weaver
2019-08-13 10:17                     ` Jan Nieuwenhuizen
2019-08-14 15:03                       ` Marius Bakke
2019-08-14 17:29                         ` Marius Bakke
2019-08-14 18:35                           ` Mark H Weaver
2019-08-14 18:43                             ` Mark H Weaver [this message]
2019-08-14 19:56                             ` Marius Bakke
2019-08-14 20:43                               ` Mark H Weaver
2019-08-15 19:44                               ` Mark H Weaver
2019-08-15 21:19                                 ` Marius Bakke
2019-08-15 23:16                                   ` Mark H Weaver
2019-08-15 20:56                               ` Mark H Weaver
2019-08-16  7:42                                 ` Mark H Weaver
2019-08-17 16:49                                   ` Mark H Weaver
2019-08-16 10:49                               ` Ludovic Courtès
2019-08-16 16:59                                 ` Mark H Weaver
2019-08-17 21:38                                   ` Ludovic Courtès
2019-08-18  1:17                                     ` Mark H Weaver
2019-08-18  9:26                                       ` Ludovic Courtès
2019-08-20 18:40                                         ` Mark H Weaver
2019-08-21 20:15                                           ` Mark H Weaver
2019-08-21 21:38                                   ` Ludovic Courtès
2019-08-21 22:57                                     ` Mark H Weaver
2019-08-22 10:09                                       ` Ludovic Courtès
2019-08-24 13:31                               ` Ludovic Courtès
2019-08-24 20:34                                 ` Mark H Weaver
2019-08-26  8:25                                   ` Ludovic Courtès
2019-08-26 18:36                                     ` Mark H Weaver
2019-08-27  9:38                                       ` Ludovic Courtès
2019-08-29 22:28                                         ` Bengt Richter
2019-08-27  3:58                                     ` Mark H Weaver
2019-08-27  9:40                                       ` Ludovic Courtès
2019-08-27 14:27                                         ` Mark H Weaver
2019-08-27 16:04                                           ` Ludovic Courtès
2019-08-27 16:46                                             ` Mark H Weaver
2019-08-28  0:55                                               ` Mark H Weaver
2019-08-28 22:12                                                 ` Ludovic Courtès
2019-08-29  5:46                                                   ` Ricardo Wurmus
2019-08-29  6:32                                                     ` Ricardo Wurmus
2019-08-29 19:28                                                   ` Mark H Weaver
2019-08-29 23:23                                                     ` Ludovic Courtès
2019-08-30 19:52                                                       ` Mark H Weaver
2019-08-31 12:44                                                         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnl74mg9.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=36747@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).