[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: assertion failure whilst copying a directory

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-09-06 22:51:25 CEST

"Dylan Cuthbert" <dylan@q-games.com> writes:

> I've been moving and mkdir'ing directories (using svn mv and svn mkdir of
> course) and now I tried to make a copy of trunk/projects and put it into
> branches/test-branch. This is what happened:
>
> $ svn cp trunk/projects/ branches/test-branch/
> assertion "! adm_access->set_owner || apr_hash_count (adm_access->set) == 0"
> failed: file "subversion/libsvn_wc/lock.c", line 438
> Aborted (core dumped)
>
> What have I done wrong? And how do I continue from here? was the directory
> copied? should I delete it and re-issue the command? Or should I revert
> and re-issue the command?

You have hit a check I recently added to the working copy code. It's
not supposed to fail, I don't know of any way to make it happen. It's
a client problem and it occurs while releasing working copy locks.
Releasing working copy locks is usually one of the last things the
client does, so it is likely that the command was "complete".

Perhaps it's too late now, but I'd like to know how you triggered it.
Do you know the status of trunk/projects and branches/test-branch
before the copy? What about after the copy? If you run 'svn st' and
you see lines containing 'L' that indicates directories that are still
locked. You need to run 'svn cleanup' to remove such locks. Before
you do that please look in the .svn directory of the locked directory
to see if there is a file called "log", and if so report what it
contains.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 6 22:52:11 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.