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

permision problems just after migrating from bdb to fsfs

From: ycdtosa <ycdtosa_at_eupla.unizar.es>
Date: 2005-09-13 15:54:37 CEST

Hi i'm working with svn 1.1.x on a RH7.x plataform, and i want ot update
to svn 1.2.x
because i 'need' to lock a few files :-). At the same time i want to
make all my repos
of the same type (fsfs) so i figured this could be a two steps process:
------
 Step 1- Migrate the repository to fsfs (do not change any binary).
 Step 2- Since repo is compatible, upgrade the binaries.

-----
I never got to the second point :-(, and here is why i need help:

I just migrated a repository from BDB to fsfs format by means of the
following commands...

> cd /path/to/repositories_root

#save the previous svnserver.conf file.
> cp myrepo/conf/svnserver.conf previous.conf

#get the dump file
> svnadmin dump myrepo > myrepo.dump
[...]

> rm -rf myrepo

#create the new repo and load!
> svnadmin create --fs-type fsfs myrepo
> svnadmin load myrepo < myrepo.dump

#restore the config.
> cp previous.conf myrepo/conf/svnserver.conf

It did seem to work, and i tested to checkout some files and it worked,
but now, when i try to commit i get the following error

(as read from tortoise, but it sure seems a server side error)

Error: Commit failed (details follow):
Error: Can't create directory
'/path/to/repositories_home/db/transactions/58-1.txn'
Error: Access Denied.
(well last line is in spanish and says:
    Error: Permiso denegado.
)

Ok. i get it is a permisions problem,
can some one point me to the right place to read what permisions should
i set.?

Thanks in advance.

-- 
ycdtosa.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 13 16:11:52 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.