Re: Restarting 'python-updates'

[Mark H Weaver]

Marius Bakke <address@hidden> writes:

> Greetings Guix!
>
> Python 3.6.2 is scheduled to be released in about a week[0].
>
> Our current Python 3.5 is EOL[1], so we should upgrade ASAP. 3.6.2 seems
> like a good excuse. It would be good to start building a branch based on
> it once it is released (or core-updates is merged, whichever is last).
>
> Are there any objections to deleting the current 'python-updates' branch
> and starting a fresh one? Looking at `git log master..python-updates`,
> most of the commits seem to have made their way to 'master' in some form.

I think this should wait until after core-updates is merged.  Our build
farm capacity is already stretched quite thin, and "guix refresh -l
address@hidden" estimates that 2886 rebuilds would be required per
architecture.  Given the limitations of "guix refresh -l", that might
well be an underestimate.  So that's at least 8600 builds total, or
about half of the entire jobset on Hydra.

I don't think we can afford to build this out at the same time as
'core-updates' is being built, and 'master' is being kept up-to-date.
Even keeping 'master' up-to-date requires significant resources, given
the frequency of updates that require rebuilding most of GNOME, Qt,
IceCat, Libreoffice, Webkitgtk, etc.

       Mark