From: ludo@gnu.org (Ludovic Courtès)
To: Dmitry Nikolaev <cameltheman@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Ampersand sign (&) in URL.
Date: Tue, 04 Oct 2016 15:35:06 +0200 [thread overview]
Message-ID: <87d1jg8cfp.fsf@gnu.org> (raw)
In-Reply-To: <CAH3JXcEka334NZ2FjmUNo6ZF30tkkqFXcJZDCSqVCvOdwXqr4w@mail.gmail.com> (Dmitry Nikolaev's message of "Tue, 4 Oct 2016 13:50:04 +0300")
Dmitry Nikolaev <cameltheman@gmail.com> skribis:
> But it's download URL contains ampersand sign (&).
>
> http://astralinux.com/images/fonts/PTAstraSans&Serif_TTF_ver1001.zip
>
> Guix returns
>
> build failed: invalid character `&' in name
> `PTAstraSans&Seif_TTF_ver1001.zip.drv'
>
> How do I escape & in URL so guix accept it?
Instead of escaping it, add a ‘file-name’ field in the ‘origin’ form
that does not contain the offending character:
(origin
(method url-fetch)
(uri …)
(sha256 …)
(file-name "the-font.zip"))
HTH!
Ludo’.
next prev parent reply other threads:[~2016-10-04 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 10:50 Ampersand sign (&) in URL Dmitry Nikolaev
2016-10-04 10:56 ` Hartmut Goebel
2016-10-04 13:35 ` Ludovic Courtès [this message]
2016-10-04 14:43 ` Vincent Legoll
-- strict thread matches above, loose matches on Subject: below --
2016-10-04 12:44 Dmitry Nikolaev
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=87d1jg8cfp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cameltheman@gmail.com \
--cc=help-guix@gnu.org \
/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.
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).