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

Re: Problem running log

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-10-05 12:02:45 CEST

Niklaus Giger <ngiger@mus.ch> writes:

Is this the complete sequence of commands that you ran?

> Then I started to move a few directories to some other places, removing
> some .exe and *.o files and got into the following errors:
> D 1_5_x/obj/vx_rom_pit.sym
> D bsp/1_1_x/cat.exe
> <...>
> niklaus@K6Linux.localdomain:/data/nm/make$ svn remove 1_5_x/obj
> svn: Attempting restricted operation for modified resource
> svn: Use --force to override this restriction
> svn: '1_5_x/obj/vxWorks_pit.dbg' has local modifications

That's expected if you are trying to delete local modifications, did
you have any? Did you try 'svn remove --force 1_5_x/obj'?

> niklaus@K6Linux.localdomain:/data/nm/make$ svn move 1_5_x/ bsp
> svn: Attempted to lock an already-locked dir
> svn: working copy locked: bsp

That's expected if you try to modify a locked directory. Did 'svn
status 1_5_x/' show a locked directory? Was that a result of the
failed remove command above? If so are you using an old version of
Subversion, 0.14.1 say, or one before rev3026?

> niklaus@K6Linux.localdomain:/data/nm/make$ svn remove bsp/1_1_x/*.exe
> D bsp/1_1_x/bash.exen

Is 'bash.exen' a typo for 'bash.exe'?

> niklaus@K6Linux.localdomain:/data/nm/make$ svn commit
> Deleting 1_1_x/1_1_8
> Deleting 1_5_x/obj/bootConfig.o
> <...>

What did it report for bsp/1_1_x/?

> Adding make
> svn: A problem occured; see later errors for details
> svn: Commit succeeded, but other errors follow:
> svn: Problem running log
> svn: Error bumping revisions post-commit (details follow):
> svn: in directory /mnt/reiser/nm/make/bsp/1_1_x
> svn: start_handler: error processing command 'committed' in
> /mnt/reiser/nm/make/bsp/1_1_x
> svn: log command for dir 'bash.exe' is mislocated

What does 'svn status' on bsp/1_1_x show? Is there a log file
bsp/1_1_x/.svn/log? What does it contain?

> Trying svn cleanup or db_recover didn't help neither.

You run db_recover on the repository db directory to do Berkeley DB4
recovery, it should not be necessary given the above commands. You
run 'svn cleanup' on the working copy to run log files and remove
locks, but if the log file is junk then the working copy is broken.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 5 12:03:29 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.