unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org,  68606@debbugs.gnu.org,  65200@debbugs.gnu.org
Subject: Re: [bug#68606] role of core-updates
Date: Wed, 24 Jan 2024 14:22:08 -0500	[thread overview]
Message-ID: <87ede6wn8f.fsf@gmail.com> (raw)
In-Reply-To: <ZbEfUcmYQs40tH5a@jurong> (Andreas Enge's message of "Wed, 24 Jan 2024 15:31:45 +0100")

Hi Andreas,

Andreas Enge <andreas@enge.fr> writes:

> Hello,
>
> Am Sat, Dec 09, 2023 at 11:33:54AM +0100 schrieb Andreas Enge:
>> Am Sat, Dec 09, 2023 at 11:16:14AM +0100 schrieb Ludovic Courtès:
>> > With that in mind, ‘core-updates’ would effectively become the branch of
>> > the ‘core-packages’ team: the branch where we update packages in these
>> > files (primarily the toolchain and Guile), perhaps also (guix build
>> > utils), and that’s all.
>> > How does that sound?
>> Sounds good, thanks to you and Maxim for thinking it through!
>
> is the current core-updates branch ready for building and merging?
> I am looking at an issue:
>    https://issues.guix.gnu.org/68606
> that adds a patch (updating patchelf) that, as far as I understand, is
> already available on core-updates. So I feel somewhat blocked for the
> issue.
>
> The last merge was in spring of 2023, I think, and my patch updating wget
> is lingering in the branch since last July. So I am afraid we are reenacting
> the problems we had with the historic core-updates branch. It would be nice
> to merge and to move the branch to its new purpose.
>
> Also,
>    https://issues.guix.gnu.org/65200
> from last August is blocked by a core-updates merge (it should probably go
> to the new-style core-updates branch, and would be the starting point of
> working on bootstrapping from a newer GMP).

Since patchelf is core material, if the rest of the series depend on
that update, it should go to core-updates as well.  Now is as good a
time as any, since work has picked to get it into a mergeable state.

-- 
Thanks,
Maxim


  reply	other threads:[~2024-01-24 19:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  6:53 role of core-updates Andy Tai
2023-11-27 17:59 ` Leo Famulari
2023-11-27 20:08   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-04 16:02 ` Andreas Enge
2023-12-09 10:16   ` Ludovic Courtès
2023-12-09 10:33     ` Andreas Enge
2024-01-24 14:31       ` Andreas Enge
2024-01-24 19:22         ` Maxim Cournoyer [this message]
2024-01-25 10:18           ` [bug#68606] " 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

  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=87ede6wn8f.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=65200@debbugs.gnu.org \
    --cc=68606@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /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).