Arch Linux User Repository

@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

@xiota: No, it does not fail to build. No, it does not qualify to flag the package out of date.

@serxxx You probably need to run rustup update stable or just rustup update as stable seems to be outated on your machine and LazyCell was stabilized in 1.80.0

You don't see any warning as cosmic-comp does not specify it's MSRV (minimum supported rust version). The repo currently uses 1.80: https://github.com/pop-os/cosmic-comp/blob/master/rust-toolchain.toml, but this PKGBUILD forces the usage of stable. It's fine to just use the latest stable as Rust is (almost always) backwards compatible, so any version higher than 1.80 should work.

@soloturn rustc 1.79.0 (129f3b996 2024-06-10)

It's chosen using rustup because some other rust thing required rustup. So it may be too recent, or not recent enough -- I didn't see any warnings about needing a specific rust version, which often are reported by the build process.

Is there a known good version that these cosmic packages build with? I am building clean, wiping the yay caches for the packages in between; I don't know what I might need to do to purge or clean whatever cruft Rust itself leaves around the filesystem.

@serxxx it works for you now? what does rustc --version say for you?

@serxxx: There is no try, only do. :P

I build in a clean chroot every time I touch my almost 500 AUR packages. Any other issues that may arise building with makepkg or AUR helpers are in userspace. Check your local environment and tool configs.

I've been trying to build these packages for a week or so, with no success. Most recently, the error is in compiling libcosmic, with:

error[E0658]: use of unstable library feature 'lazy_cell'

I suspect builders need to configure something for the Rust compiler to do unsafe things. Could we get a note on the wiki about any special Rust settings users need to make to get these packages to build, for people who aren't familiar with Rust?