Search Criteria
Package Details: b3sum 0.3.7-1
Git Clone URL: | https://aur.archlinux.org/b3sum.git (read-only, click to copy) |
---|---|
Package Base: | b3sum |
Description: | Command line implementation of the BLAKE3 hash function |
Upstream URL: | https://github.com/BLAKE3-team/BLAKE3 |
Licenses: | |
Submitter: | polyzen |
Maintainer: | polyzen |
Last Packager: | polyzen |
Votes: | 11 |
Popularity: | 0.129747 |
First Submitted: | 2020-01-10 03:32 |
Last Updated: | 2020-10-02 03:53 |
Latest Comments
andrius4669 commented on 2020-05-28 20:44
@oconnor663 looks like that was my issue, thanks. sorta forgot I was even using rustup instead of packaged stuff. tests could have more descriptive warning/error messages in that regard though.
oconnor663 commented on 2020-05-26 22:08
@andrius4669 the tests require Rust 1.43. You might need to
rustup update
.andrius4669 commented on 2020-05-26 21:41
got error during check:
oconnor663 commented on 2020-04-28 19:19
The upstream GitHub project now attaches prebuilt binaries to release tags. If we wanted to do a -bin variant package, that's an option.
oconnor663 commented on 2020-02-27 17:39
Ok that makes sense. I'll try to be more hygienic with my future crates.io uploads.
polyzen commented on 2020-02-27 17:28
We use
--locked
for reproducible builds.https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
https://wiki.archlinux.org/index.php/DeveloperWiki:ReproducibleBuilds
oconnor663 commented on 2020-02-27 14:44
Interesting, I just noticed that the untarred files from crates.io include a Cargo.lock file, and that lockfile pins
blake3
0.2.1 (rather than 0.2.2). This is probably an artifact of me publishing both crates at the same time without cleaning the repo in between.cargo install b3sum
ignores that lockfile by default, but runningcargo build
inside the untarred source tree respects it. I'm not sure what the right thing to do is here. Maybe delete the lockfile before the build? There could be important security updates for dependencies, and it's possible thatb3sum
itself might not publish an update for a long time.oconnor663 commented on 2020-01-13 20:30
The build probably depends on GCC, since the "c_avx512" feature is enabled by default in this crate, though I haven't tested it on a system without a C compiler yet.
oconnor663 commented on 2020-01-13 18:28
Thank you for putting this up so quickly!