Comment 18 for bug 881464

Here are the options I see going forward, in preferred order of precedence:
1. patch the keystone testsuite to work against installed Ubuntu packages (and therefore adding swift and keystoneclient to Build-Depends). This will allow the security, QA and SRU teams to have higher confidence that patches don't break keystone when used against the packages in the archive
2. disable the tests that require git and document somewhere (README.Debian?) how the keystone testsuite can be run against Ubuntu installed packages
3. do nothing

I don't really see '3' as an option since keystone is going to be supported for 5 years and upstream git is going to be constantly evolving while the keystone testsuite being used in the package is going to be static. This means potentially more and more problems when people try to use the integration tests in their personal testing (which we should be doing).

'2' is acceptable but far less desirable as it will also require a QRT script.