This bug was fixed in the package cargo - 0.44.1-0ubuntu1
---
cargo (0.44.1-0ubuntu1) groovy; urgency=medium
* New upstream version. (LP: #1876942)
* Update scripts/debian-cargo-vendor to invoke python3 and cope with V2
format Cargo.lock files.
* Refresh patches.
* Embed
@mwhudson It seems the anticipated requirement bump won't happen for 78.
So there is less pressure on this toolchain update. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876942
Title:
rustc
Unfortunately cargo 0.44.1 fails tests on s390x, because rustc 1.43.1 is
segfaulting. The traceback is this:
https://paste.ubuntu.com/p/Ckykd9Mvz7/
which looks upsettingly like a real problem :( I'll try to report it
upstream next week I guess.
--
You received this bug notification because you
On Tue, 26 May 2020 at 22:15, Łukasz Zemczak <1876...@bugs.launchpad.net>
wrote:
> Ok, that makes sense. But I think in this case we would still need this
> to be built in a security-enabled PPA and then copy it over to
> -proposed. Since if in the end we'd want to release this into both
>
Ok, that makes sense. But I think in this case we would still need this
to be built in a security-enabled PPA and then copy it over to
-proposed. Since if in the end we'd want to release this into both
-updates and -security, we can't do that if we build it against
-proposed. So in this case we'd
Yes that's true. The reason for the proposed upload is that the new
rustc does not build on riscv, so getting it into proposed lets us see
if this regresses installability of any other packages in focal. Or at
least I think this was the idea -- I discussed this with vorlon but
didn't write
Hey Michael! Just a quick question: normally we were doing all the rustc
uploads via security, meaning those needed building in a security-
enabled PPA and then bin-copying. But this time I see you're doing a
direct upload to -proposed. Is that on purpose? Did anything change that
I am not aware
** Changed in: cargo (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876942
Title:
rustc 1.43 and cargo 0.44 required by firefox 78
To manage
This bug was fixed in the package cargo - 0.43.1-3ubuntu1
---
cargo (0.43.1-3ubuntu1) groovy; urgency=medium
* Merge from Debian unstable (LP: #1876942): Remaining changes:
- Don't use the bootstrap.py script for bootstrapping as it no longer
works.
- remove
I've just uploaded rustc 1.42 everywhere, will move onto cargo 0.43 and
then rustc 1.43 next. There is a wrinkle around buildability on riscv
but that doesn't matter for firefox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: id-5eb240342d033a7416baa45f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876942
Title:
rustc 1.43 and cargo 0.44 required by firefox 78
To manage notifications about this bug go
11 matches
Mail list logo
