From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 37523@debbugs.gnu.org
Subject: bug#37523: Print hint if build fails due to invalid character in package source base name
Date: Thu, 26 Sep 2019 18:01:40 +0200 [thread overview]
Message-ID: <80714a9a-b70d-8810-0f1b-606b8a6b8743@crazy-compilers.com> (raw)
Followup to <http://issues.guix.gnu.org/issue/26175#4>:
guix shall print a hint if building fails due to the package source base
name containing a character invalid in a store filename (e.g. "@" or "%").
Currently, when building such a package, one gets an error message like:
guix build: error: invalid character `@' in name
`kde-l10n-ca@valencia-14.11.80.tar.xz.drv'
guix build should catch this error and print a hint like:
You may add a ‘file-name’ field to the package source to work around this.
Ludovic Courtès wrote on Sun Sep 08 22:07:10+0200 2019
> 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.
Example package raising this error:
(use-modules (guix packages) (guix download) (guix build-system gnu))
(package
(name "kde-l10n-ca-valencia")
(version "14.11.80")
(source
(origin
(method url-fetch)
(uri (string-append "mirror://kde//Attic/applications/"
version "/src/kde-l10n/"
"kde-l10n-ca@valencia-" version ".tar.xz"))
(sha256 (base32
"1mqadassxcm0m9r1l02m5vr4bbandn48xz8gifvxmb4wiz8i8d0w"))))
(build-system gnu-build-system)
(synopsis "") (description "") (license "") (home-page ""))
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next reply other threads:[~2019-09-26 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 16:01 Hartmut Goebel [this message]
2020-12-21 13:37 ` bug#37523: Print hint if build fails due to invalid character in package source base name zimoun
2020-12-21 14:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80714a9a-b70d-8810-0f1b-606b8a6b8743@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=37523@debbugs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.