You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am currently writing an ebuild (Gentoo Linux package) for the GURU repository.
While compiling, this error occurred:
error: no matching package named `env_logger` found
location searched: registry `crates-io`
required by package `spot v0.4.0 (/var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0)`
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.
It could also be related to my ebuild. But from what I have found, this often happens without any involvement of a package manager too.
I hope to not waste your time with this.
Info
Full log:
meson compile -C /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0-build --jobs 15 --load-average 0 --verbose
INFO: autodetecting backend as ninja
INFO: calculating backend command to run: /usr/bin/ninja -C /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0-build -j 15 -v
ninja: Entering directory `/var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0-build'
[1/27] /usr/bin/msgfmt -o po/ru/LC_MESSAGES/spot.mo ../spot-0.4.0/po/ru.po
[2/27] /usr/bin/msgfmt -o po/en/LC_MESSAGES/spot.mo ../spot-0.4.0/po/en.po
[3/27] /usr/bin/msgfmt -o po/nl/LC_MESSAGES/spot.mo ../spot-0.4.0/po/nl.po
[4/27] /usr/bin/msgfmt -o po/ca/LC_MESSAGES/spot.mo ../spot-0.4.0/po/ca.po
[5/27] /usr/bin/msgfmt -o po/es/LC_MESSAGES/spot.mo ../spot-0.4.0/po/es.po
[6/27] /usr/bin/msgfmt -o po/fr/LC_MESSAGES/spot.mo ../spot-0.4.0/po/fr.po
[7/27] /usr/bin/msgfmt -o po/de/LC_MESSAGES/spot.mo ../spot-0.4.0/po/de.po
[8/27] /usr/bin/msgfmt -o po/pl/LC_MESSAGES/spot.mo ../spot-0.4.0/po/pl.po
[9/27] /usr/bin/msgfmt -o po/cs/LC_MESSAGES/spot.mo ../spot-0.4.0/po/cs.po
[10/27] /usr/bin/msgfmt -o po/pt/LC_MESSAGES/spot.mo ../spot-0.4.0/po/pt.po
[11/27] /usr/bin/msgfmt -o po/tr/LC_MESSAGES/spot.mo ../spot-0.4.0/po/tr.po
[12/27] /usr/bin/msgfmt -o po/id/LC_MESSAGES/spot.mo ../spot-0.4.0/po/id.po
[12/27] /bin/bash /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0/build-aux/cargo.sh /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0 /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0-build spot src/spot plain '' true
plain
error: no matching package named `env_logger` found
location searched: registry `crates-io`
required by package `spot v0.4.0 (/var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0)`
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.
[26/27] /usr/bin/glib-compile-resources ../spot-0.4.0/src/spot.gresource.xml --sourcedir src --sourcedir ../spot-0.4.0/src --internal --generate --target src/spot.gresource --dependency-file src/spot.gresource.d
FAILED: src/spot
/bin/bash /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0/build-aux/cargo.sh /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0 /var/tmp/portage/media-sound/spot-0.4.0/work/spot-0.4.0-build spot src/spot plain '' true
ninja: build stopped: subcommand failed.
Empty build-aux/cargo.sh before meson compile.
Then, run cargo build after that and move target/release/spot to src/spot so your meson script finds the spot binary and installs it when running meson install.
@Diegovsky Sorry, but I've switched to another distribution in the meantime and am therefore not maintaining any packages in the GURU repository anymore.
There's no chance me testing offline builds with Portage 🤷♂️
@Diegovsky Sorry, but I've switched to another distribution in the meantime and am therefore not maintaining any packages in the GURU repository anymore.
There's no chance me testing offline builds with Portage 🤷♂️
NP! Thanks for taking the time to contribute anyway :)
Describe the bug
Hi, I am currently writing an ebuild (Gentoo Linux package) for the GURU repository.
While compiling, this error occurred:
It could also be related to my ebuild. But from what I have found, this often happens without any involvement of a package manager too.
I hope to not waste your time with this.
Info
Full log:
All crates used:
General information:
The text was updated successfully, but these errors were encountered: