Package Details: rust-analyzer-bin 20200217-1

Git Clone URL: https://aur.archlinux.org/rust-analyzer-bin.git (read-only, click to copy)
Package Base: rust-analyzer-bin
Description: An experimental Rust compiler front-end for IDEs. Binary build.
Upstream URL: https://github.com/rust-analyzer/rust-analyzer
Keywords: lsp rust
Licenses: MIT, Apache
Conflicts: rust-analyzer, rust-analyzer-git, rust-analyzer-vscode-git
Provides: rust-analyzer
Submitter: murlakatamenka
Maintainer: murlakatamenka
Last Packager: murlakatamenka
Votes: 6
Popularity: 3.98
First Submitted: 2020-01-14 20:33
Last Updated: 2020-02-17 18:50

Dependencies (0)

Required by (0)

Sources (1)

Latest Comments

murlakatamenka commented on 2020-01-28 15:54

The source didn't generate a unique filename for the binary, I see. Thanks, this is fixed and won't be an issue from now on!

amesgen commented on 2020-01-28 11:57

Thanks for your work! I am no expert, but I think this "warning" indirectly applies: https://wiki.archlinux.org/index.php/PKGBUILD#source (namcap also displays a warning)

Steps to reproduce:

 $ git clone https://aur.archlinux.org/rust-analyzer-bin.git
 $ cd rust-analyzer-bin
 $ git checkout 76319798a67115d78ab2611b3f58411e2a74e749
 $ makepkg
# successful build
 $ git checkout 7d8b14e394be19c1eb2b20d62bb60ca49f792632
 $ makepkg
==> Making package: rust-analyzer-bin 20200120-1 (Tue 28 Jan 2020 12:54:20 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found ra_lsp_server
==> Validating source files with md5sums...
    ra_lsp_server ... FAILED
==> ERROR: One or more files did not pass the validity check!

makepkg thinks that it does not have to redownload ra_lsp_server, as the file is already present. This would not happen if the source would be renamed such that it includes the version number. Deleting ra_lsp_server (or a clean build in general) resolves the problem.

murlakatamenka commented on 2020-01-28 11:15

amesgen, ah, sorry, I've fixed the version number.

The name of the source does not depend on the version number, therefore the validity check fails when updating (without doing a clean build).

I update checksum with updpkgsums from pacman-contrib. This should work fine if _pkgver is set correctly. I'll pay more attention with the next week release, sorry to cause troubles for you.

Thanks for the feedback!

amesgen commented on 2020-01-28 09:55

In addition to my other notes: The package version has not been updated in the last commit.

amesgen commented on 2020-01-21 23:17

The name of the source does not depend on the version number, therefore the validity check fails when updating (without doing a clean build).