From: Julien Lepiller <julien@lepiller.eu>
To: Jan Ole Zabel <jan.zabel@posteo.de>, 40858@debbugs.gnu.org
Subject: bug#40858: Cargo in Guix
Date: Sun, 26 Apr 2020 09:39:53 -0400 [thread overview]
Message-ID: <4D816AB7-3207-4375-9E93-5065ACAB152B@lepiller.eu> (raw)
In-Reply-To: <41c810f3-2694-3c59-738f-17b2c3567eb3@posteo.de>
Le 25 avril 2020 18:17:16 GMT-04:00, Jan Ole Zabel <jan.zabel@posteo.de> a écrit :
>Hi,
>
>I just installed the rust package on guix-system and realized I have no
>idea of how to use `cargo` to build something. First, cargo is not in
>my
>search path after installing `rust`, because there is no link in
>`.guix-profile`. There is no dedicated package either.
The rust package has multiple outputs. Its default output doesn't contain cargo, but it has a cargo output which you found in the store. You can install it with:
guix install rust:cargo
>Second, the
>cargo binary installed in `/gnu/store/` throws the following:
>
> $ /gnu/store/*-rust-1.39.0-cargo/bin/cargo install ripgrep
> error: failed to download from
>`https://crates.io/api/ripgrep/12.0.1/download`
>
> Caused by:
> [60] SSL peer certificate or SSH remote key not found (server
>certificate verification failed. CAfile: none CRLFile: none)
>
>A `curl https://crates.io` works normally, so it's not an issue with
>the
>system certificates.
My guess is that curl comes from your foreign system? Guix packages don't read the global location. Have you performed these additional steps after installing guix?
http://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html#X_002e509-Certificates
>
>Am I doing something wrong? Is this even the right place to report or
>ask?
guix-help would have been a better place for this one I think.
I hope this helped a bit :)
Hi,
next prev parent reply other threads:[~2020-04-26 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 22:17 bug#40858: Cargo in Guix Jan Ole Zabel
2020-04-26 13:39 ` Julien Lepiller [this message]
2021-08-08 4:20 ` Maxim Cournoyer
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=4D816AB7-3207-4375-9E93-5065ACAB152B@lepiller.eu \
--to=julien@lepiller.eu \
--cc=40858@debbugs.gnu.org \
--cc=jan.zabel@posteo.de \
/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).