starred/spotify-player
1
0
Fork 0
mirror of https://github.com/aome510/spotify-player.git synced 2026-04-26 17:35:50 +03:00
Code Issues 242 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #594] Update to 0.20.0 failed #344

New issue
Closed
opened 2026-03-02 23:46:44 +03:00 by kerem · 4 comments
kerem commented 2026-03-02 23:46:44 +03:00
Owner
Copy link

Originally created by @Jack-Kaller on GitHub (Nov 1, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/594

Describe the bug
When trying to update spotify-player with cargo-update cargo install-update -a from v0.19.1 to v0.20.0, the build failed

To Reproduce
Updating with cargo update

Expected behaviour
spotify-player update to latest release

Log and backtrace

error: failed to run custom build command for `alsa-sys v0.3.1`
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.

Caused by:
  process didn't exit successfully: `/tmp/cargo-installFFd3FV/release/build/alsa-sys-c8841b6824ac9b3e/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=ALSA_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=ALSA_STATIC
  cargo:rerun-if-env-changed=ALSA_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at /home/jack/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18:

  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags alsa

  The system library `alsa` required by crate `alsa-sys` was not found.
  The file `alsa.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `alsa.pc`.

  stack backtrace:
     0:     0x5721b5f9935a - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h304520fd6a30aa07
     1:     0x5721b5fb9abb - core::fmt::write::hf5713710ce10ff22
     2:     0x5721b5f967b3 - std::io::Write::write_fmt::hda708db57927dacf
     3:     0x5721b5f9a6a2 - std::panicking::default_hook::{{closure}}::he1ad87607d0c11c5
     4:     0x5721b5f9a30e - std::panicking::default_hook::h81c8cd2e7c59ee33
     5:     0x5721b5f9af2f - std::panicking::rust_panic_with_hook::had2118629c312a4a
     6:     0x5721b5f9ac17 - std::panicking::begin_panic_handler::{{closure}}::h7fa5985d111bafa2
     7:     0x5721b5f99839 - std::sys::backtrace::__rust_end_short_backtrace::h704d151dbefa09c5
     8:     0x5721b5f9a8a4 - rust_begin_unwind
     9:     0x5721b5f4e2c3 - core::panicking::panic_fmt::h3eea515d05f7a35e
    10:     0x5721b5f4ec44 - core::panicking::panic_display::h82ff15047a153b55
    11:     0x5721b5f4ed26 - build_script_build::main::h73656c9ec94d1362
    12:     0x5721b5f4eb83 - core::ops::function::FnOnce::call_once::hf9853bf32483c928
    13:     0x5721b5f4eb26 - std::sys::backtrace::__rust_begin_short_backtrace::h5ecc8c1584e954bb
    14:     0x5721b5f4eb09 - std::rt::lang_start::{{closure}}::h006538b62f326db3
    15:     0x5721b5f932f0 - std::rt::lang_start_internal::h4d90db0530245041
    16:     0x5721b5f4eae7 - std::rt::lang_start::h97899f08d1412653
    17:     0x5721b5f4edf5 - main
    18:     0x7b827d029d90 - <unknown>
    19:     0x7b827d029e40 - __libc_start_main
    20:     0x5721b5f4e9f5 - _start
    21:                0x0 - <unknown>
warning: build failed, waiting for other jobs to finish...
error: failed to compile `spotify_player v0.20.0`, intermediate artifacts can be found at `/tmp/cargo-installFFd3FV`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Environment

  • OS: Pop-OS 22.04
  • Application version: 0.19.1
Originally created by @Jack-Kaller on GitHub (Nov 1, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/594 **Describe the bug** When trying to update spotify-player with **cargo-update** `cargo install-update -a` from v0.19.1 to v0.20.0, the build failed **To Reproduce** Updating with cargo update **Expected behaviour** spotify-player update to latest release **Log and backtrace** ``` error: failed to run custom build command for `alsa-sys v0.3.1` note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation. Caused by: process didn't exit successfully: `/tmp/cargo-installFFd3FV/release/build/alsa-sys-c8841b6824ac9b3e/build-script-build` (exit status: 101) --- stdout cargo:rerun-if-env-changed=ALSA_NO_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG cargo:rerun-if-env-changed=ALSA_STATIC cargo:rerun-if-env-changed=ALSA_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR --- stderr thread 'main' panicked at /home/jack/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18: pkg-config exited with status code 1 > PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags alsa The system library `alsa` required by crate `alsa-sys` was not found. The file `alsa.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory. The PKG_CONFIG_PATH environment variable is not set. HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `alsa.pc`. stack backtrace: 0: 0x5721b5f9935a - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h304520fd6a30aa07 1: 0x5721b5fb9abb - core::fmt::write::hf5713710ce10ff22 2: 0x5721b5f967b3 - std::io::Write::write_fmt::hda708db57927dacf 3: 0x5721b5f9a6a2 - std::panicking::default_hook::{{closure}}::he1ad87607d0c11c5 4: 0x5721b5f9a30e - std::panicking::default_hook::h81c8cd2e7c59ee33 5: 0x5721b5f9af2f - std::panicking::rust_panic_with_hook::had2118629c312a4a 6: 0x5721b5f9ac17 - std::panicking::begin_panic_handler::{{closure}}::h7fa5985d111bafa2 7: 0x5721b5f99839 - std::sys::backtrace::__rust_end_short_backtrace::h704d151dbefa09c5 8: 0x5721b5f9a8a4 - rust_begin_unwind 9: 0x5721b5f4e2c3 - core::panicking::panic_fmt::h3eea515d05f7a35e 10: 0x5721b5f4ec44 - core::panicking::panic_display::h82ff15047a153b55 11: 0x5721b5f4ed26 - build_script_build::main::h73656c9ec94d1362 12: 0x5721b5f4eb83 - core::ops::function::FnOnce::call_once::hf9853bf32483c928 13: 0x5721b5f4eb26 - std::sys::backtrace::__rust_begin_short_backtrace::h5ecc8c1584e954bb 14: 0x5721b5f4eb09 - std::rt::lang_start::{{closure}}::h006538b62f326db3 15: 0x5721b5f932f0 - std::rt::lang_start_internal::h4d90db0530245041 16: 0x5721b5f4eae7 - std::rt::lang_start::h97899f08d1412653 17: 0x5721b5f4edf5 - main 18: 0x7b827d029d90 - <unknown> 19: 0x7b827d029e40 - __libc_start_main 20: 0x5721b5f4e9f5 - _start 21: 0x0 - <unknown> warning: build failed, waiting for other jobs to finish... error: failed to compile `spotify_player v0.20.0`, intermediate artifacts can be found at `/tmp/cargo-installFFd3FV`. To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. ``` **Environment** - OS: Pop-OS 22.04 - Application version: 0.19.1
kerem 2026-03-02 23:46:44 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-03-02 23:46:45 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Nov 1, 2024):

