From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 74527@debbugs.gnu.org
Subject: [bug#74527] [PATCH] gnu: cl-eclector: Update to 0.10.0.
Date: Tue, 26 Nov 2024 14:57:37 +0100 [thread overview]
Message-ID: <m1cyii5c8e.fsf@fastmail.net> (raw)
In-Reply-To: <87a5dmb0s2.fsf@kitej>
Guillaume Le Vaillant <glv@posteo.net> writes:
> The sbcl-common-lisp-jupyter package fails to build with this updated
> sbcl-eclector. Could you take a look at it?
It's due to a breaking change in Eclector:
https://github.com/s-expressionists/Eclector/blob/28d29445556a0c03178e3daff7a2d8b378fa4340/NEWS#L3
It also occurs when installing via Quicklisp and Ultralisp:
https://github.com/yitzchak/common-lisp-jupyter/issues/124
https://github.com/yitzchak/common-lisp-jupyter/issues/125
Upstream has already implemented a fix:
https://github.com/yitzchak/common-lisp-jupyter/commit/2c453f758aa7b3b6c1e77ab9387347f57ee1a197
https://github.com/yitzchak/common-lisp-jupyter/commit/e77d150bebc25ae89b80d903cc8da5c02e7a96b7
It looks like the best solution is to update sbcl-common-lisp-jupyter as
well. Which unfortunately is not completely trivial because it has new
dependencies which are not yet packaged. I will look into this.
Cheers,
Konrad
next prev parent reply other threads:[~2024-11-26 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 12:55 [bug#74527] [PATCH] gnu: cl-eclector: Update to 0.10.0 Konrad Hinsen
2024-11-26 13:08 ` Guillaume Le Vaillant
2024-11-26 13:57 ` Konrad Hinsen [this message]
2024-11-26 14:24 ` Konrad Hinsen
2024-11-26 14:32 ` Guillaume Le Vaillant
2024-11-26 15:44 ` [bug#74527] [PATCH v2 1/3] " Konrad Hinsen
2024-11-27 13:01 ` bug#74527: " Guillaume Le Vaillant
2024-11-26 15:45 ` [bug#74527] [PATCH v2 2/3] gnu: Add cl-nontrivial-gray-streams Konrad Hinsen
2024-11-26 15:45 ` [bug#74527] [PATCH v2 3/3] gnu: cl-common-lisp-jupyter: Update to 1.0 Konrad Hinsen
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=m1cyii5c8e.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=74527@debbugs.gnu.org \
--cc=glv@posteo.net \
/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).