Comment 6 for bug 1390533

Ok, I was able to reproduce the above error in a separate silo so as not to trample over jhodapp's work. I then loaded the code down with crazy amounts of debug logging everywhere that any deletion happens in the entire code. Then I found this:

https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-010-1-build/52/console

2014-11-07 19:29:22,623 DEBUG Deleting!: extracted_generated_source: /var/lib/jenkins/silos/ubuntu-rtm/landing-010/unity-scopes-api: Exists? True

This was quite curious as I was expecting the value to be /var/lib/jenkins/silos/ubuntu-rtm/landing-010/generated/unity-scopes-api. So indeed it turns out that there was a bug in my path handling code that caused the wrong directory to be sent for deletion. The reason for all the confusion was that, as I suspected, there was no code saying 'go delete a .bzr directory', but what was happening was actually the entire source branch was being deleted, and then a different source tree (without the branch) was being copied in it's place by some later code. Of course, how that other build succeeded with the same code is yet another mystery.

So I'm pretty sure this is fixed now, just doing some further tests to confirm it.