From: zimoun <zimon.toutoune@gmail.com>
To: Alice BRENON <alice.brenon@ens-lyon.fr>,
Sarah Morgensen <iskarian@mgsn.dev>
Cc: 49827@debbugs.gnu.org
Subject: bug#49827: Error message for missing synopsis in opam importer
Date: Tue, 17 Aug 2021 09:43:10 +0200 [thread overview]
Message-ID: <868s10pldd.fsf@gmail.com> (raw)
In-Reply-To: <20210811151520.61c85eaa@ens-lyon.fr>
Hi,
I am back from holidays. :-)
On Wed, 11 Aug 2021 at 15:15, Alice BRENON <alice.brenon@ens-lyon.fr> wrote:
> Thanks for your answer Sarah. Simon, I don't know if you have been able
> to make any progress but I wanted to make sure you had seen the patch
> proposal I sent to let the opam importer work from more repositories
> than the few initially defined (opam's official and three for coq):
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49958
I have seen but not read in details. I will do.
>> > The package iter is missing a "synopsis" field as can be seen on
>> > https://opam.ocaml.org/packages/iter/ , which when I tried
>> >
>> > guix import opam iter
>> >
>> > yielded the following backtrace:
>> >
>> > Backtrace:
>> > 8 (primitive-load
>> > "/home/alice/.config/guix/current/bin/g…") In guix/ui.scm:
>> > 2185:7 7 (run-guix . _)
>> > 2148:10 6 (run-guix-command _ . _)
>> > In guix/scripts/import.scm:
>> > 120:11 5 (guix-import . _)
>> > In guix/scripts/import/opam.scm:
>> > 104:23 4 (guix-import-opam . _)
>> > In guix/utils.scm:
>> > 752:8 3 (call-with-temporary-output-file _)
>> > In guix/import/opam.scm:
>> > 337:34 2 (_ _ _)
>> > In srfi/srfi-1.scm:
>> > 460:18 1 (fold #<procedure 7f3baca56fe0 at
>> > guix/import/opam.scm…> …) In guix/import/opam.scm:
>> > 193:15 0 (_ _ _)
>> >
>> > guix/import/opam.scm:193:15: Throw to key `match-error' with args
>> > `("match" "no matching pattern" string-pat)'.
>> >
>> >
>> > the final error is raised l.193 of guix/import/opam.scm because
>> > metadata-ref supports various types for a metadata field, but not
>> > the lack of it. As discussed with Maxime Devos on the IRC channel,
>> > it would be helpful to either allow the import of a package with a
>> > missing field (possibly filling it in the output scheme code for
>> > the imported package with some bad value requiring the user to fill
>> > it and causing any build to crash until replaced properly) or at
>> > least to handle that missing field with a more explicit error
>> > message than the above backtrace (something like "Can't import that
>> > package because it's missing such or such field").
From my understanding, there is 2 issues:
- gentle handler for error
- warn for incomplete metadata
With Jérémy (jeko), we have started to work time to time using
experimental pair-programming to fix the former. Currently, each
importer uses its own error mechanism and obviously incoherence between
them happens; especially when ’--recursive’. We are trying to unify
that.
Thanks for the report of this use case. :-)
Cheers,
simon
next prev parent reply other threads:[~2021-08-17 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 15:01 bug#49827: Error message for missing synopsis in opam importer Alice BRENON
2021-08-02 19:28 ` Sarah Morgensen
2021-08-11 13:15 ` Alice BRENON
2021-08-17 7:43 ` zimoun [this message]
2021-08-19 14:58 ` Alice BRENON
2021-11-21 23:22 ` 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:
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=868s10pldd.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=49827@debbugs.gnu.org \
--cc=alice.brenon@ens-lyon.fr \
--cc=iskarian@mgsn.dev \
/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).