Arch Linux User Repository

@yochananmarqos clean chroot build hangs forever at 627/628 and I get the following error (something with rust)

process didn't exit successfully: 'rustc --create-name cosmic_comp...

@TechXero: Using a TTY or another DE does not accomplish what I mentioned.

Hint: makepkg -C or build in a clean chroot.

@yochananmarqos I tried building in Cosmic's TTY and on KDE fails on both, KDE results in mentioned error and on Cosmic it fails with rustup error

@TechXero: I can't reproduce that. Do a clean build.

Getting this error while building

==> Starting prepare()...
patching file Cargo.lock
patching file Cargo.toml
patching file cosmic-comp-config/Cargo.toml
error: target was empty

Might need to add this patch until cosmic-comp gets updated to libdisplay-info 0.3.0: https://gitlab.archlinux.org/archlinux/packaging/packages/cosmic-comp/-/blob/c5e3d62f9e145a8ba5f70bf9c1b20d338f48cfbd/update_to_libdisplay-info_3.patch

@xiota: Ah, I see upstream just added a new dependency a few hours ago. Forgive my knee-jerk response, it actually does fail to build. Will fix it shortly.

Package was correctly flagged per flag notice:

Flagging this package should only be done if the sources moved or changes in the PKGBUILD are required because of recent upstream changes.

Relevant portion of log was provided in the flag message. However, someone keeps unflagging without bothering to check the package.

@xiota: Thank you for providing a log. I'll take a look.

Comments are enough. Flagging the package out of date does not change anything.

Fresh clone. Fails to build. Missing depends. Git packages that fail to build as a result of upstream changes are out of date. Reflagging.

error: failed to run custom build command for `libdisplay-info-sys v0.2.0`

Caused by:
  process didn't exit successfully: `/home/builder/build/src/cosmic-comp/target/release/build/libdisplay-info-sys-40cfc7340bd1432c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=/home/builder/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libdisplay-info-sys-0.2.0/Cargo.toml
  cargo:rerun-if-env-changed=LIBDISPLAY_INFO_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=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/builder/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libdisplay-info-sys-0.2.0/build.rs:2:51:
  called `Result::unwrap()` on an `Err` value: PkgConfig(
  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags libdisplay-info libdisplay-info >= 0.1.0 libdisplay-info < 0.3.0

  The system library `libdisplay-info` required by crate `libdisplay-info-sys` was not found.
  The file `libdisplay-info.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 `libdisplay-info.pc`.
  )
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace