mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #571] cargo install fails to compile on Debian/rustc 1.81.0 #1265
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1265
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ShuraShulgin on GitHub (Oct 9, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/571
Describe the bug
error[E0308]:
matcharms have incompatible types appears if I try to install with cargo install spotify_player.To Reproduce
Expected behaviour
A successful installation
Log and backtrace

Environment
Additional context
I've had this working on my home machine and my work pc so I'm quite confused what is happening, I'm running the same script as I did on those machines, all the same setup (Debian 12 in WSL). Script is basically download neovim, download tmux, download rust, install dependencies, install spotify_player. If needed I can create a reduced version of the script just concerning the spotify_player part but that would take a second to extract all that.
@ShuraShulgin commented on GitHub (Oct 9, 2024):
That would defeat the usecase in my circumstance, so no. Also I have 2 different WSL instances on other machines were this works(as stated above) so it cannot be solely WSLs fault.
I'll try different feature flags and report back if something works.
@aome510 commented on GitHub (Oct 9, 2024):
Similar to https://github.com/aome510/spotify-player/issues/560. See the discussion on how to resolve
@ShuraShulgin commented on GitHub (Oct 9, 2024):
Thank you very much, this worked.