[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Repository corruption with two access on repository

From: Manuel VACELET <manuel.vacelet-abecedaire_at_st.com>
Date: 2005-04-07 12:20:18 CEST

Saulius Grazulis wrote:
> On Wednesday 06 April 2005 18:36, Manuel VACELET wrote:
>>>I tried with subversion 1.1.4, error messages seems more relevant:
>>I now try with fsfs backend and it works.
> Could it be that accessing repository over file:// resets ownership of the
> database or directories, and after apache is not permitted to access the
> repository?
> With fsfs you don't notice this since every revision (delta) is stored in a
> separate file, and you do not need to write thas file any more, right?
> Similar, when we run subversion over svn+ssh://, the Subversion Book says our
> repository has to have permissions for group to write into it -- if we want
> every user to commit under his/her own name. And the server runs under umask
> 002 so that new files remain group writable.

Yes, I didn't RTFM enough before posting :/
I read this part of the book after Mark message and it works with bdb.
Thanks a lot.

>>Well, but not very convenient.
> Why? FSFS is nice -- you just look into db/revs/, and immediately see what
> revisions you have there, and rsync shows you what has been backed-up.
> Honestly, I do not see any charm in big f(l)at databases... ;).

I know, I founded FSFS very nice too, but I currently have some external
constraints that imply bdb.

# VACELET Manuel     manuel.vacelet-abecedaire(at)st(dot)com #
# Tel:  042 6089                          +33 (0)476 92 6089 #
# STMicroelectronics - HPC/STS                               #
# 850, rue Jean Monet - 38926 CROLLES CEDEX - FRANCE         #
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 7 12:46:41 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.