Correction to my previous comment: a no-change rebuild of rust-libphosh-
sys is a better fix than removing rust-libphosh 0.0.7-4 from -proposed.
Both rust-libphosh-sys and rust-libphosh run gir on the Phosh-0.gir
installed in the chroot at build time (debian/rules: deb-gir-tool find
... Phosh-0; gir -o .). librust-libphosh-sys-dev 0.0.7-3 was built in
November 2025 against an older phosh, so it lacks
phosh_status_icon_{get,set}_priority. rust-libphosh 0.0.7-4 is now
generated against phosh 0.57.0-1, which adds them.
Proposed plan:
1. Upload rust-libphosh-sys 0.0.7-3build1 (no-change rebuild) to stonking, so
it is generated from the phosh 0.57 GIR.
2. Once it is built, retry the failed rust-libphosh 0.0.7-4 builds (amd64,
amd64v3, arm64, armhf, ppc64el, s390x) and the riscv64 one if needed.
3. Retry the phrog 0.53.0-2 riscv64 build.
4. rust-libphosh-sys, rust-libphosh and phrog should then migrate together.
With this, the removal request in my previous comment is no longer
needed. This hasn't been test-built yet; a PPA build would confirm it.
Debian unstable has the same combination (phosh 0.57.0-1, rust-libphosh-
sys 0.0.7-3, rust-libphosh 0.0.7-4) and will hit the same failure on the
next rust-libphosh build. The underlying issue is that the two packages
generate code from the GIR independently, with nothing tying them to the
same phosh version. This will be forwarded to Debian.
--
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/phrog/+bug/2168934/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
