unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: An update on ‘core-updates’
Date: Mon, 15 Jan 2024 11:02:04 +0200	[thread overview]
Message-ID: <ZaT0jL4g3g5MnkpR@3900XT> (raw)
In-Reply-To: <87edenoqi1.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]

On Thu, Jan 11, 2024 at 04:10:14PM +0100, Ludovic Courtès wrote:
> Hello Guix!
> 
> Several of us have been fiddling with the ‘core-updates’ branch for a
> while.  I think there’s now consensus that the branch is really
> dedicated to core packages and (guix build …) modules, as embodied in
> the new ‘core-packages’ team¹.
> 
> We’ve updated GCC 11.x, glibc, binutils, and various packages from (gnu
> packages base).  Notable exceptions are Coreutils, Findutils, sed, and
> tar; I tried but that’s a bit more work, notably because their variants
> in commencement.scm would no longer build because their build scripts
> use sed patterns not supported by Gash-Utils.
> 
> Long story short: I’d like us to freeze and merge the branch ASAP,
> notably because the glibc graft on ‘master’ leads to a bad user
> experience.  I’m happy with the current state of the branch and wouldn’t
> mind postponing remaining upgrades for the next cycle.
> 
> Thoughts?
> 
> Remaining work includes: checking that cross-compilation targets still
> work after the recent Binutils updates, checking i586-gnu (GNU/Hurd) and
> other platforms, and possibly addressing the Gawk non-determinism
> issue².
> 
> Currently package subsets are built here:
> 
>   https://ci.guix.gnu.org/jobset/core-updates
>   https://guix.bordeaux.inria.fr/jobset/guix-core-updates
> 
> I don’t think I can commit to coordinating the stabilization effort
> though as I’m busy with other things this month.  Would anyone like to
> take the lead on this?
> 
> Happy updating!
> 
> Ludo’.
> 
> ¹ https://issues.guix.gnu.org/67880
> ² https://issues.guix.gnu.org/68378

There's a patch floating around somewhere to adjust the page size on
jemalloc on aarch64 to be at least 64k so that people running guix
software on apple silicon don't have issues.  I think we should add it
for core-updates so it doesn't get forgotten, I've seen it come up on
IRC at least once a week.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-01-15  9:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 15:10 An update on ‘core-updates’ Ludovic Courtès
2024-01-12 12:13 ` Josselin Poiret
2024-01-29 16:32   ` Ludovic Courtès
2024-01-12 12:55 ` Janneke Nieuwenhuizen
2024-01-13 13:54   ` Janneke Nieuwenhuizen
2024-01-16  7:46     ` Janneke Nieuwenhuizen
2024-01-20  9:34       ` Janneke Nieuwenhuizen
2024-01-15  8:57   ` Efraim Flashner
2024-01-16  7:49     ` Janneke Nieuwenhuizen
2024-01-15  9:02 ` Efraim Flashner [this message]
2024-01-15 17:25   ` Roman Scherer
2024-01-15 19:06     ` Roman Scherer
2024-01-17 13:51 ` Maxim Cournoyer
2024-01-17 15:40 ` Simon Tournier

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=ZaT0jL4g3g5MnkpR@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.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).