[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: B. W. Fitzpatrick <fitz_at_red-bean.com>
Date: 2002-09-06 14:26:09 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?

Dylan,

Can you provide more information? The most helpful thing you can do in
a situation like this is to post a nice reproduction recipe showing
exactly what you did, from soup to nuts, to cause the
problem. Something like this:

    I'm running Windows version blah blah, SVN version foo compiled using
    mingw. Here's how I blew up the repos:

    $ svnadmin create /myrepos
    $ svn import file:///myrepos /some/dir
    $ svn co file:///myrepos /my/working/copy
    $ cd /my/working/copy
    $ svn mkdir foo
    $ svn ci -m "blah"
    $ svn mv foo bar
    ...
    $ svn mv baz bat
      ERROR MESSAGE QUX: invalid Frozznozzle in the Hoopgart!

Vague descriptions like "I've been moving and mkdir'ing
directories..." really only leave people room to guess at your
problem, so more often than not, you won't get the answer you're
looking for.

-Fitz

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 6 14:26:50 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.