From: Nathan Dehnel <ncdehnel@gmail.com>
To: Timothy Sample <samplet@ngyro.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
Leo Prikler <leo.prikler@student.tugraz.at>,
48152-done@debbugs.gnu.org
Subject: bug#48152: no code for module (json) on guix upgrade
Date: Sun, 2 May 2021 16:22:29 -0500 [thread overview]
Message-ID: <CAEEhgEt3motKXUBUtCnBJg_s0MTVqBkU_oLvF4R3JpoA=fY0Ew@mail.gmail.com> (raw)
In-Reply-To: <87eeepdl5a.fsf@ngyro.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
It works now for me, thanks.
On Sun, May 2, 2021, 1:51 PM Timothy Sample <samplet@ngyro.com> wrote:
> Hi Leo,
>
> Thanks for pinging me.
>
> Leo Prikler <leo.prikler@student.tugraz.at> writes:
>
> > Am Sonntag, den 02.05.2021, 19:03 +0200 schrieb Mathieu Othacehe:
> >> Hello,
> >>
> >> > I found this stops being an issue after reverting
> >> > 66b14dccdd0d83c875ce3a8d50ceab8b6f0a3ce2.
> >> > @Timothy do you know how we can get guile-json in there for SWH?
> >>
> >> I think this is fixed with d2b5bb5f9de8dc1a51260e17cd91c3039070a7f2
> >> to
> >> fd5527407ff336c4af1c5511e19c0956720cd7aa. Could you please confirm?
> >>
> > Thanks for your quick work. At least hg-download seems to work and I'm
> > currently building linux-libre, which relies on regular download. I
> > also tested git, which probably already had this. Can someone test the
> > others?
>
> I can confirm that ‘cvs-fetch’ and ‘android-repo-fetch’ work, too. The
> ‘bzr-fetch’ and ‘svn-fetch’ systems do not pull in ‘(guix build
> download)’, so they should be fine (and indeed, they work when I test
> them).
>
> Thanks Mathieu!
>
>
> -- Tim
>
[-- Attachment #2: Type: text/html, Size: 1683 bytes --]
prev parent reply other threads:[~2021-05-02 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 2:17 bug#48152: no code for module (json) on guix upgrade Nathan Dehnel
2021-05-02 16:04 ` Leo Prikler
2021-05-02 17:03 ` Mathieu Othacehe
2021-05-02 17:24 ` Leo Prikler
2021-05-02 18:51 ` Timothy Sample
2021-05-02 21:22 ` Nathan Dehnel [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='CAEEhgEt3motKXUBUtCnBJg_s0MTVqBkU_oLvF4R3JpoA=fY0Ew@mail.gmail.com' \
--to=ncdehnel@gmail.com \
--cc=48152-done@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=othacehe@gnu.org \
--cc=samplet@ngyro.com \
/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).