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

Re: Cannot Checkout or Commit on New Repository

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-11-30 12:19:29 CET

On Nov 29, 2005, at 19:56, Hal Vaughan wrote:

> I have a system (I've mentioned it before) that I'm developing on
> Linux. It
> is all in the directory tree /thresh/threshNet/. In the directory
> threshNet
> are a number of subdirectories, some I have set to be ignored, the
> rest are
> part of the project. I set this up way before I ever realized I'd
> be needing
> version control (actually, before I even really knew what it was --
> I'd just
> back up the old version of a file before I started changing it), so
> the
> repository is in /thresh/threshNet/source -- and, yes, this
> directory is set
> to be ignored.
> So, while in the /thresh/threshNet/ directory, I ran this:
> svnadmin create source
> to create the repository. (Again, I need it in the same tree so
> it'll be
> included in backups and archives.) After this, I edited the global
> config
> file in /etc/subversion to ignore a number of directories,
> including source.
> Then, to enter my project, I did this:
> svn import ./ file:///thresh/threshNet/source -m "Initial import"

Really not such a great idea to have your repository inside your
working copy. Working copies are supposed to be just thatócopies
where you work. The fact that it's a copy (of what's in the
repository) is supposed to mean that you can freely delete the
working copy at any time, or create new ones for separate tasks. By
putting your repository inside your working copy you create a
dangerous confusion.

Instead, put your repository in a location of its own, say /thresh/
threshNet/repository (or "source" if you think that's clearer). Then
you can make any number of working copies that you like, for example /
thresh/threshNet/trunk or /thresh/threshNet/new-design or /thresh/
threshNet/widget-feature. You can make new working copies as needs
arise and remove the old ones as they're no longer needed.

> and it imported all my files. Once this was done, I wanted to test
> it out, so
> I edited one program, /thresh/threshNet/bin/t-test by changing it
> just a
> little, and got this:
> [hal@server:threshNet]$ svn commit bin/t-test
> svn: '/thresh/threshNet/bin' is not a working copy

As Theo said, importing a directory into Subversion does not
transform that directory into a working copy. Theoretically, after
you import a directory into a repository, you then delete the
directory and check out a new working copy from the repository. In
practice you probably want to just move the imported directory aside,
in case you discover the import went awry and you need to redo it.
And in your case in particular, since you put the repository into the
directory you were importing, you certainly cannot delete it or you'd
delete the repository with it.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 30 13:10:20 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.