Using latest cargo-binstall==1.7.3 release, I was trying to install atuin through:
cargo-binstall -y -v atuin
But found it was falling back to installation from source despite the packages being available in atuin's Github releases.
As you can see in the logs below, it correctly is trying to download from https://github.com/atuinsh/atuin/releases/download/v18.3.0/ but then tries two patterns of atuin-v18.3.0-{platform}.tar.gz before giving up. But doesn't try atuin-{platform}.tar.gz which atuin changed to in the 18.3.0 release (previously putting the version string in there).
What's weird about this is { name }-{ target }{ archive-suffix } ("versionless") is listed in the supported cargo-binstall url templates, and there is no binstall metadata info in atuin's Cargo.toml, so I don't know why it's not checking those here. But I did notice they switched to cargo-dist==0.16 for their 18.3 release, so it could be related to that?
Using latest
cargo-binstall==1.7.3
release, I was trying to install atuin through:But found it was falling back to installation from source despite the packages being available in atuin's Github releases.
As you can see in the logs below, it correctly is trying to download from
https://github.com/atuinsh/atuin/releases/download/v18.3.0/
but then tries two patterns ofatuin-v18.3.0-{platform}.tar.gz
before giving up. But doesn't tryatuin-{platform}.tar.gz
which atuin changed to in the 18.3.0 release (previously putting the version string in there).What's weird about this is
{ name }-{ target }{ archive-suffix } ("versionless")
is listed in the supported cargo-binstall url templates, and there is nobinstall
metadata info in atuin'sCargo.toml
, so I don't know why it's not checking those here. But I did notice they switched tocargo-dist==0.16
for their 18.3 release, so it could be related to that?Debug logs:
(Failure here because I didn't have cargo/rust installed on this machine)