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

Re: so I need to install Subversion first?

From: Thomas Crausaz <crausaz_at_epac.ch>
Date: Thu, 15 Nov 2012 14:51:20 +0100

Hi all,
I just installed Tortoise and I am now testing it and have some trouble with
the locks.

Again I am not at all am IT guy so bear with me please.
We are artists and working with binary files only.

I created a local repository (not on a server yet) just for testing.

It all work fine with basic commit. But I have problem with locks.

First : When I edit the properties of a file to add "svn:needs-lock" on it,
I do not see the overlay grey tick icon on that file (read only). Why is
that? (it does the lock all-right, but I would like to visibly see on the
icon that it is read only)

Second : I tried to apply the "svn:needs-lock" property to every files in a
specific folder. When I go the properties of the folder and try to apply the
"svn:needs-lock", nothing happened. How can I apply that property to all the
files and subfolders in a specific folder?

Third : I want to edit the config file so that all new files commited into
that repository is read only.
From what I understood, I need :
- to uncomment the line enable-auto-props = yes
- then what should I edit/add into the config file?

Thank you very much for your help,


-----Message d'origine-----
From: Simon Large
Sent: Tuesday, November 06, 2012 11:46 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: so I need to install Subversion first?

On 6 November 2012 21:55, Bob Archer <Bob.Archer_at_amsi.com> wrote:
> > ok thanks to clarify.
> >
> > I need it mostly for binaries (images and meshes) so I guess it is not
> > ideal then.
> >
> > too bad, I though I found the ideal free software I was after...
> It will work. It just works much better for text based code. Just
> remember, locks aren't really enforced. But, it is possible to lock a
> file.

I think this needs to be clarified. Subversion works equally well for
text and binary files. Locking works. The bit that doesn't work with
binaries is trying to merge changes when two users change a file
simultaneously. And that is the whole point of locking, to prevent two
users changing the same file.

Because locking is not the default in Subversion there are a few
things your need to consider when using it. You need to set the
svn:needs-lock property on every binary file. It is possible to set up
client-side rules to apply this property automatically, but to be
really safe you may want to set up a server-side hook to ensure that
no file is ever added to the repository without that property.

What that property does is make every file which has not been locked
read-only. When you take a lock the file becomes writeable. This is
what gives you your local protection against modifying a file without
taking a lock. However it does rely on your software telling you
straight away that the file is read-only and not letting you modify
it. If your image editor only tells you that when you come to save
changes after forgetting to take out a lock, then it could get

When Bob says that locks aren't enforced what (I think) he means is
that there are commands to break a lock (i.e. remove a lock which
someone else has taken out) and steal a lock (remove someone else's
lock and lock the file yourself). This can allow anti-social behaviour
where someone decides their changes are more important than yours and
steals your lock so they can commit changes and yours get discarded.
But that is more of a community behaviour issue rather than a problem
with locking per se. The reason for these commands is that if someone
takes a lock and then goes on holiday without releasing it, then
everyone else is stuck until they get back. If you are really paranoid
then it is possible to set up server hooks to prevent locks being
broken or stolen, but that is not generally recommended.

Also, if you are working as a team then using a proper server is a
must. Do NOT be tempted to use a shared NAS drive or similar and just
pretend it is a local repository. Fortunately there are several
friendly Windows installers for Subversion which will take you through
the installation and setup using a wizard front end. Three of them are
mentioned at the bottom of this manual page:


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
> >
> > cheers
> >
> > Thomas
> >
> > -----Original Message-----
> > From: Bob Archer
> > Sent: Tuesday, November 06, 2012 6:45 PM
> > To: users_at_tortoisesvn.tigris.org
> > Subject: RE: so I need to install Subversion first?
> >
> > > Subject: Re: so I need to install Subversion first?
> > >
> > > yes sorry, I meant revision control system.
> > >
> > > So you do need Subversion  installed first on the server?
> >
> > The answer is, it depends. If you are going to be the only one accessing 
> > the
> > repository, then no. You can just create a repository on your location 
> > machine
> > and access it from there. You can also run svnserver on a work station 
> > to allow
> > remote PCs access to it.
> >
> > >
> > > also, I had a look in the features description but could not find this 
> > > :
> > > can you
> > > lock a file so only one person at a time can work on it?
> >
> > You can, but that is not the recommended use case.
> >
> >
> > > or maybe it is not the right software for what i am after. I am
> > > looking at something that allow a team to commit various types of
> > > files on a server, and to be able to lock the file they are working on
> > > and then commit them for the other to use.
> >
> > Once again, SVN uses an optimistic locking scenario rather than 
> > pessimistic.
> > This works very well for text based files. Not so much for binaries...
> > although svn can be used to version binary files, the merging doesn't 
> > really
> > work out.
> >
> > BOb
> >
> >
> > >
> > > thanks
> > >
> > > Thomas
> > >
> > > From: Gabri Nurtinaz Shally
> > > Sent: Tuesday, November 06, 2012 11:11 AM
> > > To: users_at_tortoisesvn.tigris.org
> > > Subject: Re: so I need to install Subversion first?
> > >
> > > On Nov 6, 2012 4:57 PM, "Thomas Crausaz" <crausaz_at_epac.ch> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > sorry for the noob question, but I am not an IT guy at all, still I
> > > > need to install
> > > an asset management program for my class.
> > > >
> > > > So I need to install Subversion first on the server, right? And then
> > > TortoiseSVN?
> > > >
> > > what does this assets management do?
> > > SVN is a client for collaboration file versioning. so i don't think it
> > > has something to do with assets management.
> > > regards,
> > > gabri
To unsubscribe from this discussion, e-mail: 
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-15 14:51:29 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.