Cannot Update Source Tree After Move To Subversion 1.8

Tim Daneliuk tundra at
Tue Jun 25 23:26:44 UTC 2013

On 06/24/2013 04:58 PM, Tim Daneliuk wrote:
> On 06/24/2013 03:20 PM, Matthew Seaman wrote:
>> On 24/06/2013 20:28, Tim Daneliuk wrote:
>>> After the update to svn 1.8, I did a new svn co of the FBSD 9-STABLE
>>> source branch.  When I try to do an update to it, I see this now:
>>>     svn: E155005: Working copy not locked at /usr/scr
>>>     svn co svn:// /usr/src
>>> /usr/src is a symlink to another directory in a separate filesystem,
>>> but this historically worked, so I'm guess that is not the problem.
>>> Ideas?
>> svn upgrade
> Hmmmmm ....
> [root] ozzie ~>svn upgrade /usr/src
> [root] ozzie ~>svn update /usr/src
> svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
> svn: E155004: Working copy '/usr1/src-9-STABLE' locked.
> svn: E155004: '/usr1/src-9-STABLE' is already locked.
> [root] ozzie ~>svn cleanup /usr/src
> [root] ozzie ~>svn update /usr/src
> Updating '/usr/src':
> svn: E155005: No write-lock in '/usr/src/sys'
> svn: E155005: Additional errors:
> svn: E155005: Working copy not locked at '/usr/src'.

It seems that svn 1.8 does not like symlinks.  I have this:

    /usr/src -> /usr1/src-9-STABLE

I can do this fine:

   svn update /usr1/src-9-STABLE

But this causes svn to dump core:

   svn update /usr/src

At which point I have to do a cleanup to get the locks cleared out.

Tim Daneliuk     tundra at
PGP Key:

More information about the freebsd-questions mailing list