Package Details: rust-nightly-bin 1.50.0_2020.12.05-1

Git Clone URL: https://aur.archlinux.org/rust-nightly-bin.git (read-only, click to copy)
Package Base: rust-nightly-bin
Description: Fast, concurrent, safe. The Rust programming language and its package manager, Cargo.
Upstream URL: https://www.rust-lang.org/
Keywords: cargo development rust
Licenses: custom, MIT, Apache
Conflicts: cargo, cargo-git, cargo-nightly, cargo-nightly-bin, rust, rust-docs, rust-git, rust-nightly
Provides: cargo, cargo-nightly, rust, rust-docs, rust-nightly
Submitter: michaelsproul
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 60
Popularity: 0.43
First Submitted: 2014-04-20 03:15
Last Updated: 2020-12-06 02:08

Required by (1000)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

untitaker commented on 2015-12-27 13:33

Sorry, overlooked the pkgver function below.

I do have a server, yes, and would be happy to set up a cronjob for this script. I still have to learn the new AUR workflow though.

I wonder when it's most effective to run this script. The release times seem to vary a lot, which is why I'm thinking of running the script hourly.

Stebalien commented on 2015-12-21 23:22

_date is the date upstream distributed the package. The date in pkgver is the date the package was built (read from the tarball). I don't currently have a server/always on computer so I run an update script every few days (it's out of date now because the builds were failing last week). If you have a server to run the update script (attached), I'd be happy to add you to the maintainers :).

Update script: https://gist.github.com/Stebalien/25fa39c5d60db7311602

untitaker commented on 2015-12-21 22:25

This package doesn't update with every nightly, and in the current PKGBUILD `pkgver` and `_date` have different values. IIRC there was a bot that took care of this. I'd be interested in helping with such a bot.

bitwave commented on 2015-11-16 17:23

please add conflicts cargo

howesteve commented on 2015-09-29 19:23

@Stebalien Thanks, it worked

Stebalien commented on 2015-09-29 02:56

@howesteve, https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

howesteve commented on 2015-09-29 02:49

Please, how exactly do I overcome the error "unknown public key 5CB4A9347B3B09DC" and install this package?

howesteve commented on 2015-09-29 02:49

Please, how exatly to I overcome the error "unknown public key 5CB4A9347B3B09DC" and install this package?

Stebalien commented on 2015-08-26 03:50

@Jonhoo Done.

Jonhoo commented on 2015-08-25 10:13

When using a source cache for `makepkg` (`SRCDEST` in `/etc/makepkg.conf`), this package is always rebuilt from the same source file since there is nothing telling makepkg that it should download a new source (i.e. there's no checksum, and no version number in the file name). It'd be great if you could add an alternative source name (see https://wiki.archlinux.org/index.php/PKGBUILD#source; use filename::url) that included the pkgver, or better yet, today's date.