For this team's purposes, the job is not done until the package gets into
Debian Testing. This is a rigorous QA process the details of which can be read
-about elsewhere. The short version for us, is to run::
+about elsewhere.
+
+Install graphviz and pypy3, then run::
dev/rust-excuses.mk refresh all
problem; the excuses page is the authoritative source on the matter.)
Generally, you should look at the bottom-most packages in this diagram, and
-deal with their issues first. More details for each package can be found at:
+deal with their issues first.
+
+You can also visit the permanent rust transition tracker here:
+
+ https://release.debian.org/transitions/html/rust.html
+
+This page also gives you an overview about architectures being broken for a package.
+Ideally, all rust crates on this site should migrate to testing eventually.
+ More details for each package can be found at:
https://qa.debian.org/excuses.php?package=rust-$crate