From: Julien Lepiller <julien@lepiller.eu>
To: Csepp <raingloom@riseup.net>
Cc: 61033@debbugs.gnu.org
Subject: bug#61033: opam importer can't handle list field
Date: Sat, 28 Jan 2023 13:18:11 +0100 [thread overview]
Message-ID: <20230128131811.23b5806c@sybil.lepiller.eu> (raw)
In-Reply-To: <86h6wg652t.fsf@riseup.net>
Le Tue, 24 Jan 2023 03:23:44 +0100,
Csepp <raingloom@riseup.net> a écrit :
> Truncated stack trace:
>
> ```
> ...
> In guix/import/opam.scm:
> 287:2 3 (opam->guix-package "mirage-crypto-pk" #:repo _ # _)
> In unknown file:
> 2 (filter #<procedure 7f43905afd00 at guix/import/opam.s…>
> …) In guix/import/opam.scm:
> 290:13 1 (_ ("mirage-no-solo5" "mirage-no-xen"))
> In unknown file:
> 0 (string-prefix? "conf-" ("mirage-no-solo5" "mirage-n…")
> …)
>
> ERROR: In procedure string-prefix?:
> In procedure string-prefix?: Wrong type argument in position 2
> (expecting string): ("mirage-no-solo5" "mirage-no-xen") ```
>
>
>
The issue is related to lines like this in the list of dependencies:
(("mirage-no-solo5" & "mirage-no-xen") | "zarith-freestanding" |
"mirage-runtime" {>= "4.0"})
This reads as a choice between three dependencies:
- mirage-no-solo5 with mirage-no-xen
- zarith-freestanding
- mirage-runtime
The importer infrastructure is not intelligent enough to really be able
to solve constraints in imported packages, so I don't see an easy
solution. It could silently use the first option, or put a comment
instead.
Ideas?
next prev parent reply other threads:[~2023-01-28 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 2:23 bug#61033: opam importer can't handle list field Csepp
2023-01-28 12:18 ` Julien Lepiller [this message]
2023-01-28 19:30 ` Csepp
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=20230128131811.23b5806c@sybil.lepiller.eu \
--to=julien@lepiller.eu \
--cc=61033@debbugs.gnu.org \
--cc=raingloom@riseup.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).