unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: 54394@debbugs.gnu.org
Subject: [bug#54394] [PATCH core-updates 00/12] Remove old GNU utilities from early bootstrap
Date: Wed, 16 Mar 2022 18:32:07 +0100	[thread overview]
Message-ID: <8735jhdcrs.fsf@gnu.org> (raw)
In-Reply-To: <87v8wg40dl.fsf@ngyro.com> (Timothy Sample's message of "Mon, 14 Mar 2022 16:47:50 -0600")

Timothy Sample <samplet@ngyro.com> skribis:

> The next two patches spruce up the ‘gnu-bootstrap’ module.  One fixes an
> omission, and the other gets it ready to handle Gash-Utils 0.2.0, which
> unfortunately has two module directories.
>
> The next three are updates.  The bootar update optimistically assumes
> that someone with access will upload the source file to the Guix mirror
> URL: “mirror://gnu/guix/...” as was done with previous versions.
>
> The rest hopefully speak for themselves.  Sadly, the last one is
> something of a jumble.  Originally I wanted to remove the utilities one
> at a time, but it turns out there are interference effects.  I can’t
> remember the exact details now, but to get an idea, removing both old
> Bash and old Grep might work, but removing one and then the other (in
> either order) might not.  Hence, many utilities get updated in one
> commit.

The patches all LGTM!  I think you can push them to ‘core-updates’ if
there are no objections.

Then Maxim, Ricardo, or myself (I think we’re the three people who can
do that currently) can upload bootar to ftp.gnu.org.  Let us know.

It’s quite something to see these intermediate versions of Bash, Gawk,
tar, grep, coreutils, and sed go away in the last patch, and that tells
something about the magnitude of the work that has gone in this
Gash-Utils release.  Thumbs up, and big thanks!

Ludo’.




  parent reply	other threads:[~2022-03-16 17:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 22:47 [bug#54394] [PATCH core-updates 00/12] Remove old GNU utilities from early bootstrap Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 01/12] gnu: hello-mesboot: Downgrade to 2.10 Timothy Sample
2022-03-16 17:25   ` [bug#54394] [PATCH core-updates 00/12] Remove old GNU utilities from early bootstrap Ludovic Courtès
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 02/12] gnu-bootstrap: Configure PACKAGE_NAME Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 03/12] gnu-bootstrap: Allow multiple module directories Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 04/12] gnu: gash-utils: Update to 0.2.0 Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 05/12] gnu: bootar: Update to 1b Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 06/12] gnu: gash: Update to 0.3.0 Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 07/12] gnu: gash-utils-boot: Create 'echo' wrapper Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 08/12] gnu: bzip2-mesboot: Remove package Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 09/12] gnu: sed-mesboot0: " Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 10/12] gnu: binutils-mesboot0: Update to 2.20.1a Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 11/12] gnu: %boot-tcc-inputs: Remove extra "gash-utils" Timothy Sample
2022-03-14 22:57 ` [bug#54394] [PATCH core-updates 12/12] gnu: commencement: Remove many old utilities Timothy Sample
2022-03-15 10:34   ` Maxime Devos
2022-03-15 19:35     ` Timothy Sample
2022-03-16 17:25 ` [bug#54394] [PATCH core-updates 00/12] Remove old GNU utilities from early bootstrap Ludovic Courtès
2022-03-16 17:32 ` Ludovic Courtès [this message]
2022-03-19 19:53   ` bug#54394: " Timothy Sample
2022-03-21 15:17     ` [bug#54394] " Ludovic Courtès
2022-03-20 11:38 ` Jan Nieuwenhuizen

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=8735jhdcrs.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54394@debbugs.gnu.org \
    --cc=samplet@ngyro.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).