From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 55367@debbugs.gnu.org, Rostislav Svoboda <rostislav.svoboda@gmail.com>
Subject: bug#55367: guix refresh fails. struct-vtable: Wrong type argument in position 1 (expecting struct)
Date: Thu, 12 May 2022 11:07:31 +0200 [thread overview]
Message-ID: <fe865a99c8fb32a0c7ccca7f162387d1f63120c0.camel@telenet.be> (raw)
In-Reply-To: <87a6bnmaen.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
Ludovic Courtès schreef op do 12-05-2022 om 10:18 [+0200]:
> To me, the conclusion is that the package has a invalid URI, so it’s not
> a Guix bug strictly speaking. However, we could change
> gnu-maintenance.scm so that it deals with invalid URIs gracefully.
>
> Thoughts?
Maybe emit a warning and skip them? Or just skip them (by returning
#false in the is-it-a-gnu-package procedure)?
Extending Guile to support IRIs can be left for later I think.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-12 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 13:10 bug#55367: guix refresh fails. struct-vtable: Wrong type argument in position 1 (expecting struct) Rostislav Svoboda
[not found] ` <handler.55367.B.16522747076110.ack@debbugs.gnu.org>
2022-05-11 13:15 ` bug#55367: Acknowledgement (guix refresh fails. struct-vtable: Wrong type argument in position 1 (expecting struct)) Rostislav Svoboda
2022-05-11 13:49 ` bug#55367: guix refresh fails. struct-vtable: Wrong type argument in position 1 (expecting struct) Ludovic Courtès
2022-05-11 14:08 ` Maxime Devos
2022-05-11 14:13 ` Maxime Devos
2022-05-12 8:18 ` Ludovic Courtès
2022-05-12 8:57 ` Maxime Devos
2022-05-12 9:07 ` Maxime Devos [this message]
2022-05-12 9:47 ` Rostislav Svoboda
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=fe865a99c8fb32a0c7ccca7f162387d1f63120c0.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55367@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rostislav.svoboda@gmail.com \
/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).