[GH-ISSUE #785] RUSTLS dependency no longer on crates.io #1402

Closed
opened 2026-03-14 14:40:05 +03:00 by kerem · 4 comments
Owner

Originally created by @noahknegt on GitHub (Jul 29, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/785

Describe the bug
When following the install steps even with only the default features, the cargo install fails due to a yanked dependency. To be exact rustls version 0.23.30.

To Reproduce

  1. Run cargo install spotify_player

Log and backtrace

noah@framework-13:~$ cargo install spotify_player
    Updating crates.io index
  Installing spotify_player v0.20.7
    Updating crates.io index
error: failed to compile `spotify_player v0.20.7`, intermediate artifacts can be found at `/tmp/cargo-installdSkw2m`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Caused by:
  failed to select a version for the requirement `rustls = "^0.23.30"`
    version 0.23.30 is yanked
  location searched: crates.io index
  required by package `spotify_player v0.20.7`

Environment

  • OS: Debian 13 (trixie)
  • Application version: 0.20.7
Originally created by @noahknegt on GitHub (Jul 29, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/785 **Describe the bug** When following the install steps even with only the default features, the cargo install fails due to a yanked dependency. To be exact rustls version 0.23.30. **To Reproduce** 1. Run `cargo install spotify_player` **Log and backtrace** ``` noah@framework-13:~$ cargo install spotify_player Updating crates.io index Installing spotify_player v0.20.7 Updating crates.io index error: failed to compile `spotify_player v0.20.7`, intermediate artifacts can be found at `/tmp/cargo-installdSkw2m`. To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. Caused by: failed to select a version for the requirement `rustls = "^0.23.30"` version 0.23.30 is yanked location searched: crates.io index required by package `spotify_player v0.20.7` ``` **Environment** - OS: Debian 13 (trixie) - Application version: 0.20.7
kerem 2026-03-14 14:40:05 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@KUHLwasStolen commented on GitHub (Jul 30, 2025):

I will look into just replacing the version with 0.23.31
The latest release notes don't mention any breaking changes so it should hopefully cause no problems.

<!-- gh-comment-id:3135624233 --> @KUHLwasStolen commented on GitHub (Jul 30, 2025): I will look into just replacing the version with `0.23.31` The latest release notes don't mention any breaking changes so it should hopefully cause no problems.
Author
Owner

@KUHLwasStolen commented on GitHub (Jul 30, 2025):

Ok so I cannot fully reproduce the error message that you are getting, the closest I got was this:

$ cargo install spotify_player --locked
    Updating crates.io index
  Installing spotify_player v0.20.7
    Updating crates.io index
warning: package `rustls v0.23.30` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

I only get this when running with --locked and not without it.

Independent of this I do not get errors or warnings when bumping the rustls version to 0.23.31 and spotify_player seems to install just fine.

<!-- gh-comment-id:3135836819 --> @KUHLwasStolen commented on GitHub (Jul 30, 2025): Ok so I cannot fully reproduce the error message that you are getting, the closest I got was this: ```shell $ cargo install spotify_player --locked Updating crates.io index Installing spotify_player v0.20.7 Updating crates.io index warning: package `rustls v0.23.30` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked ``` I only get this when running with `--locked` and not without it. Independent of this I do not get errors or warnings when bumping the `rustls` version to `0.23.31` and `spotify_player` seems to install just fine.
Author
Owner

@noahknegt commented on GitHub (Jul 30, 2025):

I will verify again later today, but you might have a locally cached version of it thus cargo finding it, for me it was on a clean system.

<!-- gh-comment-id:3136577411 --> @noahknegt commented on GitHub (Jul 30, 2025): I will verify again later today, but you might have a locally cached version of it thus cargo finding it, for me it was on a clean system.
Author
Owner

@KUHLwasStolen commented on GitHub (Jul 30, 2025):

Yeah something like this is most likely the case.
Anyway, using the latest rustls version will solve your error and my warning and I will open a pull request to fix this.

<!-- gh-comment-id:3136675243 --> @KUHLwasStolen commented on GitHub (Jul 30, 2025): Yeah something like this is most likely the case. Anyway, using the latest `rustls` version will solve your error and my warning and I will open a pull request to fix this.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-player#1402
No description provided.