The system library alsa required by crate alsa-sys was not found.
The file alsa.pc needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
The PKG_CONFIG_PATH environment variable is not set.

HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing alsa.pc.

Did you try to follow the above instruction?

<!-- gh-comment-id:2451926460 --> @aome510 commented on GitHub (Nov 1, 2024): > The system library `alsa` required by crate `alsa-sys` was not found. > The file `alsa.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory. > The PKG_CONFIG_PATH environment variable is not set. > > HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `alsa.pc`. Did you try to follow the above instruction?
kerem commented 2026-03-02 23:46:45 +03:00
Author
Owner
Copy link

@Jack-Kaller commented on GitHub (Nov 3, 2024):

Yes, alsa seems to be a library and can't be installed as a package on my computer

image

<!-- gh-comment-id:2453327399 --> @Jack-Kaller commented on GitHub (Nov 3, 2024): Yes, alsa seems to be a library and can't be installed as a package on my computer ![image](https://github.com/user-attachments/assets/5eef4e0f-2e7f-40d7-8243-1dec3fd8237a)
kerem commented 2026-03-02 23:46:45 +03:00
Author
Owner
Copy link

@juliamertz commented on GitHub (Nov 3, 2024):

This is indicating you're missing a system dependency required to compile alsa-sys. To fix this on debian based distro's you can run: sudo apt install libasound2-dev

<!-- gh-comment-id:2453446975 --> @juliamertz commented on GitHub (Nov 3, 2024): This is indicating you're missing a system dependency required to compile alsa-sys. To fix this on debian based distro's you can run: `sudo apt install libasound2-dev`
kerem commented 2026-03-02 23:46:45 +03:00
Author
Owner
Copy link

@Jack-Kaller commented on GitHub (Nov 4, 2024):

It worked, thank you ! I'm closing the issue 👍

<!-- gh-comment-id:2454731360 --> @Jack-Kaller commented on GitHub (Nov 4, 2024): It worked, thank you ! I'm closing the issue :+1:
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
phase2
fix-broken-pipe
v0.0.0
v0.23.0
v0.22.1
v0.22.0
v0.21.3
v0.21.2
v0.21.1
v0.21.0
v0.20.7
v0.20.6
v0.20.5
v0.20.4
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.1
v0.18.2
v0.18.1
v0.18.0
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.2
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.1
v0.12.0
v0.11.1
v0.11.0
v0.10.0
v0.9.8
v0.9.6
v0.9.5
v0.9.4
v0.9.3
v0.9.2
v0.9.0
v0.8.0
v0.7.0
v0.6.0
v0.5.2
v0.5.1
v0.5.0
v0.4.0
v0.3.0
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels   
bug

   
documentation

   
enhancement

   
good first issue

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
third-party

   
third-party

   
wontfix
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-player#344
No description provided.