Re: 01/03: gnu: sbcl: Update to 2.3.5.

[Guillaume Le Vaillant <glv@posteo.net>]

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

Christopher Baines <mail@cbaines.net> skribis:

> guix-commits@gnu.org writes:
>
>> glv pushed a commit to branch master
>> in repository guix.
>>
>> commit b019b49c74e51e42230da471f39bff9f642fbc24
>> Author: Guillaume Le Vaillant <glv@posteo.net>
>> AuthorDate: Fri Jun 2 13:32:55 2023 +0200
>>
>>     gnu: sbcl: Update to 2.3.5.
>>
>>     * gnu/packages/lisp.scm (sbcl): Update to 2.3.5.
>> ---
>>  gnu/packages/lisp.scm | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> Did this change need to go straight to master?
>
> → guix refresh -l sbcl
> Building the following 314 packages would ensure 1615 dependent packages are rebuilt: ...
>
> Above 300 but below 1800 means staging according to [1].
>
> 1: https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html#index-rebuild-scheduling-strategy

Currently there is no staging branch, as it got deleted because of the
changes in the branching strategy ([1]). If someone creates a staging
branch, will cuirass see that and start building it? Or could it just
stay in limbo for months?

Concerning the specific case of sbcl dependents, they build pretty fast.
On my machine, building all of them took less than one hour. So the
period during which some substitutes are missing is pretty short.

[1] https://issues.guix.gnu.org/63459

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