`GCRYPT_1.2' not found on Debian unstable

[kwbr]

With the current Debian unstable the same error as on Fedora (see #33) appears:

$ spotify 
/home/kai/.local/lib/spotify-client/spotify: /home/kai/.local/lib/spotify-client/libgcrypt.so.11: version `GCRYPT_1.2' not found (required by /home/kai/.local/lib/spotify-client/libcef.so)

[kwbr]

BTW, installing the package libgcrypt11 fixes the issue.

[rriemann]

Same issue on opensuse 13.2 64bit. There is no libgcrypt11 in the default repository.

However, someone has build and changing a symlink makes spotiy start.

[leamas]

For those of you on distribtutions not having a libgcrypt11 available, submitting such a prebuilt file makes a lot of sense. This is actually the only thing required to patch spotify-make to handle the situation.

Note that when distributing binary files, it's important to submit the license file as well for whatever license the code is published under.

[SecUpwN]

Same issue on opensuse 13.2 64bit. There is no libgcrypt11 in the default repository.

Experiencing this as well on my openSUSE, getting errors in Spotify-AdKiller. @rriemann, would you please submit this prebuilt file including its license file so that @leamas can patch spotify-make?

[rriemann]

For opensuse 13.2 64 bit

# as root
zypper in http://download.opensuse.org/repositories/home:/fstrba/openSUSE_13.2/x86_64/libgcrypt11-1.5.4-1.1.x86_64.rpm
# as user 
cd ~/.local/lib/spotify-client
mv libgcrypt.so.11{,~}
ln -sv /usr/lib64/libgcrypt.so.11

I do not support the use of the Spotify AdKiller. Dear @SecUpwN, are you premium user?

[SecUpwN]

Thank you @rriemann for answering so fast with a fix! @leamas please implement it.

I do not support the use of the Spotify AdKiller. Dear @SecUpwN, are you premium user?

Yes, I actually am. And that script is NOT meant to circumvent premium, it also doesn't do so.

[leamas]

Hm... In order to do this I need toi create a virtual suse host running zypper. As of now, I'm not motivated enough to do this.

What's needed is

• The 64-bit library as of above.
• The corresponding 32-bit library.
• The license file from any the 64- or 32-bit package (they should be the same).
• The output from lsb-release -i on a suse host.

If someone could provide these one way or another I should be able to update spotify-make to cope with the situation.

[SecUpwN]

@leamas, first of all: Happy New Year! Here we rock:

• The 64-bit library as of above.
• The corresponding 32-bit library.
• The license file from any the 64- or 32-bit package (they should be the same).
• The output from lsb-release -i on a suse host. -> Distributor ID: openSUSE project

[leamas]

Looks good besides the license file. That file is not the license but rather the README. It doesn't even include a license statement.

Since this is a GNU package, there should be a COPYING file somewhere. Can you fix this?

[SecUpwN]

Since this is a GNU package, there should be a COPYING file somewhere. Can you fix this?

I think so. The file in question is located in /usr/share/doc/packages/libgcrypt/COPYING and is just a copy of GPL v2. Let me know if you need anything else, @leamas. Thanks for your great work here.

[leamas]

No, it's not a copy - there is some boilerplate text filled in. I need the real /usr/share/doc/packages/libgcrypt/COPYING

[SecUpwN]

I need the real `/usr/share/doc/packages/libgcrypt/COPYING

Ok, fair. There are actually two different ones: libgcrypt11 has GNU GENERAL PUBLIC LICENSE 2 and libgcrypt20 uses GNU LESSER GENERAL PUBLIC LICENSE 2.1. So which one do you need?

[leamas]

The file related to libgrypt11

[SecUpwN]

The file related to libgrypt11

There ya go, the download link will be valid for 7 days.