mod_dav_svn: MERGE request failed xx-x.txn/props No such file or directory

I'm cross posting this on users and the developer list, as I'm not 100% sure
it's a bug, but it sure looks like one.

I have subversion set up, and everything works fine using svnserve, but when
I switch over to using http, I always get an error during commits. I get
something similar to the following:

MERGE request failed on '/test3/test'

Can't open directory '/svn/test3/db/transactions/1801.txn/props': No such
file or directory.

I ran apache through strace, and found this:

<snip>

28192 chmod("/svn/test3/db/transactions/18-1.txn/props", 0777) = 0

28192 rename("/svn/test3/db/transactions/18-1.txn/props",
"/svn/test3/db/revprops/19") = 0

28192 open("/svn/test3/db/revprops", O_RDONLY) = 24

.

28192 open("/svn/test3/db/transactions/18-1.txn",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 24

28192 fstat64(24, {st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0

28192 fcntl64(24, F_SETFD, FD_CLOEXEC) = 0

28192 getdents64(24, /* 6 entries */, 4096) = 184

28192 open("/svn/test3/db/transactions/18-1.txn/props",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or
directory)

28192 close(24) = 0

28192 fcntl64(23, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0})
= 0

28192 close(23) = 0

28192 open("/svn/test3/db/transactions/18-1.txn",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 23

28192 fstat64(23, {st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0

28192 fcntl64(23, F_SETFD, FD_CLOEXEC) = 0

28192 getdents64(23, /* 6 entries */, 4096) = 184

28192 gettimeofday({1144185031, 772969}, NULL) = 0

28192 write(7, "[Tue Apr 04 16:10:31 2006] [erro"..., 163) = 163

28192 gettimeofday({1144185031, 773050}, NULL) = 0

28192 write(7, "[Tue Apr 04 16:10:31 2006] [erro"..., 120) = 120

28192 gettimeofday({1144185031, 773123}, NULL) = 0

28192 write(7, "[Tue Apr 04 16:10:31 2006] [erro"..., 160) = 160

28192 writev(22, [{"HTTP/1.1 409 Conflict\r\nDate: Tue"..., 201}, {"<?xml
version=\"1.0\" encoding=\"ut"..., 282}], 2) = 483

As you can see, it renames the props folder to revprops/19, and then tries
to open the props folder (which is obviously not found). It's weird that
nobody else reported this issue, but I don't see how this can be a
configuration thing on my end. Is this a bug?

Russ
Received on Wed Apr 5 00:18:49 2006