unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 55198-close@debbugs.gnu.org
Subject: bug#55198: [PATCH]: sbcl: Update to 2.2.4
Date: Fri, 06 May 2022 09:17:30 +0000	[thread overview]
Message-ID: <87fslnypti.fsf@kitej> (raw)
In-Reply-To: <87y1zf2g6e.fsf@gmail.com>

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

André A. Gomes <andremegafone@gmail.com> skribis:

> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> When testing this updated sbcl I found out that it has a bug breaking
>> the sbcl-lzlib package (maybe others too). I reported it upstream and
>> they managed to fix it (https://bugs.launchpad.net/sbcl/+bug/1971088).
>>
>> We could add a patch for the fix to sbcl 2.2.4, or just wait a few weeks
>> for the next release.
>
> This is not exactly on topic but I'm wondering how should I proceed in
> the future.  I checked that there was a new sbcl release, tried to build
> locally and it succeeded.  What else should I do?  Thanks.

After checking that the updated sbcl builds fine, you can also check all
the packages depending on sbcl with a command like:

--8<---------------cut here---------------start------------->8---
  ./pre-inst-env guix build $(./pre-inst-env guix refresh -l sbcl | cut -d ':' -f 2)
--8<---------------cut here---------------end--------------->8---


> Perhaps we could wait until the next release.

Ok. I'm closing this issue then, and you can open a new one to update to
sbcl 2.2.5 (or maybe 2.3.0?) when it it released (probably near the end
of May or beginning of June if upstream keeps the same release
schedule).

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

      reply	other threads:[~2022-05-06  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30 17:36 [bug#55198] [PATCH]: sbcl: Update to 2.2.4 André A. Gomes
2022-05-06  8:24 ` Ludovic Courtès
2022-05-06  8:38   ` Guillaume Le Vaillant
2022-05-06  8:55     ` André A. Gomes
2022-05-06  9:17       ` Guillaume Le Vaillant [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=87fslnypti.fsf@kitej \
    --to=glv@posteo.net \
    --cc=55198-close@debbugs.gnu.org \
    --cc=andremegafone@gmail.com \
    --cc=ludo@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).