One other issue: streaming from the fallback repository into the newly unstacked repository possibly requires opening a second transport connection where previously we had only one; if this isn't done we'll probably see a smart transport "connection in use" error.
One other issue: streaming from the fallback repository into the newly unstacked repository possibly requires opening a second transport connection where previously we had only one; if this isn't done we'll probably see a smart transport "connection in use" error.