Chris 'Xenon' Hanson wrote:
> Stefan Küng wrote:
>>> What would have been the "proper" way to fix this so I can sort it
>>> out if/when it next happens?
>> Update the working copy, run cleanup.
>
> Yeah, I had tried cleanup prior to deleting the props file, without
> success.
Did the cleanup show an error or succeed successfully?
>> If that doesn't work, zip up the corrupted folder and send it to the
>> subversion dev list for analysis.
>
> Exactly how much do you need? Just the .svn? The revision-controlled
> part of my working directory is 130Mb by itself.
Not me, the Subversion devs. And it would be enough to just zip that
particular folder which shows the problem.
>> Do you have some commit hook scripts running on the server which might
>> not work properly? For example, if a post-commit hook script fails (or
>> takes too long because it isn't started as a new process/thread), then
>> the commit succeeds but the working copy isn't updated to reflect the
>> commit.
>
> Just good old /usr/share/subversion/hook-scripts/commit-email.pl. I
> wouldn't expect that to take very long or be prone to failure.
Well, that depends on how you start the script. You should start the
script as a separate process. Which means you should maybe write a
wrapper script which starts the mail script as a separate process and
then terminates immediately.
>> You posted a lot of links to users describing problems with commits,
>> but every one of them was due to different problems.
>
> Well, yes. I posted my symptoms, which were alike to those described by
> others. If I knew what the underlying problem was, I would just fix it
> myself. I spent an entire day Google-ing trying to resolve the problem
> myself, and thought it would be useful to cite what I _had_ found that
> seems to be relevant.
Sure, but don't forget that we don't know what you're exact problem is.
Just posting links to reports of others with similar symptoms is not
enough - we also need to know *your* symptoms.
>> That's all I can think of right now. Maybe you can think of something
>> on your computer/server setup that's not very common?
>
> Pretty vanilla. Ubuntu stock Apache & Subversion. Apache doesn't run
> any web pages, just the repository.
I thought more of your setup on where you run the clients (TSVN and
Ankh). Because you have the problem on the client side, the server setup
shouldn't matter much (besides the commit scripts).
Anyway: if you can't solve this issue, you should report it on the
Subversion mailing list. TSVN as well as Ankh both use the Subversion
libraries for all SVN related operations and don't touch the svn admin
dirs (.svn) themselves.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Oct 1 22:42:38 2007