This link has been bookmarked by 108 people . It was first bookmarked on 19 Apr 2006, by Danny armstrong.
-
12 Oct 10
-
04 Jul 10
-
15 Jan 10
-
13 Jan 10
-
08 Dec 09
Joel Bennettsvn (Subversion Client) can use a proxy if you configure it in .subversion/servers
-
07 Dec 09
-
22 Sep 09
-
01 Sep 09
-
22 Aug 09
-
24 Jul 09
-
21 Jul 09
-
26 May 09
-
How do I manage several different projects under Subversion?
It depends upon the projects involved. If the projects are related, and are likely to share data, then it's best to create one repository with several subdirectories like this:
$ svnadmin create /repo/svn $ svn mkdir file:///repo/svn/projA $ svn mkdir file:///repo/svn/projB $ svn mkdir file:///repo/svn/projC
If the projects are completely unrelated, and not likely to share data between them, then it's probably best to create separate and unrelated repositories.
$ mkdir /repo/svn $ svnadmin create /repo/svn/projA $ svnadmin create /repo/svn/projB $ svnadmin create /repo/svn/projC
The difference between these two approaches is this (as explained by Ben Collins-Sussman <sussman@collab.net>):
- In the first case, code can easily be copied or moved around between projects, and the history is preserved. ('svn cp/mv' currently only works within a single repository.)
- Because revision numbers are repository-wide, a commit to any project in the first case causes a global revision bump. So it might seem a bit odd if somebody has 'projB' checked out, notices that 10 revisions have happened, but projB hasn't changed at all. Not a big deal, really. Just a little weird at first. This used to happen to svn everytime people committed to rapidsvn, when rapidsvn was in the same repository. :-)
- The second case might be easier to secure; it's easier to insulate projects from each other (in terms of users and permissions) using Apache's access control. In the 1st case, you'll need a fancy hook script in the repository that distinguishes projects ("is this user allowed to commit to this particular subdir?") Of course, we already have such a script, ready for you to use.
-
Use
svnadminto see which log files can be deleted. You may want a cron job to do this. -
Debris from a failed commit is littering your working copy.
You may have had a commit that went sour between the time the new revision was added in the server and the time your client performed its post-commit admin tasks (including refreshing your local text-base copy). This might happen for various reasons including (rarely) problems in the database back end or (more commonly) network dropouts at exactly the wrong time.
If this happens, it's possible that you have already committed the very changes you are trying now to commit. You can use 'svn log -rHEAD' to see if your supposed-failed commit actually succeeded. If it did, run 'svn revert' to revert your local changes, then run 'svn update' to get your own changes back from the server. (Note that only 'svn update' brings your local copies up-to-date; revert doesn't do that.)
Mixed revisions.
When Subversion commits, the client only bumps the revision numbers of the nodes the commit touches, not all nodes in the working copy. This means that in a single working copy, the files and subdirectories might be at different revisions, depending on when you last committed them. In certain operations (for example, directory property modifications), if the repository has a more recent version of the node, the commit will be rejected, to prevent data loss. See Mixed revisions have limitations in the Version Control with Subversion book for details.
You can fix the problem by running 'svn update' in the working copy.
You might be genuinely out of date — that is, you're trying to commit a change to a file that has been changed by someone else since you last updated your copy of that file. Again, 'svn update' is the way to fix this.
I'm trying to commit, but Subversion says my working copy is out of date?
Three kinds of situation that can cause this:
-
-
30 Mar 09
-
18 Feb 09
-
26 Jan 09
-
31 Dec 08
-
30 Dec 08
-
11 Nov 08
Neil SaundersBut this automatic upgrade behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe:
-
07 Oct 08
-
30 Sep 08
Charles SchoenfeldHere's the fix for subversion error "already under version control."
-
The directory you're trying to add already contains a .svn subdirectory — it is a working copy — but it's from a different repository location than the directory to which you're trying to add it. This probably happened because you used your operating system's "copy" command (instead of svn copy) to copy a subdirectory in this working copy, or to copy some other working copy into this one.
The quick and dirty solution is to delete all .svn directories contained in the directory you're trying to add; this will let the "add" command complete. If you're using Unix, this command will delete .svn directories under dir:
find dir -type d -name .svn -exec rm -rf {} \;
-
-
30 May 08
-
put a template of the file under version control
-
-
20 May 08
-
30 Apr 08
-
11 Apr 08
-
30 Mar 08
-
25 Mar 08
-
03 Mar 08
Adelbert GC:\Documents and Settings\adg\Application Data\Subversion
subversion configuration windows proxy cvs version control delicious original
-
11 Jan 08
-
02 Jan 08
-
28 Dec 07
-
26 Nov 07
-
04 Nov 07
-
20 Oct 07
-
15 Sep 07
-
31 Jul 07
-
26 Jul 07
-
22 Jul 07
-
20 Jul 07
-
17 Jul 07
-
05 Jun 07
-
25 Apr 07
-
05 Mar 07
-
28 Feb 07
-
13 Feb 07
-
01 Feb 07
Niall HaslamCollabNet, Facilitating Collaborative Software Development
-
21 Nov 06
-
15 Nov 06
-
03 Nov 06
-
19 Oct 06
-
29 Aug 06
-
24 Apr 06
-
19 Apr 06
-
My admins don't want me to have a HTTP server for Subversion. What can I do if I still want remote usage?
-
How do I convert an existing CVS repository into a Subversion repository?
-
How do I create a repository? How do I import data into it?
-
-
27 Mar 06
Glendon SolsberryHow do I convert my repository from using BDB to FSFS or from FSFS to BDB?
-
21 Mar 06
-
07 Dec 05
-
25 Oct 05
-
24 Oct 05
david_r_whitinghowto run ssh so that it only starts svnserve. Use this when you want to have people log in using ssh but don't want to worry about them getting access to other parts of the system.
-
29 Jun 05
-
16 Mar 05
-
22 Feb 05
-
Every time I try to access my repository, the process just hangs. Is my repository corrupt?
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.