** Changed in: rust-cargo-c (Ubuntu)
Status: Triaged => 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/2078055
Title:
librsvg needs cargo-c but it's not available on i386
To mana
** Changed in: librsvg (Ubuntu)
Status: Triaged => 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/2078055
Title:
librsvg needs cargo-c but it's not available on i386
To manage no
The autopkgtests are also failing:
https://autopkgtest.ubuntu.com/packages/rust-cargo-c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078055
Title:
librsvg needs cargo-c but it's not available on
Liu,
Matthias sponsored your upload and it fixed the librsvg build. The
excuses report has this complaint though:
librust-cargo-c-dev/i386 has unsatisfiable dependency
I suggest that we build the librust-cargo-c-dev packages on all
architectures except for i386 (or alternatively I guess you coul
The attachment "rust-cargo-c-minor-fix.debdiff" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned b
Hi Jeremy,
Please find the refinement in the patch attached.
** Patch added: "rust-cargo-c-minor-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+attachment/5819451/+files/rust-cargo-c-minor-fix.debdiff
--
You received this bug notification because you are a memb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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/+sou
Liu,
The best practices around Rust vendoring are still a work-in-progress.
It is an interesting technique to use a second .orig tarball to contain
the vendoring. I used a different method when I vendored gnome-snapshot.
Because workflows are not standard yet, could you add a
debian/README.source
(Nothing needs to be done currently on the librsvg side, but I have a
bug task so that this shows up on the proposed-migration excuses report)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078055
Tit
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
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 resolvin
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 y
12 matches
Mail list logo
