From: zimoun <zimon.toutoune@gmail.com>
To: "Philip Munksgaard" <philip@munksgaard.me>
Cc: 48700@debbugs.gnu.org
Subject: bug#48700: guix import fails with unexpected token
Date: Thu, 10 Jun 2021 11:41:11 +0200 [thread overview]
Message-ID: <86im2mjbuw.fsf@gmail.com> (raw)
In-Reply-To: <39115c49-4522-413d-87f9-bc2c422b0dcf@www.fastmail.com> (Philip Munksgaard's message of "Sun, 30 May 2021 18:38:47 +0200")
Hi,
On Sun, 30 May 2021 at 18:38, "Philip Munksgaard" <philip@munksgaard.me> wrote:
> As far as I can tell, this is actually an instance of
> https://issues.guix.gnu.org/48701. You can close this issue in favor of that
> one.
From my understanding, no. I propose to unmerge. WDYT?
The bug#48700 is a duplicate of bug#44115 (recursive importers). For
instance, a first attempt to fix it is proposed by patch#45984; a new
version should come soon. :-)
But bug#48701 is not related, instead it is related to the Cabal
implemented by Guix.
For instance, this works:
--8<---------------cut here---------------start------------->8---
for p in bytestring-to-vector bmp directory-tree language-c-quote mainland-pretty neat-interpolation pcg-random srcloc; \
do
guix import hackage $p -r ;
done
guix import hackage futhark
--8<---------------cut here---------------end--------------->8---
i.e., the option recursive with ’futhark’ goes to ’recursive-import’
from (guix import utils) and the ’node’ is not always well-formed when
’lookup-node’ as explained in #44115 and #45984.
<http://issues.guix.gnu.org/issue/44115>
<http://issues.guix.gnu.org/issue/45984>
All the best,
simon
next prev parent reply other threads:[~2021-06-10 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 13:08 bug#48700: guix import fails with unexpected token Philip Munksgaard
2021-05-27 19:54 ` zimoun
2021-05-30 16:38 ` Philip Munksgaard
2021-06-10 9:41 ` zimoun [this message]
2021-06-10 12:20 ` Philip Munksgaard
2021-06-10 13:02 ` zimoun
2021-06-10 13:29 ` Philip Munksgaard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86im2mjbuw.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=48700@debbugs.gnu.org \
--cc=philip@munksgaard.me \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.