This bug was fixed in the package rust-gst-plugin-gtk4 - 0.15.2-1ubuntu1
---------------
rust-gst-plugin-gtk4 (0.15.2-1ubuntu1) stonking; urgency=medium
* Sync with Debian (LP: #2154448). Remaining changes:
- Run debian/rules vendor to:
+ Update vendored rust crates
+ Update debian/source/include-binaries
+ Update XS-Vendored-Sources-Rust field
- d/control: Update maintainer, add missing quilt B-D.
- d/s/lintian-overrides: Ignore irrelevant nags.
- d/patches/bump-target-lexicon-riscv64a23.patch: bump cfg-expr to 0.20.8
in Cargo.lock, pulling target-lexicon 0.13.5. The previously-vendored
0.12.16 (pinned transitively via system-deps -> cfg-expr 0.17.2) does
not recognise the riscv64a23-unknown-linux-gnu triple, so its build
script panics with "Invalid target name:
'riscv64a23-unknown-linux-gnu'" and FTBFS on riscv64. Only required for
the Ubuntu vendored build, which resolves crates from Cargo.lock; Debian
builds against the packaged target-lexicon (>= 0.13.4).
- d/patches/require-gtk-v4_10.patch: pin the base gtk dependency to the
v4_10 feature. gst-plugin-gtk4 0.15.2 unconditionally compiles the
render widget which needs GTK 4.10 API (upstream default =
["gtk_v4_10"]), so building against the gtk4-rs v4_6 baseline FTBFS
(gtk::Accessible not found). Dependency features are always on
regardless of --no-default-features, so this makes every feature
combination - including the per-feature autopkgtests - build against
GTK 4.10 and pass.
-- Charles <[email protected]> Mon, 20 Jul 2026 18:16:29 +0100
** Changed in: rust-gst-plugin-gtk4 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2154448
Title:
Please merge 0.15.2-1 into Stonking
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-gst-plugin-gtk4/+bug/2154448/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
