From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 26175@debbugs.gnu.org
Subject: bug#26175: [bug#36976] [PATCH 1/1] download: Map file-name characters not allowed in store.
Date: Sun, 08 Sep 2019 22:07:10 +0200 [thread overview]
Message-ID: <87h85m4knl.fsf@gnu.org> (raw)
In-Reply-To: <d389e39b-1482-c9a7-3034-661b59cbb9b1@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 8 Sep 2019 20:50:15 +0200")
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 04.09.19 um 12:32 schrieb Ludovic Courtès:
>> Hi,
>>
>> Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
>>
>>> (origin
>>> (method url-fetch)
>>> (uri (string-append "mirror://kde//Attic/applications/"
>>> version "/src/kde-l10n/"
>>> "kde-l10n-ca@valencia-" version ".tar.xz"))
>> In this case just add a ‘file-name’ field. I think that’s a reasonable
>> expectation.
>>
>> Thanks,
>> Ludo’.
>
> Agreed. WDYT about adding this as a hint when the error shows up?
>
> How can I catch the "error: invalid character `@' in name" in guix build?
Unfortunately it cannot really be caught. I mean, you could catch
‘&store-protocol-error’ error conditions, but then the error message is
just a string, there’s no error code you can compare against.
Ludo’.
next prev parent reply other threads:[~2019-09-08 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190808144448.25147-1-h.goebel@crazy-compilers.com>
[not found] ` <874l271tf6.fsf@gnu.org>
[not found] ` <c5b96442-0ab8-2472-b387-03ceefd7c588@crazy-compilers.com>
[not found] ` <87woerajr8.fsf@gnu.org>
2019-09-03 14:39 ` bug#26175: [bug#36976] [PATCH 1/1] download: Map file-name characters not allowed in store Hartmut Goebel
2019-09-04 10:32 ` Ludovic Courtès
2019-09-08 18:50 ` Hartmut Goebel
2019-09-08 20:07 ` Ludovic Courtès [this message]
2019-09-26 15:53 ` Hartmut Goebel
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=87h85m4knl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26175@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.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).