Public bug reported: rust-libphosh 0.0.7-4 fails to build from source in stonking.
Regressing architectures (0.0.7-2 built before, 0.0.7-4 fails now): amd64, amd64v3, arm64, armhf, ppc64el, s390x. (riscv64 built on 2026-06-24, before phosh 0.57 reached the chroot.) Build log(s): - https://launchpad.net/ubuntu/+source/rust-libphosh/0.0.7-4/+build/33005516/+files/buildlog_ubuntu-stonking-amd64.rust-libphosh_0.0.7-4_BUILDING.txt.gz - https://launchpad.net/ubuntu/+source/rust-libphosh/0.0.7-4/+build/33005517/+files/buildlog_ubuntu-stonking-amd64v3.rust-libphosh_0.0.7-4_BUILDING.txt.gz - https://launchpad.net/ubuntu/+source/rust-libphosh/0.0.7-4/+build/33005518/+files/buildlog_ubuntu-stonking-arm64.rust-libphosh_0.0.7-4_BUILDING.txt.gz - https://launchpad.net/ubuntu/+source/rust-libphosh/0.0.7-4/+build/33005519/+files/buildlog_ubuntu-stonking-armhf.rust-libphosh_0.0.7-4_BUILDING.txt.gz - https://launchpad.net/ubuntu/+source/rust-libphosh/0.0.7-4/+build/33005520/+files/buildlog_ubuntu-stonking-ppc64el.rust-libphosh_0.0.7-4_BUILDING.txt.gz - https://launchpad.net/ubuntu/+source/rust-libphosh/0.0.7-4/+build/33005522/+files/buildlog_ubuntu-stonking-s390x.rust-libphosh_0.0.7-4_BUILDING.txt.gz Diagnosis (deterministic matcher): testsuite-failure — dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101. Deeper analysis: this is a compile error that surfaces during cargo test, not a test failure. Root cause: debian/rules regenerates the high-level bindings (src/auto) from the Phosh-0.gir installed in the build chroot. Stonking now has phosh 0.57.0-1, which adds phosh_status_icon_{get,set}_priority. The pre-generated FFI crate librust-libphosh-sys-dev 0.0.7-3 lacks those symbols, so the build fails with: error[E0425]: cannot find function `phosh_status_icon_get_priority` in crate `ffi` --> src/auto/status_icon.rs:330:18 error[E0425]: cannot find function `phosh_status_icon_set_priority` in crate `ffi` --> src/auto/status_icon.rs:370:18 Possible fixes (maintainer choice): 1. Stop regenerating src/auto in debian/rules, or regenerate it against the same GIR that rust-libphosh-sys was generated from. 2. Regenerate rust-libphosh-sys from the phosh 0.57 GIR, upload it first, then rebuild rust-libphosh. 3. Filter phosh_status_icon_{get,set}_priority out of Phosh-0.gir (xmlstarlet) in debian/rules, like the existing phosh fixes. Debian unstable/testing ship the same 0.0.7-4, and their buildd logs predate phosh 0.57, so Debian will likely FTBFS on rebuild too. There is no upstream fix: libphosh-rs has no release after 0.0.7; latest main commit is https://gitlab.gnome.org/World/Phosh/libphosh-rs/-/commit/580d6093944f9805d3efd1fdb38a740b09b53325 ** Affects: rust-libphosh (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs stonking update-excuse ** Tags added: ftbfs stonking update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2168934 Title: rust-libphosh 0.0.7-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-libphosh/+bug/2168934/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
