Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save bearcatsandor/65716039bc5b05e44ff0d3dfb1e7d061 to your computer and use it in GitHub Desktop.
Save bearcatsandor/65716039bc5b05e44ff0d3dfb1e7d061 to your computer and use it in GitHub Desktop.
crate not found
-pqv '=app-shells/nushell-0.78.0::moonwind'`.
* The complete build log is located at '/var/tmp/portage/app-shells/nushell-0.78.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-shells/nushell-0.78.0/temp/environment'.
* Working directory: '/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0'
* S: '/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0'
>>> Compiling source in /var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0 ...
* cargo build --release --features stable --features dataframe --workspace
error: failed to select a version for the requirement `miette = "^5.6.0"` (locked to 5.6.0)
candidate versions found which didn't match: 5.3.0
location searched: directory source `/var/tmp/portage/app-shells/nushell-0.78.0/work/cargo_home/gentoo` (which is replacing registry `crates-io`)
required by package `nu-cli v0.78.0 (/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0/crates/nu-cli)`
perhaps a crate was updated and forgotten to be re-vendored?
As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without the offline flag.
* ERROR: app-shells/nushell-0.78.0::moonwind failed (compile phase):
* cargo build failed
*
* Call stack:
* ebuild.sh, line 136: Called src_compile
* environment, line 1452: Called cargo_src_compile '--workspace'
* environment, line 571: Called die
* The specific snippet of code:
* "${@}" || die "cargo build failed"
*
* If you need support, post the output of `emerge --info '=app-shells/nushell-0.78.0::moonwind'`,
* the complete build log and the output of `emerge -pqv '=app-shells/nushell-0.78.0::moonwind'`.
* The complete build log is located at '/var/tmp/portage/app-shells/nushell-0.78.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-shells/nushell-0.78.0/temp/environment'.
* Working directory: '/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0'
* S: '/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0'
>>> Compiling source in /var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0 ...
* cargo build --release --features stable --features dataframe --workspace
error: no matching package found
searched package name: `miette`
perhaps you meant: mime
location searched: registry `crates-io`
required by package `nu-cli v0.78.0 (/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0/crates/nu-cli)`
As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without the offline flag.
* ERROR: app-shells/nushell-0.78.0::moonwind failed (compile phase):
* cargo build failed
*
* Call stack:
* ebuild.sh, line 136: Called src_compile
* environment, line 1452: Called cargo_src_compile '--workspace'
* environment, line 571: Called die
* The specific snippet of code:
* "${@}" || die "cargo build failed"
*
* If you need support, post the output of `emerge --info '=app-shells/nushell-0.78.0::moonwind'`,
* the complete build log and the output of `emerge -pqv '=app-shells/nushell-0.78.0::moonwind'`.
* The complete build log is located at '/var/tmp/portage/app-shells/nushell-0.78.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-shells/nushell-0.78.0/temp/environment'.
* Working directory: '/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0'
* S: '/var/tmp/portage/app-shells/nushell-0.78.0/work/nushell-0.78.0'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment