Package Details: librespot-git 1:2117.987dfa5d-1

Git Clone URL: https://aur.archlinux.org/librespot-git.git (read-only, click to copy)
Package Base: librespot-git
Description: Open source client library for Spotify
Upstream URL: https://github.com/librespot-org/librespot
Licenses: MIT
Conflicts: librespot
Provides: librespot
Submitter: christoph.gysin
Maintainer: christoph.gysin
Last Packager: christoph.gysin
Votes: 12
Popularity: 0.000000
First Submitted: 2016-09-05 20:30 (UTC)
Last Updated: 2025-09-04 18:58 (UTC)

Dependencies (18)

Required by (6)

Sources (1)

Latest Comments

1 2 3 4 5 Next › Last »

Quaiki8o commented on 2025-09-05 09:19 (UTC) (edited on 2025-09-05 09:21 (UTC) by Quaiki8o)

@christoph.gysin Thanks! That indeed fixes the build.

I also tried to enable rustls-tls-native-roots, which sounds like a good compromise (having the benefits of rustls but still using the system's certificate trust store), but got the conflict again. In case you're considering enabling rustls by default, I would suggest the following:

diff --git a/PKGBUILD b/PKGBUILD
index 830c238..87c5cb4 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -43,7 +43,7 @@ sha256sums=('SKIP')
 _features=(
   # TLS
   #native-tls
-  #rustls-tls-native-roots
+  rustls-tls-native-roots
   #rustls-tls-webpki-roots

   # backends
@@ -81,7 +81,7 @@ build() {

   export RUSTUP_TOOLCHAIN=stable
   export CARGO_TARGET_DIR=target
-  cargo build --frozen --release --features "$_features" --workspace
+  cargo build --frozen --release --no-default-features --features "$_features" --workspace
 }

 check() {
@@ -89,7 +89,7 @@ check() {

   export RUSTUP_TOOLCHAIN=stable
   export CARGO_TARGET_DIR=target
-  cargo test --frozen --release --features "$_features" --workspace
+  cargo test --frozen --release --no-default-features --features "$_features" --workspace
 }

 package() {
@@ -99,6 +99,7 @@ package() {
   cargo install \
       --no-track \
       --locked \
+      --no-default-features \
       --features "$_features" \
       --root "$pkgdir/usr" \
       --path .

christoph.gysin commented on 2025-09-04 19:00 (UTC)

@Quaiki8o I explicitly listed all features except the new -tls ones.

Quaiki8o commented on 2025-09-03 19:31 (UTC)

For me, the build fails on hyper-proxy2, unless I remove every instance of 'cargo [...] --all-features [...]'. Some features seem to conflict when they are enabled at the same time.

rossome commented on 2025-01-24 21:22 (UTC)

I have tweaked the PKGBUILD to fix the build issues I was running into.

christoph.gysin commented on 2024-09-15 13:57 (UTC) (edited on 2024-09-15 15:14 (UTC) by christoph.gysin)

@acidicX This is a -git package, please file a bug upstream or use librespot instead.

Upstream issue: https://github.com/librespot-org/librespot/issues/1336

acidicX commented on 2024-09-10 18:26 (UTC)

@christoph.gysin the package won't build anymore:

error: the lock file /home/.../librespot-git/src/librespot/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.

christoph.gysin commented on 2021-12-19 12:01 (UTC)

@keithspg Apparently the target for armv6h is simply arm-unknown-linux-gnueabihf.

keithspg commented on 2021-12-19 10:12 (UTC) (edited on 2021-12-19 11:03 (UTC) by keithspg)

I have a similar issue to @chilikk, I get this package to build under aarch64 and armv7h but not armv6h. I get this when I try it on RPi:

==> Starting prepare()...
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --target armv6h-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit status: 1)
  --- stderr
  error: Error loading target specification: Could not find specification for target "armv6h-unknown-linux-gnu". Run `rustc --print target-list` for a list of built-in targets

==> ERROR: A failure occurred in prepare().
    Aborting...

When I list the architectures, this is all that lists for armv6

armv6-unknown-freebsd
armv6-unknown-netbsd-eabihf
armv6k-nintendo-3ds

This package last built on December 5 on armv6h and I have updated my system since then. Did rust remove this as a valid architecture? When I comment out the prepare section and remove the --frozen flag it does build but I do not know if it is a functional binary.

Update... If I revert to the commit 9bd43b4 and keep the current rust and llvm-libs, I can get it to build a binary under armv6. I do not know if it works or not, though. It seems that the extra edits since then work for armv7 and aarch64 but not armv6.

christoph.gysin commented on 2021-10-17 13:30 (UTC)

@themooleman I'm afraid I don't know and won't support raspotify. You might want to ask about your issue on https://aur.archlinux.org/packages/raspotify-git.

themooleman commented on 2021-10-17 04:39 (UTC) (edited on 2021-10-17 04:45 (UTC) by themooleman)

I use raspotify (raspotify-git) on a Raspberry Pi 4b. The most recent librespot version broke raspotify.service with journalctl logging the following error:

raspotify.service: Main process exited, code=exited, status=101/n/a

Rolling back to version 1357.68bec41 resolved the issue.

1 2 3 4 5 Next › Last »