Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to cargo install #989

Closed
1 of 6 tasks
Icelk opened this issue Aug 23, 2021 · 7 comments
Closed
1 of 6 tasks

Unable to cargo install #989

Icelk opened this issue Aug 23, 2021 · 7 comments
Labels
bug A functionality or parts of a program that do not work as intended wontfix Issues that will not be fixed under any circumstances

Comments

@Icelk
Copy link
Contributor

Icelk commented Aug 23, 2021

Description

I'm unable to build with any features.

To Reproduce

It building and installing successfully.

Logs

Click to show logs
Caused by:
  failed to select a version for the requirement `stream-cipher = "^0.3"`
  candidate versions found which didn't match: 0.99.99, 0.7.1, 0.6.0, ...
  location searched: crates.io index
  required by package `aes-ctr v0.3.0`
      ... which is depended on by `librespot-audio v0.1.5`
      ... which is depended on by `librespot v0.1.5`
      ... which is depended on by `spotifyd v0.3.2

Compilation flags

  • dbus_mpris
  • dbus_keyring
  • alsa_backend
  • portaudio_backend
  • pulseaudio_backend
  • rodio_backend

Versions (please complete the following information):

  • OS: Arch
  • Spotifyd: v0.3.2
  • cargo: 1.54.0
@Icelk Icelk added the bug A functionality or parts of a program that do not work as intended label Aug 23, 2021
@ghost
Copy link

ghost commented Sep 1, 2021

I'm having the same issue here

@f0rki
Copy link

f0rki commented Sep 24, 2021

Running with --locked seems to work, but prints the following warnings:

$ cargo install --locked --force --features dbus_mpris,pulseaudio_backend
,dbus_keyring spotifyd
    Updating crates.io index
  Installing spotifyd v0.3.2
warning: package `aes v0.3.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `aes-soft v0.3.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
[...]

It seems the problem is that several packages were yanked from crates.io?

@Icelk
Copy link
Contributor Author

Icelk commented Sep 27, 2021

Can confirm. Thanks for the tip!
Seems bad to use the 10-ish dependencies which were yanked, for whatever reason. Can't help to notice most of them are cryptography-related...

@f0rki
Copy link

f0rki commented Sep 27, 2021

@Icelk I think the work in the PR #977 to upgrade to librespot 0.2 should also fix this issue (no more deps on yanked versions).

@Icelk
Copy link
Contributor Author

Icelk commented Sep 27, 2021

@f0rki Great! Should we keep this open until the PR is merged?

@stale
Copy link

stale bot commented Dec 26, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Issues that will not be fixed under any circumstances label Dec 26, 2021
@stale stale bot closed this as completed Jan 5, 2022
@Icelk
Copy link
Contributor Author

Icelk commented Jan 6, 2022

This seems resolved now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A functionality or parts of a program that do not work as intended wontfix Issues that will not be fixed under any circumstances
Projects
None yet
Development

No branches or pull requests

2 participants