From: Julien Lepiller <julien@lepiller.eu>
To: 58497@debbugs.gnu.org, raingloom@riseup.net
Subject: bug#58497: opam import doesn't work with ocaml_intrinsics among others
Date: Thu, 13 Oct 2022 18:37:33 +0200 [thread overview]
Message-ID: <8293CA82-3DB5-420A-843F-BDF3096C6F1B@lepiller.eu> (raw)
In-Reply-To: <87fsfr4s83.fsf@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
(beautify-description #f _)
Seems to be the cause. Yet, there is a description. Maybe parsing ends a bit too soon?
Le 13 octobre 2022 18:07:08 GMT+02:00, Csepp <raingloom@riseup.net> a écrit :
>The error might not be the same for others, I have a slightly patched
>opam->guix-package function.
>
>guix import opam ocaml_intrinsics
>Backtrace:
>In ice-9/boot-9.scm:
> 1752:10 10 (with-exception-handler _ _ #:unwind? _ # _)
>In unknown file:
> 9 (apply-smob/0 #<thunk 7ff952d2f2e0>)
>In ice-9/boot-9.scm:
> 724:2 8 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
>In ice-9/eval.scm:
> 619:8 7 (_ #(#(#<directory (guile-user) 7ff952d34c80>)))
>In guix/ui.scm:
> 2263:7 6 (run-guix . _)
> 2226:10 5 (run-guix-command _ . _)
>In guix/scripts/import.scm:
> 92:11 4 (guix-import . _)
>In guix/scripts/import/opam.scm:
> 105:24 3 (guix-import-opam . _)
>In guix/import/opam.scm:
> 385:24 2 (opam->guix-package _ #:repo _ #:version _)
>In guix/import/utils.scm:
> 290:27 1 (beautify-description #f _)
>In unknown file:
> 0 (string-trim-both #f #<undefined> #<undefined> #<undefi…>)
>
>ERROR: In procedure string-trim-both:
>In procedure string-trim-both: Wrong type argument in position 1 (expecting string): #f
>
>
>
[-- Attachment #2: Type: text/html, Size: 1650 bytes --]
next prev parent reply other threads:[~2022-10-13 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 16:07 bug#58497: opam import doesn't work with ocaml_intrinsics among others Csepp
2022-10-13 16:37 ` Julien Lepiller [this message]
2022-10-16 19:40 ` Csepp
2023-10-11 9:02 ` Simon Tournier
2023-10-12 21:01 ` 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=8293CA82-3DB5-420A-843F-BDF3096C6F1B@lepiller.eu \
--to=julien@lepiller.eu \
--cc=58497@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).