Stuart Longland <firstname.lastname@example.org> writes:
> Stuart Longland wrote:
> | Hi All,
> | I've recently got a Subversion repository (after having argued
> | needlessly with CVS) going on a small server I have here. So far, I've
> | been able to check out a working directory, and add files, but I run
> | into problems when I try to commit the changes...[...]
> Is there a bug in Subversion reguarding this that I should know about?
> I'm still not able to commit to the SVN repository, and I need this
> repository up and going as soon as possible.
> I'd like some assistance on this matter. I appreciate the help I've had
> so far, but there's still problems, and I'd like some pointers on how to
> solve them.
How about giving us the exact client and server version, and an exact
transcript of your commands that produce the error?
Looking at your error message (and your apache logs), your client is
successfully doing a MKACTIVITY, which creates a unique writable
127.0.0.1 - stuartl [26/Aug/2003:23:25:46 +1000] "MKACTIVITY
9e8 HTTP/1.1" 201 329
But then your error message comes from this:
[Tue Aug 26 23:09:45 2003] [error] [client 192.168.0.1] Could not
CHECKOUT resource /svn/atomiclinux/!svn/bln/0. [409,
[Tue Aug 26 23:09:45 2003] [error] [client 192.168.0.1] The specified
activity does not exist. [409, #190002]
When you CHECKOUT a file into an activity, you make it writable. The
CHECKOUT request has the activity in the Location: http header. The
error message makes it sound like your client is specifying a bad
Location: header. But of course, we can't verify this, because we
have no HTTP trace of the conversation. So all we can do is ask you
for a reproduction recipe.
(You're not behind some kind of web-proxy, are you? Something that
rewrites http headers? Another theory is that somehow mod_dav_svn is
unable to record the MKACTIVITY data into a database successfully.
Either way, I've never ever seen an error like this before.)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Aug 30 14:34:43 2003