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

Re: Can I have the same folder in twice?

From: Gabriel Rossetti <rossettigab_at_charter.net>
Date: 2005-11-02 14:40:14 CET

Yes, I understand better now. I have tried to do just that twice
actually, remove the repositories,
but I get strange msgs that made me think that there was a central db
somewhere.

here's what I did on the server side (as root)

mkdir /data/svnroot
mkdir /data/svnroot/repA
mkdir /data/svnroot/repB
mkdir /data/svnroot/private

svnadmin create /data/svnroot/repA
svnadmin create /data/svnroot/repB
svnadmin create /data/svnroot/private

(then changed rights, groups, users, etc)

on the client side (with gui client):

svn add dirA
svn commit -m "foo....." my_url/data/svnroot/repA

svn add my_dirs
svn commit -m "foo....." my_url/data/svnroot/private

but at this point, since private contains dirA, I got an error msg that
repA was already in the repository.
RepA is where my teammates and I accutally put our code and private is a
private backup of all my files,
so it also has repA in it. I then decided to start over with my setup,
so on the server, I did :

rm -fr /data/svnroot

mkdir /data/svnroot
mkdir /data/svnroot/repA
mkdir /data/svnroot/repB
mkdir /data/svnroot/private

svnadmin create /data/svnroot/repA
svnadmin create /data/svnroot/repB
svnadmin create /data/svnroot/private

(then changed rights, groups, users, etc)

on the client side (with gui client):

svn add dirA
svn commit -m "foo....." my_url/data/svnroot/repA

now I get the same error as before, but this time it sais that I can't
add dirA
because it exists already on /data/svnroot/private/.../dirA , but I
deleted it.... So.... I tried something else:

rm -fr /data/svnroot

mkdir /data/svnroot
mkdir /data/svnroot/public
mkdir /data/svnroot/private

svnadmin create /data/svnroot/public
svnadmin create /data/svnroot/private

(then changed rights, groups, users, etc)

on the client side (with gui client):

svn add directory_that_held_all_of_repA_directories
svn commit -m "foo....." my_url/data/svnroot/public/

and I get the same error as before, I can't add dirA (that is in
directory_that_held_all_of_repA_directories)
because it exists already on /data/svnroot/private/.../dirA

What I didn't get (and I still don't completely get now) is how can
those last two errors existe after I deleted
everything? I hope that this explanation of my (wrong)doing helps.

Thank you,
Gabriel Rossetti

Ryan Schmidt wrote:

> On Nov 1, 2005, at 18:49, Gabriel Rossetti wrote:
>
>> Thank you, yes, indeed, that must be it. My question now is, how can
>> I fix everything?
>> I have been playing around with svn and I've made a mess, how can I
>> get a fresh start?
>> Where is all this working copy stuff stored? It's still not very
>> clear for me. So there is a
>> sort of "global" db somewhere to keep track of all this? I've used
>> CVS some, but this
>> working copy thing must be a new construct.
>
>
> The working copy is not a new construct. It is where you do your
> work. After you do your work, you check your work into the
> repository. Both of these Subversion concepts are the same as they
> are in CVS.
>
> To start over, you can remove your repository or repositories (the
> directory or directories that got created when you executed "svnadmin
> create /path/to/repository") and any working copies you created (when
> you executed "svn checkout /path/to/workingcopy").
>
> If you have further problems, please show us the exact commands you
> executed.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 2 14:43:18 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.