Bug 889360 – app-crypt/nitrocli-0.4.1 fails to compile (USR-MERGE-SYSTEM): environment: line 1537: shell-complete: No such file or directory

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2023-01-02 09:21:30 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: app-crypt/nitrocli-0.4.1 fails to compile (USR-MERGE-SYSTEM).
Discovered on: amd64 (internal ref: usr-merge_tinderbox)

NOTE:
(USR-MERGE-SYSTEM) in the summary means that the bug was found on a machine that runs default/linux/amd64/17.1/systemd/merged-usr profile but this bug MAY or MAY NOT BE related to the new profile.

[Comment 1 Agostino Sarubbo 2023-01-02 09:21:33 UTC]

Created attachment 846536 [details]
build.log

build log and emerge --info

[Comment 2 deso 2023-01-02 18:17:36 UTC]

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.

[Comment 3 deso 2023-02-06 13:45:11 UTC]

Is this fixed, Agostino?

[Comment 4 deso 2023-02-12 17:40:54 UTC]

I take that as a yes.