Option 4 --------- Build rust-cargo-c as a vendored package. Once it's vendored, it would have a much lower number of Build-Depends. Then build rust-cargo-c on i386.
We already do this for Rust packages in main according to current MIR team policy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2078055 Title: librsvg needs cargo-c but it's not available on i386 Status in librsvg package in Ubuntu: Triaged Bug description: Starting with the librsvg 2.59 series (2.58.9*), librsvg requires cargo-c to build. cargo-c comes from the Debian source rust-cargo-c. The issue is that librsvg needs to be built on i386, but rust-cargo-c is not currently built for i386. The list of Build-Depends is kinda long. Currently except for librsvg, I believe the only rust-related packages built on i386 are rustc and cargo (which is totally different from cargo-c). https://packages.debian.org/source/unstable/rust-cargo-c Option 1 -------- Stop building librsvg on i386. This might not be practical but it would offer some simplicity. I'm not sure of a perfect way to discover reverse-depends on i386. We may be able to drop gtk4's build dependency on librsvg. It looks like it is optional for cairo, but not sure whether it would be a good idea to attempt to remove it there. Option 2 -------- Build cargo-c as arch:all. Unfortunately, this won't work since cargo-c ships arch-specific binaries unlike many of the rust-* .deb packages. Option 3 -------- Attempt to vendor cargo-c inside the librsvg package. This is what I suspect to be the solution we'll need to go with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
