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 need: upload to security-ppa (or tinkered bileto), bin sync to -proposed, testing in -proposed, release to -updates/-security.
Does that make sense? Or is the plan different? -- 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 to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1876942/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
