From: Andreas Enge <andreas@enge.fr>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Latest news on core-updates
Date: Wed, 19 Apr 2023 14:41:31 +0200 [thread overview]
Message-ID: <ZD/he8EmwH7nqHh+@jurong> (raw)
In-Reply-To: <87edog5dvl.fsf@cbaines.net>
Am Wed, Apr 19, 2023 at 11:58:03AM +0100 schrieb Christopher Baines:
> I haven't restarted submitting builds for core-updates given I think
> there's still some big changes going to land, but in any case, it would
> be good to get this going once there are no planned big changes (aka the
> branch is frozen).
I am not sure what "frozen" means exactly; I would say we must not make
commits to core-updates unless they repair a broken package, or maybe help
repair broken packages further down towards the leaves. (And this has been
true for a while now.) And maybe we should go further and refrain from
repairing things in core-updates that are already broken on master, at
least if they are relatively close to the root of the dependency graph.
These can be done later in feature branches; I think we have the infra-
structure to shoulder bigger changes outside of core-updates.
On the other hand, this report is a bit worrying:
[core-updates] locales not installed properly
https://issues.guix.gnu.org/62934
It could potentially mean changes to glibc, which would throw us back
a week.
Andreas
next prev parent reply other threads:[~2023-04-19 12:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57 ` Andreas Enge
2023-04-17 8:06 ` Andreas Enge
2023-04-17 8:18 ` Core-updates after the staging merge Guillaume Le Vaillant
2023-04-17 8:33 ` Andreas Enge
2023-04-17 9:03 ` Andreas Enge
2023-04-17 9:56 ` Andreas Enge
2023-04-17 12:19 ` Simon Tournier
2023-04-17 12:38 ` Andreas Enge
2023-04-17 12:57 ` Simon Tournier
2023-04-17 14:12 ` Lars-Dominik Braun
2023-04-17 17:47 ` Simon Tournier
2023-04-17 18:07 ` Andreas Enge
2023-04-17 19:01 ` Lars-Dominik Braun
2023-04-18 17:16 ` Andreas Enge
2023-04-21 18:29 ` Lars-Dominik Braun
2023-04-17 12:57 ` Andreas Enge
2023-04-17 18:03 ` Maxim Cournoyer
2023-04-17 18:08 ` Andreas Enge
2023-04-18 5:04 ` John Kehayias
2023-04-18 17:38 ` Andreas Enge
2023-04-19 10:48 ` Latest news on core-updates Andreas Enge
2023-04-19 10:58 ` Christopher Baines
2023-04-19 12:41 ` Andreas Enge [this message]
2023-04-21 7:58 ` Andreas Enge
2023-04-21 13:01 ` Maxim Cournoyer
2023-04-20 13:56 ` Christopher Baines
2023-04-20 18:09 ` Andreas Enge
2023-04-21 8:20 ` Simon Tournier
2023-04-21 8:47 ` Andreas Enge
2023-04-21 11:31 ` Simon Tournier
2023-04-21 16:12 ` Katherine Cox-Buday
2023-04-21 16:12 ` Katherine Cox-Buday
2023-04-21 17:04 ` reza.housseini
2023-04-23 7:17 ` Andreas Enge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZD/he8EmwH7nqHh+@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.