role of core-updates

role of core-updates

[Andy Tai]

Hi, hope Guix maintainers can clarify the role of the now core-updates
branch; the current documentation does not specify the core-updates
branch as a thing but there are clearly interests and uses of this
branch for package updates not belonging to a feature branch like
gnome and it is useful for, say, updating to the GNU make package
which would have caused world rebuild.  Thanks

Re: role of core-updates

[Leo Famulari]

On Mon, Nov 27, 2023, at 01:53, Andy Tai wrote:
> Hi, hope Guix maintainers can clarify the role of the now core-updates
> branch; the current documentation does not specify the core-updates
> branch as a thing but there are clearly interests and uses of this
> branch for package updates not belonging to a feature branch like
> gnome and it is useful for, say, updating to the GNU make package
> which would have caused world rebuild.  Thanks

Hi!

I'm not a maintainer but I did suggest the new 'feature branch' workflow so I will speak up.

The core-updates branch was / is for updating core packages, which are listed here:

 https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/ci.scm?h=v1.4.0#n136

Perhaps other packages like 'make' could be considered honorary members of this group as well, or maybe some other workflow can be imagined by the project.

I hope that helps!

Leo

Re: role of core-updates

[Felix Lechner via Development of GNU Guix and the GNU System distribution.]

Hi Leo,

On Mon, Nov 27 2023, Leo Famulari wrote:

> The core-updates branch was / is for updating core packages, which are listed here:
>
>  https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/ci.scm?h=v1.4.0#n136

I was surprised to see guile-3.0 there. Should it read guile-3.0/pinned
instead?

Kind regards
Felix

Re: role of core-updates

[Andreas Enge]

Am Sun, Nov 26, 2023 at 10:53:46PM -0800 schrieb Andy Tai:
> Hi, hope Guix maintainers can clarify the role of the now core-updates
> branch; the current documentation does not specify the core-updates
> branch as a thing but there are clearly interests and uses of this
> branch for package updates not belonging to a feature branch like
> gnome and it is useful for, say, updating to the GNU make package
> which would have caused world rebuild.  Thanks

When we started implementing the teams idea, I thought we would get rid
of the core-updates branch altogether. I still think it should not exist
as such, but be folded into the teams workflow. I am still mildly worried
that we have this branch into which many unrelated things get dumped,
without a clear responsibility who pushes it forward and on which timeline.

There is a "core" team, but this is probably not the same thing: I think
there are packages outside of the core team scope that cause now inside
the core-updates branch.

Andreas

Re: role of core-updates

[Ludovic Courtès]

Hi!

Andreas Enge <andreas@enge.fr> skribis:

> When we started implementing the teams idea, I thought we would get rid
> of the core-updates branch altogether. I still think it should not exist
> as such, but be folded into the teams workflow. I am still mildly worried
> that we have this branch into which many unrelated things get dumped,
> without a clear responsibility who pushes it forward and on which timeline.

Yeah, I share this sentiment.

> There is a "core" team, but this is probably not the same thing: I think
> there are packages outside of the core team scope that cause now inside
> the core-updates branch.

Maxim and I briefly discussed this on IRC and concluded we should have a
‘core-packages’ team for basically base.scm and commencement.scm (the
‘bootstrap’ team should be co-responsible for commencement.scm), and
maybe also guile.scm.

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?

Ludo’.

Re: role of core-updates

[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!

Andreas

Re: role of core-updates

[Andreas Enge]

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).

Andreas

Re: [bug#68606] role of core-updates

[Maxim Cournoyer]

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

[bug#68606] role of core-updates

[Andreas Enge]

Am Wed, Jan 24, 2024 at 02:22:08PM -0500 schrieb Maxim Cournoyer:
> Since patchelf is core material, if the rest of the series depend on
> that update, it should go to core-updates as well.

If I understand correctly, the series just needs patchelf 0.18, which is
already in core-updates. So I will wait until core-updates is merged to
look at the remainder of the series.

Andreas