Dan Allen wrote:
>>The errors he's talking about are caused by something being committed to
>>the file between his commits. The server knows that, and will not allow
>>a commit without an update first.
>>
>>
>
>Well let me jump from here. I mentioned to the list that somehow
>the repository gets "out of sync" complaining that there is a newer
>file on the server when I know for a fact there is not because not
>only am I the only one committing right now (no I do not have a
>post-commit hook because I am evaluating svn and I want to make sure
>that it can work for us at the very primitive level first before
>getting fancy). I do an svn update but it just says the repository
>version number and ends, meaning there are no new updates, but when
>I go to commit, it won't go. I even touch and change the file I am
>committing, still no dice. The clocks are pretty much the same on
>both server in client (maybe only off by a half a minute a most).
>Do I think in the long run there should be a force that might break
>the repository, probably not. Is it necessary while this bug
>exists....it would be helpful.
>
>Client: 0.20.1
>Server: 0.20.1
>
>
Well, can you please tell us which platform you're using, where you got
the SVN binaries or how you compiled them, and the exact command
sequence (including repository creation) that lets you reproduce this
problem? The fact is, we have a zillion tests that do exactly what you
claim you're doing, and they pass on quite a few platforms.
As Garrett said, without a detailed bug report, we can't even begin to
gues what's going on.
And no, there should not be a --force that hides bugs, if this is indeed
a bug. Such an option is just plain wrong. If it's a user error, then
it's even wronger.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 28 18:21:56 2003