Search Criteria
Package Details: kr 2.4.14-1
| Git Clone URL: | https://aur.archlinux.org/kr.git (read-only) |
|---|---|
| Package Base: | kr |
| Description: | SSH using a key stored in Krypton |
| Upstream URL: | https://github.com/kryptco/kr |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | kryptco |
| Maintainer: | kryptco |
| Last Packager: | kryptco |
| Votes: | 6 |
| Popularity: | 0.771732 |
| First Submitted: | 2017-08-13 18:56 |
| Last Updated: | 2018-12-17 18:48 |
Dependencies (6)
- gcc-libs-multilib (gcc-libs-multilib-x32, gcc-libs-git, gcc-libs-multilib-git, gcc-libs)
- git (git-git) (make)
- go (go1.13-pie, gcc-go-git, gcc-go, go-pie) (make)
- nodejs (nodejs-git, nodejs-0.12, nodejs6-bin, nodejs-lts-carbon, nodejs-lts-dubnium) (make)
- rsync (rsync-git, rsync-fadvise) (make)
- rustup (rustup-git) (make)
Latest Comments
1 2 3 Next › Last »
mercxry commented on 2019-04-08 12:47
@L3vi47h4N Seems like there is a temporary workaround for that, https://github.com/kryptco/kr/issues/254#issuecomment-464890476
L3vi47h4N commented on 2019-03-06 17:30
Heyya! Seems cargo is once again causing build failures. The last few lines I get off the install are:
error: error: failed to parse manifest at
/home/user/.cache/yay/kr/src/src/github.com/kryptco/kr/sigchain/Cargo.tomlCaused by: virtual manifests do not specify [target]
make[1]: [Makefile:25: libsigchain-with-dashboard] Error 101 make[1]: Leaving directory '/home/user/.cache/yay/kr/src/src/github.com/kryptco/kr/sigchain' make: [Makefile:50: all] Error 2
Regards!
kryptco commented on 2018-12-17 18:50
Version 2.4.14 now uses the latest version of cargo-web which should fix the openssl-related build issues. Thanks everyone for reporting!
mprom commented on 2018-11-05 08:47
Hey kryptco, I think you should add running
kr uninstallto the package uninstall hook, as right now uninstalling the package as one normally uninstalls packages from the AUR (likeyay -R kr) leaves SSH unusablePyrepenol commented on 2018-10-21 02:57
got cargo-web to install with this
env OPENSSL_INCLUDE_DIR=/usr/include/openssl-1.0 OPENSSL_LIB_DIR=/usr/lib/openssl-1.0 cargo install -f --version 0.6.10 cargo-web
unomar commented on 2018-10-17 15:14
Yeah, when I run makepkg that way I get:
error: could not find native static libraryssl, perhaps an -L flag is missing?kryptco commented on 2018-10-16 20:08
Have you tried running makepkg with the same
envcommand prepended as in the GitHub issue?unomar commented on 2018-10-16 20:03
@kryptco Thanks for the link. I managed to get cargo-web 0.6.10 installed, but that only got me a little further. Running makepkg I get this error:
error: failed to run custom build command for `openssl-sys v0.9.23 (<https://github.com/kryptco/rust-openssl#f87423dd>)It seems to be ignoring or missing the OPENSSL envvars and finding OpenSSL 1.1.1 as this error follows below:
This crate is only compatible with OpenSSL 1.0.1, 1.0.2, and 1.1.0, or LibreSSL 2.5 and 2.6.0, but a different version of OpenSSL was found. The build is now aborting due to this version mismatch.kryptco commented on 2018-10-13 19:20
@unomar thank you for reporting this. We are awaiting an upstream openssl depdendency update, but in the meantime you can workaround this issue following the instructions here: https://github.com/kryptco/kr/issues/237#issuecomment-422183393
unomar commented on 2018-10-09 18:40
I'm getting issues while attempting to build cargo-web. It appears to be related to rust-openssl & openssl 1.1.1 refereced here: https://github.com/sfackler/rust-openssl/issues/994
error: failed to run custom build command for `openssl v0.9.24` process didn't exit successfully: `/tmp/cargo-installq4ar12/debug/build/openssl-959868a99e49436a/build-script-build` (exit code: 101) --- stderr thread 'main' panicked at 'Unable to detect OpenSSL version', /home/<user>/.cargo/registry/src/github.com-1ecc6299db9ec823/openssl-0.9.24/build.rs:16:14 note: Run with `RUST_BACKTRACE=1` for a backtrace.