I chatted with Zixing today and we agree that Option 4 sounds like a
good option. Alternatively, Zixing suggested this issue would have been
minimized if most Rust packages would be arch:all; then we wouldn't have
to individually enable i386 builds across so many packages as another
way of resolving this issue.
By the way, because this is only a Build-Depends, rust-cargo-c will need
to be added to the permanent i386 allow list in ubuntu-archive-tools
because otherwise in my experience, it will be semi-automatically
removed on i386.
** Also affects: rust-cargo-c (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rust-cargo-c (Ubuntu)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Changed in: rust-cargo-c (Ubuntu)
Importance: Undecided => High
** Changed in: rust-cargo-c (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
