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

Re: Subversion is convinced it's commiting, nothing happens, no errors

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-03-28 21:53:59 CEST

On Mar 28, 2007, at 09:38, d.mcclure@yahoo.com wrote:

> I am trying to take an existing document root for a webserver, e.g.
> /home/site.com/htdocs
> And make it editable via Subversion so user A can check out for
> example the file /home/site.com/htdocs/index.php, make changes, and
> commit them which should modify /home/site.com/htdocs/index.php on
> the server. This doesn't seem as if it needs to be terribly
> complex but I must be missing something obvious.
> Also, a programmer thought they were successfully doing this last
> night and made some revisions -- is there any way to tell exactly
> what they did from looking at the repository db or anything?

Ok. I understand what you're trying to do. Let's start at the
beginning and see how you're doing:

On Mar 28, 2007, at 09:08, d.mcclure@yahoo.com wrote:

> Hi....I've installed two separate versions of subversion with the
> same result. Check out works, it updates its versions, but nothing
> actually gets changed in my files so obviously I'm doing something
> wrong. I'm using svnadmin like so
> svnadmin create /var/svn/repositories

Note that this is confusing. You say you have created a repository
called "repositories". If you're only going to have one repository,
you should name it "repository" or "svn" or "mywebsites" or something
else. Naming a single repository "repositories" is weird.

If, on the other hand, the directory /var/svn/repositories is meant
to contain several repositories, each of which have been created with
svnadmin create, then /var/svn/repositories should not itself be a
repository. It should merely be a normal filesystem directory created
with mkdir.

> Then importing an existing directory with
> svn import /home/qxt.com/app /var/svn/repositories/project.com/
> project -m "initial import"

Ok, wonderful. You've imported the contents of that directory into
your repository (assuming, of course, you specify the repository URL
properly, as Mark Phippard noted earlier in the thread). The
directory you imported is, however, not connected to the repository
in any way. You've merely imported its contents into Subversion as a
place to start out.

> I can connect and check out everything just fine. Commit also
> thinks it is doing everything it should -- no errors, the version
> updates, but the files in that directory are unchanged. The rev
> and revprops directories are updated -- nothing else is, and I am
> not getting a single error. Permissions do not seem to be the issue.

You asked above if there is a way to see what has been done in the
repository. Sure. Use svn log to see the log messages, or svn log -v
to also see the paths modified. Use svn diff -c on a specific
changeset to see the actual line by line code changes.

But. What you said you want is that /home/qxt.com/app updates itself
when someone commits to the repository. That doesn't normally happen,
and to make it happen, you will need to make it into a working copy,
and write a post-commit hook.

To make it a working copy, you will have to move it out of the way
(rename it to /home/qxt.com/app-presvn for example) and then check
out a new working copy from the repository (cd /home/qxt.com && svn
checkout file:///var/svn/repositories/project.com/project app). Then,
write a post-commit hook which runs, approximately, svn up /home/

To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 28 21:54:42 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.