Tiny-QA-tasks.md

@@ -19,9 +19,10 @@ If the package does not fit in any team it should be imported into the [Salvage
 3. Check package tracker for more information at `https://tracker.debian.org/PACKAGENAME`
 4. Check the Homepage of the package. Is `debian/control` pointing to the correct homepage or did it moved
 5. Check the `debian/watch` file whether it reports the latest upstream version correctly
-6. Is `debian/rules` using `dh` or possibly `cdbs` / long `debhelper`.  It might be worth migrating to `dh` in case we  will salvage the package.
-7. Is `debian/copyright` in DEP-5 format?  It might be worth migrating to DEP-5 in case we will salvage the package.
-8. What happens if you run `routine-update -f` on the packaging?  Its migrating the package to latest packaging standards.  It might create some noise since latest packaging standards for instance mean that the upstream testsuite is run in `dh_auto_test` and `dh_mising` defaults to `failmissing`.  These are things you might like to deal with when salvaging the package.
+6. Does `debian/source/format` exist and does it contain `3.0 (quilt)`
+7. Is `debian/rules` using `dh` or possibly `cdbs` / long `debhelper`. It might be worth migrating to `dh` in case we will salvage the package.
+8. Is `debian/copyright` in DEP-5 format? It might be worth migrating to DEP-5 in case we will salvage the package.
+9. What happens if you run `routine-update -f` on the packaging? Its migrating the package to latest packaging standards. It might create some noise since latest packaging standards for instance mean that the upstream testsuite is run in `dh_auto_test` and `dh_mising` defaults to `failmissing`. These are things you might like to deal with when salvaging the package.
 
 ## Some hints