Recently libcurl3, used by the spotify-client, was replaced with libcurl4 which is incompatible. It is impossible to upgrade to libcurl4 without removing spotify client.
The change in libcurl is described in the changelog below; is there any plan to rebuild the spotify-client with libcurl4 soon, so that one can upgrade all the other packages held back because they need libcurl4?
curl (7.60.0-2) unstable; urgency=medium
[ Steve Langasek ] * Build-depend on libssl-dev instead of libssl1.0-dev. * Rename libcurl3 to libcurl4, because libcurl exposes an SSL_CTX via CURLOPT_SSL_CTX_FUNCTION, and this object changes incompatibly between openssl 1.0 and openssl 1.1. * debian/patches/03_keep_symbols_compat.patch: drop, since we are no longer claiming compatibility. * debian/patches/90_gnutls.patch: Retain symbol versioning compatibility for non-OpenSSL builds. Closes: #858398. * Adjust libssl1.1 vs libssl1.0 Suggests/Conflicts; thanks, Adrian Bunk
-- Alessandro Ghedini <*snip*> Wed, 23 May 2018 20:25:39 +0100
FWIW Spotify Linux client is the pick of the bunch.
Agreed, but the problem is for 32-bit linux only (i.e. i386 architecture) there is no updated version of the 32 bit linux client built with the new libcurl4. This means libcurl4 can't be installed without removing spotify-client.
Lack of libcurl4 is blocking about 300 packages so far from getting upgraded.