I did it!
I'm running a 3.1 installation on the server now, however..
I just found out that the previous error doesnt appear anymore, but the
svn process still hangs at checkout.
However, this doesnt seem to happen on other clients..
On the client machine I'm running a 3.0 client.. should I upgrade this too?
Is there any way to find out why or where the process is hanging.. it
has always worked and nothing changed (except the server now)
Evert
Ryan Schmidt wrote:
> On Apr 26, 2006, at 05:48, Evert|Collab wrote:
>
>> The last time i did a commit, the svn process hanged. After that I
>> haven't been able to access (that part of) my repo.
>>
>> I tried:
>> svn verify (all revisions verified)
>> svn recover (went allright)
>>
>> After that I hotcopied my repo and used that instead, still the same
>> error.
>>
>> This appeared in the apache2 error log:
>> [Wed Apr 26 04:42:34 2006] [error] [client *****] A failure occurred
>> while driving the update report editor [500, #190004]
>>
>> I'm using a debian package of subversion (on the server), the version
>> is 1.1.4-2.
>
> 1.1.4 is old. The current version is 1.3.1 and I recommend you upgrade.
>
> Are you using a BDB repository? If so, I recommend you upgrade to FSFS.
>
> I recommend you dump the repository to a text file using Subversion
> 1.1.4, then upgrade to 1.3.1, then create a new repository (which will
> automatically use FSFS) and load the dumpfile into it.
>
> http://subversion.tigris.org/faq.html#dumpload
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 26 21:30:01 2006