Can't update or install raspotify

Kachelkaiser commented 2 years ago

Compatible OS

[ ] I'm running Raspotify on a compatible OS

Latest Version

[X] I'm running the latest version of Raspotify

Due Diligence

[ ] I have done my due diligence

What happened?

Hi,

I run rasportify for some days.

Now I wanted to update to the latest version. But this is not possible via sudo apt-get upgrade or with the installation script

I get the following error:

sudo apt install raspotify

Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:

The following packages have unmet dependencies: raspotify : Depends: libasound2 (>= 1.2.4) Depends: systemd (>= 247.3) but 241-7~deb10u8+rpi1 is to be installed Depends: init-system-helpers (>= 1.60) but 1.56+nmu1 is to be installed E: Unable to correct problems, you have held broken packages.

How can I reinstall raspotify?

Also after running sudo apt update the latest version of e.g. libasound2 is not installing.

Gringles commented 2 years ago

Raspotify recently updated to 0.31.8.1 which added minimum dependencies. This error probably means your OS isn't compatible with Raspotify (e.g. running debian buster when you need debian bullseye). If raspotify was working for you before, try manually downloading 0.31.8 and installing that (it wont throw any errors installing, but might not work once installed).

JasonLG1979 commented 2 years ago

@Gringles hit the nail on the head.

github-actions[bot] commented 2 years ago

The OS referenced is unsupported.

baileyji commented 2 years ago

Looking through the release notes it looks like raspotify is updating in part to keep up with Spotify API changes resulting in work over in librespot. Given that buster is still maintained and in wide deployment "unsupported, closed" is frustrating.

I'm seeing similar, though the list has grown:

         Depends: libc6 (>= 2.31) but 2.28-10+rpt2+rpi1+deb10u1 is to be installed
         Depends: libasound2 (>= 1.2.4)
         Depends: alsa-utils (>= 1.2.4) but 1.1.8-2+rpt1 is to be installed
         Depends: libpulse0 (>= 14.2) but 12.2-4+deb10u1+rpt3 is to be installed
         Depends: systemd (>= 247.3) but 241-7~deb10u8+rpi1 is to be installed
         Depends: init-system-helpers (>= 1.60) but 1.56+nmu1 is to be installed

Is the path forward here to try, to (possibly painfully) rebuild librespot ourselves on buster? Has this been tried and discovered to be a fools errand, hence the lack of support?

For posterity installing rust and then building the release build of 0.4.2 with an up-to-date buster install seems to have worked just fine.

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh cargo build --release

JasonLG1979 commented 2 years ago

Buster may be still deployed in the wild and still supported as "old stable" by Debian, but I'm not Debian. I neither have the time nor desire to support anything but the package I build on Debian Stable.

It may be possible to build on Buster but if you choose to do so you will not be using the package provided by this repo thus doing so and whatever you happen to build is unsupported.

You're on your own.

dtcooper / raspotify