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

Re: SVN not updating original file

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 22 Feb 2011 11:11:01 -0500

On Tue, Feb 22, 2011 at 10:58, Christopher D Haakinson
<cdhaakin_at_us.ibm.com> wrote:
> Hi SVN mailing list! I'm a first timer with SVN and am having problems.
> I followed this simple howto:
> http://www.tonyspencer.com/2007/03/02/setup-a-subversion-server-in-4-minutes/
> Now I have a repo setup that is accessible from remote clients. I can
> checkout the repo files, edit any of the files included and commit these
> changes back to SVN. To double-check I checked out the repo on a separate
> machine and was able to see my changes made from the first workstation.
> The problem I have is that the original file never changes, no matter how
> many changes I make.
> For example here's how my layout looks:
> /svn/scripts <-- This folder has my original script files I want SVN to
> track and update
> "svn import /svn/scripts file:///svn/scripts" is the command I run to create
> the repo
> /svn/scripts/check.sh <-- this is the file I change on my remote client
> So after I change this file, I commit the changes back to SVN and this
> appears to work, however the file /svn/scripts/check.sh remains the same,
> original un-edited file.
> What am I doing wrong? Seems simple enough it just doesn't work. Thanks!

What that tutorial fails to point out is that when you use svn import,
there is no connection made between the local directory and the
repository. All it does is push the contents of the local directory
into the repository.

This confusion can be mitigated by performing an "in-place import"
instead of a vanilla import. See

However, since you've already done the import, the safest route to go
now is to just check out a working copy from the repository.

Please also read the fine manual, http://svnbook.org/ . A "simple,
4-minute how-to" might *seem* OK for getting a repository set up, but
it really doesn't help you understand *how* Subversion works and how
to use it. In fact, that how-to completely glosses over *why* you're
running svnserve, and omits any discussion about administering it, and
I'm really puzzled as to why one would import via file:///, then fire
up svnserve, as opposed to just doing everything via svnserve (to
eliminate confusion).
Received on 2011-02-22 17:12:17 CET

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.