Summary: | app-crypt/nitrocli-0.4.1 fails to compile (USR-MERGE-SYSTEM): environment: line 1537: shell-complete: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | deso |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/28938 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 893356 | ||
Attachments: | build.log |
Description
Agostino Sarubbo
2023-01-02 09:21:30 UTC
Created attachment 846536 [details]
build.log
build log and emerge --info
I suspect the issue is that you are creating a debug build and we assume release.
> Running `rustc --crate-name shell_complete --edition=2018 var/shell-complete.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=6406dd94465bbc3e -C extra-filename=-6406dd94465bbc3e --out-dir /var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps -L dependency=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps --extern anyhow=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libanyhow-f7d0d2678986ecfe.rlib --extern base32=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libbase32-243fb18d9081bd74.rlib --extern directories=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libdirectories-68a3605648be2bc8.rlib --extern envy=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libenvy-73510d6236ddb679.rlib --extern libc=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/liblibc-9765d293976a2b5a.rlib --extern merge=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libmerge-bfc074c9676bbd78.rlib --extern nitrokey=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libnitrokey-1864d34c9bb2b11e.rlib --extern progressing=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libprogressing-20e683c6ddebc9b7.rlib --extern serde=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libserde-9ea3a5d921a395f7.rlib --extern structopt=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libstructopt-f65135732d76296a.rlib --extern termion=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libtermion-8a238d2fe5bbbf8f.rlib --extern toml=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/deps/libtoml-7688c7a48a42f08f.rlib -L native=/var/tmp/portage/app-crypt/nitrocli-0.4.1/work/nitrocli-0.4.1/target/debug/build/nitrokey-sys-640b53c9349c7098/out`
I can try and use cargo install instead. But either is a bit of a hack, in my opinion.
Is this fixed, Agostino? I take that as a yes. |