-
Notifications
You must be signed in to change notification settings - Fork 29
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
Problem with libgcrypt dependency #42
Comments
Same stuff here, any updates? |
Confirming this as well, I suspect this to be the same case as in leamas/spotify-make#40. Hoping this to be fixed soon, I will then see if this project works with my Spotify-AdKiller and may add it to our |
i am using; System: Host: linux-s4s1 Kernel: 4.5.0-3-default x86_64 (64 bit gcc: 5.3.1) i installed and allowed the install to proceed as 'broken' ; https://gist.github.com/anonymous/d1dd196e8e93df10898f4fc8485b3b1d and also installed the missing dependency; worked for me, should work on tw at least. |
@two-dogs I would like to pay a beer to you. This libcrypt version worked :) |
WORKAROUND on Magea 6 (currently in development version; Cauldron) ( Symlinking from mageia 6 libgcrypt.so.20 did not work; Spotify replies /lib64/libgcrypt.so.11: version `GCRYPT_1.2' not found ) Details see my post https://forums.mageia.org/en/viewtopic.php?f=15&t=11003 |
I work around this issue by installing libgcrypt11 package from https://software.opensuse.org/package/libgcrypt11 |
Great with more ways to get it :) |
https://software.opensuse.org/package/libgcrypt11 -- the official is only 32-bit, I download a 64-bit version and installed with zypper locally - worked on TW @ 1/25/18 |
Hey folks, thanks a lot for your contributions here. I've finally admitted I need to step aside and let someone else with more motivation and free time than me drive this - please see #50. |
I tried to install spotify with a fresh installation of Opensuse Leap 42.1 and I got an error saying
Problem: nothing provides libgcrypt.so.11()(64bit) needed by spotify-client-0.9.17.8.gd06432d.31-1.x86_64
There is some workaround to this?
The text was updated successfully, but these errors were encountered: