From: Christopher Baines <mail@cbaines.net>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: 01/03: gnu: sbcl: Update to 2.3.5.
Date: Thu, 08 Jun 2023 10:18:25 +0100 [thread overview]
Message-ID: <8735321f91.fsf@cbaines.net> (raw)
In-Reply-To: <87jzwf1q6x.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> 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?
Joining this thread with a different issue, it looks like this change
has broken sbcl on armhf-linux [1].
1: https://data.guix.gnu.org/repository/1/branch/master/package/sbcl/output-history?output=out&system=armhf-linux&target=none
Maybe you tested this locally and knew of this breakage, but it would
still be good to send this for review (either as some patches or pushed
to a branch) so that it's visible to others what the effect of the
change will be.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2023-06-08 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168604233936.6585.5956822286248744058@vcs2.savannah.gnu.org>
[not found] ` <20230606090539.E018EC23ED1@vcs2.savannah.gnu.org>
2023-06-07 11:11 ` 01/03: gnu: sbcl: Update to 2.3.5 Christopher Baines
2023-06-07 11:41 ` Guillaume Le Vaillant
2023-06-07 12:37 ` Christopher Baines
2023-06-08 9:18 ` Christopher Baines [this message]
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=8735321f91.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=glv@posteo.net \
--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).