unofficial mirror of 
 help / color / mirror / code / Atom feed
From: zimoun <>
Subject: bug#53165: "guix import opam coq-of-ocaml" unexpected error
Date: Mon, 10 Jan 2022 18:01:46 +0100	[thread overview]
Message-ID: <> (raw)


For some reasons, the Opam importer is failing for coq-of-ocaml:

--8<---------------cut here---------------start------------->8---
$ guix import opam coq-of-ocaml

Starting download of /tmp/guix-file.058Nel
following redirection to `'...
following redirection to `'...
 …ll.2.5.1.tar.gz  2.3MiB            44.3MiB/s 00:00 [##################] 100.0%
           8 (primitive-load "/home/simon/.config/guix/current/bin/guix")
In guix/ui.scm:
   2206:7  7 (run-guix . _)
  2169:10  6 (run-guix-command _ . _)
In guix/scripts/import.scm:
   124:11  5 (guix-import . _)
In guix/scripts/import/opam.scm:
   105:23  4 (guix-import-opam . _)
In guix/build/utils.scm:
    251:8  3 (call-with-temporary-output-file #<procedure 7ff70d73d500 at guix/import/opam.scm:348:12 (temp port)>)
In guix/import/opam.scm:
   374:37  2 (_ _ _)
In guix/import/utils.scm:
   244:19  1 (beautify-description #f _)
In unknown file:
           0 (string-prefix? "A " #f #<undefined> #<undefined> #<undefined> #<undefined>)

ERROR: In procedure string-prefix?:
In procedure string-prefix?: Wrong type argument in position 2 (expecting string): #f
--8<---------------cut here---------------end--------------->8---


             reply	other threads:[~2022-01-10 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 17:01 zimoun [this message]
2022-01-10 20:36 ` bug#53165: "guix import opam coq-of-ocaml" unexpected error raingloom
2022-01-11 10:51   ` zimoun
2022-06-12  5:15     ` Julien Lepiller

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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

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).