unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 42385@debbugs.gnu.org
Subject: bug#42385: guile-based jupyter kernels mix guile3 and guile2.2
Date: Mon, 20 Jul 2020 08:22:40 -0600	[thread overview]
Message-ID: <e639e2ed-4aca-eb51-00be-810d3121f864@gmail.com> (raw)
In-Reply-To: <87lfjey20u.fsf@gnu.org>


On 7/20/20 3:22 AM, Ludovic Courtès wrote:
> Hi Jesse,
>
> Jesse Gibbons <jgibbons2357@gmail.com> skribis:
>
>> jupyter-guile-kernel and guix-jupyter mix guile3 and guile2.2.
>>
>> - jupyter-guile-kernel only has one of its dependencies in
>> GUILE_LOAD_PATH, so it doesn't build.
>>
>> - guix-jupyter builds successfully, but searches in the wrong
>> directory for guix-jupyter-kernel.scm.
>>
>> jupyter-guile-kernel requires guile-json1 which has not been packaged
>> for guile3, and is still built with guile2.2. IINM the
>> jupyter-guile-kernel repository has been updated to build with guile3,
>> so it might be worth updating. Unfortunately, there are no releases in
>> its github repository. I expect guix-jupyter will be much easier to
>> fix.
>> I have a series of patches coming soon that fix both named issues.
> Good catch!  Did you eventually manage to complete your work?
>
> Thanks,
> Ludo’.


The only reason I have not yet sent these patches (and others I have 
ready to send) is I haven't found the time to make the patches 
acceptable (lint, format commit messages, etc.). I will have time to do 
that tomorrow, so expect patches by July 22.





  reply	other threads:[~2020-07-20 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  4:29 bug#42385: guile-based jupyter kernels mix guile3 and guile2.2 Jesse Gibbons
2020-07-17 14:25 ` Jesse Gibbons
2020-07-20  9:22 ` Ludovic Courtès
2020-07-20 14:22   ` Jesse Gibbons [this message]
2020-07-24 10:16     ` Ludovic Courtès

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=e639e2ed-4aca-eb51-00be-810d3121f864@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=42385@debbugs.gnu.org \
    --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).