unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 26175@debbugs.gnu.org
Subject: bug#26175: guix download fails if filename contains "@"
Date: Mon, 20 Mar 2017 23:22:40 +0100	[thread overview]
Message-ID: <87wpbjsi4v.fsf@gnu.org> (raw)
In-Reply-To: <4e979de0-b9d9-d489-792c-4a63c91aaba1@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 19 Mar 2017 19:06:22 +0100")

Hello,

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> guix download fails if filename contains "@":invalid character `@' in name
>
>
> $ guix download
> mirror://kde/stable/applications/16.12.3/src/kde-l10n/kde-l10n-ca@valencia-16.12.3.tar.xz
> [...]
> Starting download of /tmp/guix-file.oVF3qZ
> From
> http://mirror.karneval.cz/pub/kde/stable/applications/16.12.3/src/kde-l10n/kde-l10n-ca@valencia-16.12.3.tar.xz...
>  ...cia-16.12.3.tar.xz  2.0MiB            1.4MiB/s 00:01
> [####################] 100.0%
> guix download: error: build failed: invalid character `@' in name
> `kde-l10n-ca@valencia-16.12.3.tar.xz'

To address this we’d need an extra command-line option in ‘guix
download’ to specify the name to use in the store (similar to the
‘file-name’ field in <origin>.)

So one would type:

  guix download --name=foo.tar.xz mirror://…/kde-l10n-ca@valencia-16.12.3.tar.xz

In the meantime, you can work around it by doing something like:

  guix download -o foo.tar.xz mirror://…/kde-l10n-ca@valencia-16.12.3.tar.xz
  guix hash foo.tar.xz

Thanks,
Ludo’.

  reply	other threads:[~2017-03-20 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 18:06 bug#26175: guix download fails if filename contains "@" Hartmut Goebel
2017-03-20 22:22 ` Ludovic Courtès [this message]
2017-03-20 22:30   ` Hartmut Goebel
2017-03-21  8:57     ` Ludovic Courtès

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=87wpbjsi4v.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).