From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36760@debbugs.gnu.org
Subject: [bug#36760] [PATCH 0/3] Switch to Guile-JSON 3.x
Date: Sat, 17 Aug 2019 22:47:45 +0200 [thread overview]
Message-ID: <87pnl3mscu.fsf@elephly.net> (raw)
In-Reply-To: <877e7bem4l.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> When we update the ‘guix’ package, everything that depends on it will
>> also have to be updated to a snapshot that uses Guile-JSON 3.x: cuirass,
>> hpcguix-web, and rcas-web. I count on you, dear reader, to help in
>> those areas. :-)
>
> Commit 2eb0628a423a36bc21777d7439885baa9a9a8e6d updates the ‘guix’ and
> ‘cuirass’ packages to use Guile-JSON 3.x. ‘hpcguix-web’ was updated
> earlier, in commit 4b0356590a57bc27a61956b981f4a90efcf9c92d.
Thank you!
> I haven’t checked rcas-web though; Ricardo?
rcas-web doesn’t talk to Guix, so its use of an older Guile JSON is not
a problem. If we want to let “guile-json” point to 3.x that’s fine;
we’d just let rcas-web use the 1.x variant.
(I’ll update it at some point in the future, but it doesn’t seem
critical.)
--
Ricardo
next prev parent reply other threads:[~2019-08-17 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 10:13 [bug#36760] [PATCH 0/3] Switch to Guile-JSON 3.x Ludovic Courtès
2019-07-22 10:18 ` [bug#36760] [PATCH 1/3] maint: " Ludovic Courtès
2019-07-22 10:18 ` [bug#36760] [PATCH 2/3] gnu: guile-json: Define 'guile-json-1' Ludovic Courtès
2019-07-22 10:18 ` [bug#36760] [PATCH 3/3] gnu: Explicitly refer to 'guile-json-1' when needed Ludovic Courtès
2019-07-24 22:39 ` bug#36760: [PATCH 0/3] Switch to Guile-JSON 3.x Ludovic Courtès
2019-08-17 17:29 ` [bug#36760] " Ludovic Courtès
2019-08-17 20:47 ` Ricardo Wurmus [this message]
2019-08-17 21:17 ` 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=87pnl3mscu.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36760@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).