Comment 4 for bug 1993819

Note that this is a followup on https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1957932/comments/6 as stated on the description. I’m not going to repost the whole content as most of the issues are now fixed or addressed in the current bug description like the copyright explanation. Thanks for those!

I do have a few remaining questions before the finale MIR team ack:
* Do you mind explaining if the state on the testing strategy since 1.58 is better in Ubuntu now? IIRC, you mentioned previously that we were making the build failing only if too many tests are failing. However, with the comitment to main from the foundation team, the goal was to have a better story here and fix/remove flaky tests (as they are useless anyway: are they flaky because of the tests themselves, or is it due to a flaky behaviour, so in the production code itself? Before investigating, there is no way to know about it).
* I still find there are a lot of warnings during package build (I would say ~300 of valid ones, once you remove the deprecation tests), which is weird for one of the official Rust tooling. Do you know anything we can help to make this better? (the reasoning being: if you got one warning, and another warning, then the next one is just an additional one on the list, which can be a valid issue and go unnotice).
* Finally, at the time of the previous MIR, we got a provisional ACK from the security team, do we need more official approvals there?

Ofc, once the MIR ack is there, we still need to remaining dependencies not fully ACKed yet to be processed.