Subversion upgrades of existing dirs

[Garrett Cooper]

On Thu, Dec 22, 2011 at 2:17 PM, Garrett Cooper <yanegomi at gmail.com> wrote:
> On Thu, Dec 22, 2011 at 12:55 PM, Sean Bruno <seanbru at yahoo-inc.com> wrote:
>>
>> Even more strange, on another machine in the cluster I can read and
>> update my tree with subversion-1.7.1 ... but that version doesn't know
>> how to upgrade the tree?  I'm so confused on this.
>>
>> [sbruno at crush /dumpster/scratch/sbruno-scratch/9]$ pkg_info |grep
>> subversion
>> subversion-1.7.1_1  Version control system
>>
>> [sbruno at crush /dumpster/scratch/sbruno-scratch/9]$ svn upgrade
>> svn: E155019: Can't upgrade '/dumpster/scratch/sbruno-scratch/9' as it
>> is not a pre-1.7 working copy directory
>> svn: E150000: Missing default entry
>
> From what I've seen the originally reported error is usually the
> result of two things:
> 1. I can't lock files, because the filesystem doesn't support locking.
> 2. I can't lock files, because of a permissions issue.

Or scenario 3. I just remembered:

3. I can't lock because someone else has the .svn database file(s) locked ;).

> subversion 1.7 doesn't make the difference between these two cases
> intuitive and easy to understand; you might need to ktrace -d the
> process to figure out what the exact issue is (most likely the former
> case based on earlier notes in the thread).

Cheers,
-Garrett