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

Re: Question on Subversion Functionality

From: Mark Eramo <mark.eramo_at_trustvesta.com>
Date: 2007-08-28 17:40:29 CEST

Thank you for the information however I am still having an issue so I
must still be doing something wrong.

To recap....
What I have is, for example, the project *svn/project1* in Subversion
was checked out to */home/user/project1*

Now, a new folder was added in Subversion, *svn/project1/test

*I have already seen that if I try to checkout *svn/project1/test *to
*/home/user/project1/test, *it sees it as 2 separate checkouts because
in subcommander, the* test *folder shows up with a question mark so it
does not think it is under svn control.

I tried doing just an update but it does not clear the ? flag. I also
tried just doing an update of the working copy at the folder level but
it does not update the */home/user/project1 *folder to include *test.

*Could it be that when I did a checkout on */home/user/project1 *I did
not do a recursive checkout so now when I try to recursively add a
folder, it does not do it. Maybe I am using the update command the wrong

Any additional thoughts or comments would be much appreciated.


Hari Kodungallur wrote:
> cc-ing the group.. i did not hit 'reply-all' first time..
> On 8/24/07, *Mark Eramo* <mark.eramo@trustvesta.com
> <mailto:mark.eramo@trustvesta.com>> wrote:
> Hello,
> I am having a problem with Subversion and wondering if anyone
> has run
> into this before. ( I am rather new to Subversion so I am not sure if
> this is a bug or I am doing something wrong).
> We are using Subcommander 1.2.2 as our GUI Interface. Here is the
> issue.
> I check out the following folder/code from the Subversion Repository:
> */svn/repo/Database/project1/trunk*
> Now the code is on my local PC. When I setup a working copy folder, it
> shows up fine in subcommander.
> I put the code into in */home/user/Subversion/Database/project1 (mind
> you, the code in trunk resides i nthe project1 folder so there ie now
> trunk sub folder).*
> A developer came along and added the following folder into Subversion:
> */svn/repo/Database/project1/trunk/test
> *So now there is a test cases folder under trunk with new code.
> I now go into Subversion and checkout the *test cases only*, not
> all the
> code under trunk.
> They would get checked out to:
> */home/user/Subversion/Database/project1/test
> *If I then look at the working copy view in Subcommander, it is like
> Subversion does not know I have it checked out there. In Subcommander,
> the folder test shows up with a question mark. Subversion does not see
> them as being under source control but I just checked this out
> from the
> repository. The test folder has it's own .svn folder now and the
> code is
> in the test folder.
> If I start over and do a recursive checkout on the trunk folder to
> include all the files in test as well, it shows up fine in
> subcommander.
> It is almost like subversion is not updating the information in the*
> /home/user/Subversion/Database/project1/.svn* folder to tell it about
> the new folder/code the I just checked out underneath.
> I was wondering if anyone has run int this? Could this be a
> subversion
> or subcommander bug? Could I be doing something wrong, missing a step?
> Any help or thoughts would be much appreciated.
> I believe you just checked out the project1/trunk/test folder under
> project1/ folder. Those are two different checkouts and svn will treat
> them that way. The only reasons .svn folder gets updated are when you
> check-in something from your folder or when you update ('svn up') that
> folder.
> So, basically, if you update project1, instead of checking out a
> folder separately, you will be fine.
> rgds
> -Hari Kodungallur

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 28 17:38:30 2007

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.