Hi, I am trying to find out if some new behavior we see with version 1.7 is considered a bug (I would).
What we try to do is assembling a larger piece of software from tens or hundreds of repositories. In that, checkouts might also live within checkouts of other svn repositories. We usually checkout these in parallel, but because the contained checkout isn't using a subdirectory name that would be part of the containing repository, this wasn't a problem in the past. However, version 1.7 seems to change this. Trying to checkout the contained repository while the containing repository isn't finished yet (parallel checkout) produces errors like svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted My theory is that the checkout of the contained repository tries to look into .svn of the containing repository, and finds it 'currently used'. This was not the case for versions <1.7, maybe because these didn't use a 'central' .svn directory. I would now argue that this is a regression, since svn <1.7 worked fine in this scenario, while >=1.7 doesn't. Ways to reproduce: 1. svn co some_repo 2. interrupt during checkout (control-Z) 3. cd into new (partial) checkout 4. svn co some_other_repo thanks, Frank Loeffler
signature.asc
Description: Digital signature
