Package Details: rustup-git 1.24.3.r133.gd0804112-1

Git Clone URL: (read-only, click to copy)
Package Base: rustup-git
Description: The Rust toolchain installer
Upstream URL:
Licenses: MIT, Apache
Conflicts: cargo, rust, rust-nightly, rust-nightly-bin, rustfmt, rustup
Provides: cargo, cargo-nightly, lib32-rust-libs, rust, rust-musl, rust-nightly, rust-src, rust-wasm, rustfmt, rustup
Replaces: cargo-tree
Submitter: Jonhoo
Maintainer: ilai
Last Packager: ilai
Votes: 7
Popularity: 0.014532
First Submitted: 2016-05-06 15:30 (UTC)
Last Updated: 2022-03-08 04:43 (UTC)

Dependencies (5)

Required by (2980)

Sources (1)

Latest Comments

Jonhoo commented on 2017-07-18 00:44 (UTC)

@krakhn: this is a -git package, which will always install the latest version. you should only need to flag it out-of-date if it fails to build.

Jonhoo commented on 2016-12-14 05:00 (UTC)

@saghm: Hmm, I cannot reproduce the issue here.. You're sure your rust install is up to date?

saghm commented on 2016-12-13 22:03 (UTC)

I might not have been clear; that's what I meant when I said "removing the package" (the regular Rust package gets automatically pulled in as a build dependency, so I didn't manually install it). The build step worked fine, it just segfaulted when the init step was run.

Jonhoo commented on 2016-12-13 17:20 (UTC)

@saghm: oh, that's weird -- it builds just fine for me. You could try uninstalling rustup-git, installing the regular rust package, and then re-installing rustup-git.

saghm commented on 2016-12-13 16:53 (UTC)

Ah, good to know! Unfortunately, I am getting a build error now: ``` -> Running rustup-init /home/saghm/.cache/pacaur/rustup-git/PKGBUILD: line 24: 15989 Segmentation fault (core dumped) env -u CARGO_HOME "HOME=$srcdir/tmp" target/release/rustup-init -y --no-modify-path ==> ERROR: A failure occurred in build(). Aborting... :: failed to build rustup-git package(s) ``` I tried removing the package and deleting my ~/.multirust and ~/.cargo directories (as well as the previously downloaded files in ~/.cache), but it still gets the same error. I'm not sure if this is an upstream issue or not, but I figured I should mention it in case other people get the same issue.

Jonhoo commented on 2016-08-21 18:34 (UTC)

This is a -git package, so unless it doesn't compile, it isn't out of date.