Search Criteria
Package Details: libzkgroup 0.7.1-3
Git Clone URL: | https://aur.archlinux.org/libzkgroup.git (read-only, click to copy) |
---|---|
Package Base: | libzkgroup |
Description: | Library for the Signal Private Group System. |
Upstream URL: | https://github.com/signalapp/zkgroup |
Keywords: | signal zkgroup |
Licenses: | |
Submitter: | AsamK |
Maintainer: | AsamK |
Last Packager: | AsamK |
Votes: | 1 |
Popularity: | 0.88 |
First Submitted: | 2020-12-15 21:33 |
Last Updated: | 2020-12-23 16:09 |
Dependencies (1)
- cargo (cargo-standalone-git, cargo-nightly-bin, cargo-git, rust-bin, rustup-git, rust-nightly-bin, rust-wasm, rust, rustup) (make)
Latest Comments
1 2 Next › Last »
AsamK commented on 2021-02-24 22:16
upstream has fixed the issue, the build should work again now.
AsamK commented on 2021-02-24 18:07
Ok, I could reproduce it after clearing the cargo cache. The issue is that upstream has force pushed the branch, thus removing the old commit ... https://github.com/signalapp/curve25519-dalek/pull/1#issuecomment-785265272
mkez commented on 2021-02-24 11:28
I cleaned my yay and cargo cache and tried building again, but it still fails. The cargo error is
Unable to update https://github.com/signalapp/curve25519-dalek.git?branch=lizard2#477356e0
followed byobject not found - no match for id (477356e017c7cc2aa168f956786b34690870768f); class=Odb (9); code=NotFound (-3)
AsamK commented on 2021-02-23 20:07
It still builds fine for me. An updated git dependency shouldn't be an issue because the commit hash is fixed in the lock file.
mkez commented on 2021-02-21 12:09
Build fails with
error: failed to get 'curve25519-dalek' as a dependency of package 'zkgroup v0.7.1'
.It seems like https://github.com/signalapp/curve25519-dalek.git?branch=lizard2 has been updated to 3.0.0, but cargo wants 2.0.0.
gue5t commented on 2021-01-06 01:29
Could you please apply the following patch (which simply replaces
target
withCARGO_TARGET_DIR
if the latter is set)?See discussion here for explanation, but in short, it's common and desirable (for improved cache sharing and build times) to set the
CARGO_TARGET_DIR
environment variable, which causes binaries to not be placed in./target/release
but instead in$CARGO_TARGET_DIR/release
. This patch makes the package build in both situations.morganmay commented on 2020-12-23 22:09
Thanks; for some reason it was set to Java 11 instead of Java 15. Changing that fixed it.
AsamK commented on 2020-12-23 22:02
you can use
archlinux-java status
morganmay commented on 2020-12-23 22:00
I have multiple java versions installed. How can I find out which one it's using?
AsamK commented on 2020-12-23 21:42
is there any more error output? Which java package did you install?