You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Res Pons <po...@hotmail.com> on 2005/12/02 05:17:52 UTC
New Server Installation, Access File, and Auto-Props
I'm hoping to get some feedback. Couple of months ago we installed
Subversion on a test server but due to time constraints and not having the
budget for newer equipment, we rolled the test server into production and it
became our de facto repository. The server is old, and there's limited disk
space on it. It was set up just to run basic repsitory transactions,
running Apache on a RedHat Linux box.
We received our new Linux Enterprise server which has a Raid system, tons of
disk space, RHLE3.5, latest linux kernel, latest Apache, etc. I downloaded
and installed all the Subversion.rpm files successfully without a hitch.
Both boxes disallow ssh except the administrator. Our users are all on
WinXP machines using either Svn DOS client or Tortoise.
I have already tarred up the old repo, untar, and installed it on the new
server and ran bunch of tests to make sure everything will work. And I
allowed Apache to own all the files as www:www. And managed to login and
check out the entir repo from the DOS client to my desktop. So far, so
good.
I have couple of problems which I'm not certain how to handle and need your
help and feedback please:
1. Both the old and the new servers have different DNS entries and IP
addresses naturally.
Option A: I'm getting ready to migrate repositories over the weekend by
asking users to stop all activity, so I can tar up the old repo, move it to
the new server, untar, test, and bring the new server online. I thought I
ask the users to check in all their working folders, clear out their
desktops, and just check out fresh new code or working folders from the new
repo on Monday. The downside of this option, incomplete code breaking the
builds but then again all activity would stop over the weekend.
Option B: Another option would be to turn off the old server, remove and
point its DNS entry as an alias to point to the new server to make it
seamless to the users? I really prefer not to take down the old server yet
or point its DNS to the new server.
Is there a way or compromise where users can just stop activity, leave their
current working folders intact, and on Monday they just point their
SVN-clients to the new repo and everything magically resolves itself and all
the repository urls in the hidden .svn subdirs magically get replaced with
the new server url? Any ideas to make this easier for both of us; user and
administratorwise?
2. I got my access file in conf/ working restricting access and rights. Is
it possible to block access per file rather per directory? There're couple
of files in a directory which contians many subdirectories that only few
authorized users should modify but all other users should have r/w access to
the subdirectories beneath.
3. I'm trying to turn on and enable the auto-props but I don't see
/etc/subversion being created. Do I manually create this directory? Who
should be the owner? Root or www? I copied "config, servers, and
readme.txt" from Windows side to this newly created subdir and tweaked the
config file and set enable-auto-prop=yes and created [auto-close] with file
pattern entries underneath it like so *.txt=keyword=Id. Created a new text
file, checked it in successfully but when I executed "svn proplist
filename..." I did not see the new properties. Could someone please
elaborate on this further. Does Subversion automatically and magically by
default look for /etc/subversion and executes the files? I'm lost and this
part is not working for me.
Thanks in Advance
_________________________________________________________________
Don�t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: New Server Installation, Access File, and Auto-Props
Posted by Res Pons <po...@hotmail.com>.
I figured #2 wasn't probably possible but worth asking anyway.
As for #3, I read the manual and wasn't sure whether I was doing this right
or not. I was wondering what the role of /etc/subversion/config was, I got
it to run by restarting Apache. And on my desktop created a new dummy file
to test whether the config rules applied or not, so when I ran svn propget
filename from my desktop, I didn't see any attached metadata. I kinda
guessed this was solely a user thing but wasn't sure and were confused.
Thanks for clearing it up.
We use Perl for all our pre/post commits; is there a perl equivalent file
for the python script you speak of? Otherwise, I'll see if I can dissect
the python script to write my own perl script.
Thank you.
----Original Message Follows----
From: Ryan Schmidt <su...@ryandesign.com>
To: Res Pons <po...@hotmail.com>
CC: users@subversion.tigris.org
Subject: Re: New Server Installation, Access File, and Auto-Props
Date: Sun, 4 Dec 2005 23:34:42 -0600
MIME-Version: 1.0 (Apple Message framework v746.2)
Received: from server20.hostpoint.ch ([217.26.52.30]) by
bay0-mc2-f17.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 4
Dec 2005 21:34:35 -0800
Received: from [67.9.127.101] (helo=[192.168.0.4])by server20.hostpoint.ch
with esmtpa (Exim 4.54 (FreeBSD))id 1Ej8zh-000Hlb-3A; Mon, 05 Dec 2005
06:34:33 +0100
X-Message-Info: JGTYoYF78jHivLSQClyjWMKcpHOV0zxjOixuzFWuDos=
References: <BA...@phx.gbl>
X-Mailer: Apple Mail (2.746.2)
X-AntiAbuse: This header was added to track abuse, please include it with
any abuse report
X-AntiAbuse: Primary Hostname - server20.hostpoint.ch
X-AntiAbuse: Original Domain - hotmail.com
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6]
X-AntiAbuse: Sender Address Domain - ryandesign.com
Return-Path: subversion-2005@ryandesign.com
X-OriginalArrivalTime: 05 Dec 2005 05:34:36.0195 (UTC)
FILETIME=[941A3F30:01C5F95D]
On Dec 1, 2005, at 23:17, Res Pons wrote:
>2. I got my access file in conf/ working restricting access and rights.
>Is it possible to block access per file rather per directory? There're
>couple of files in a directory which contians many subdirectories that
>only few authorized users should modify but all other users should have
>r/w access to the subdirectories beneath.
I don't know whether that is possible, sorry.
>3. I'm trying to turn on and enable the auto-props but I don't see
>/etc/subversion being created. Do I manually create this directory? Who
>should be the owner? Root or www? I copied "config, servers, and
>readme.txt" from Windows side to this newly created subdir and tweaked the
>config file and set enable-auto- prop=yes and created [auto-close] with
>file pattern entries underneath it like so *.txt=keyword=Id. Created a
>new text file, checked it in successfully but when I executed "svn
>proplist filename..." I did not see the new properties. Could someone
>please elaborate on this further. Does Subversion automatically and
>magically by default look for /etc/subversion and executes the files? I'm
>lost and this part is not working for me.
auto-props are a client-side thing, not a server-side thing. The clients
need to set up their config files with the auto-props they want. Any config
file in /etc/subversion is merely used as the default for clients running
on that same computer who don't have a custom config file in their own
Subversion directories. So unless your users are logging in to the
Subversion repository server with SSH (which you said they're not) then an
/etc/subversion directory on the repository server won't do anything for
anyone.
What you should do is create a standard config file and distribute it to
your users. Then you should install a pre-commit hook on the server which
verifies committed files against that master config file, and rejects
commits that do not comply. I recently posted a link to a Python script
that someone had written for this purpose.
_________________________________________________________________
Don�t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: New Server Installation, Access File, and Auto-Props
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Dec 5, 2005, at 00:19, Gavin Lambert wrote:
> Quoth Ryan Schmidt <ma...@ryandesign.com>:
>> auto-props are a client-side thing, not a server-side thing. The
> [...]
>> What you should do is create a standard config file and distribute it
>> to your users.
>
> Though on that note: what happens when a single user wants to
> connect to
> multiple repositories (from multiple projects, with different owners)
> that have conflicting auto-props requirements?
Then the client is probably inconvenienced.
> It really does seem like something that ought to be set on the server
> rather than the client, though of course the client should be able to
> "override" the automatic property when they add a file. Though I
> guess
> it'd be a little tricky finding a place to put it (on the client),
> since
> the client would probably need to get pushed a copy of it.
I'm not saying it wouldn't be nice to have a server-controlled auto-
props setting; I'm just describing the way it is now.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: New Server Installation, Access File, and Auto-Props
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Dec 5, 2005, at 11:44, Res Pons wrote:
> On Dec 4, 2005, at 23:34, Ryan Schmidt wrote:
>
>> auto-props are a client-side thing, not a server-side thing. The
>> clients need to set up their config files with the auto-props they
>> want. Any config file in /etc/subversion is merely used as the
>> default for clients running on that same computer who don't have a
>> custom config file in their own Subversion directories. So unless
>> your users are logging in to the Subversion repository server with
>> SSH (which you said they're not) then an /etc/subversion directory
>> on the repository server won't do anything for anyone.
>>
>> What you should do is create a standard config file and distribute
>> it to your users. Then you should install a pre-commit hook on the
>> server which verifies committed files against that master config
>> file, and rejects commits that do not comply. I recently posted a
>> link to a Python script that someone had written for this purpose.
>
> We only use the one server with 1 repo and multiple projects under
> it; no multiple repos. So then, could I ask all users to delete
> their winxp local config files and just let the one in /etc/
> subversion to be the default, would that work?
Again, if all these users are logging in to the Subversion server via
SSH and using the svn command line client while logged in to that
server, then the config file in the server's /etc/subversion
directory will have effect. If your users are using clients on their
local Windows machines, then it will not.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: New Server Installation, Access File, and Auto-Props
Posted by Res Pons <po...@hotmail.com>.
So here's a 2nd question then:
We only use the one server with 1 repo and multiple projects under it; no
multiple repos. So then, could I ask all users to delete their winxp local
config files and just let the one in /etc/subversion to be the default,
would that work?
----Original Message Follows----
From: "Gavin Lambert" <ga...@compacsort.com>
To: "'Ryan Schmidt'" <su...@ryandesign.com>
CC: <us...@subversion.tigris.org>
Subject: RE: New Server Installation, Access File, and Auto-Props
Date: Mon, 5 Dec 2005 19:19:54 +1300
MIME-Version: 1.0
Received: from tigris.org ([64.125.133.100]) by bay0-mc2-f9.bay0.hotmail.com
with Microsoft SMTPSVC(6.0.3790.211); Sun, 4 Dec 2005 22:22:19 -0800
Received: (qmail 10289 invoked by uid 5000); 5 Dec 2005 06:22:00 -0000
Received: (qmail 10262 invoked from network); 5 Dec 2005 06:22:00 -0000
X-Message-Info: JGTYoYF78jGYXz4fNA4FfkjzDbeMVHt0v/VNEW8lDnE=
Mailing-List: contact users-help@subversion.tigris.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
list-help: <ma...@subversion.tigris.org>
list-unsubscribe: <ma...@subversion.tigris.org>
list-post: <ma...@subversion.tigris.org>
Delivered-To: mailing list users@subversion.tigris.org
Organization: Compac Sorting Equipment
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Return-Path: users-return-42031-pons32=hotmail.com@subversion.tigris.org
X-OriginalArrivalTime: 05 Dec 2005 06:22:20.0107 (UTC)
FILETIME=[3F2089B0:01C5F964]
Quoth Ryan Schmidt <ma...@ryandesign.com>:
> auto-props are a client-side thing, not a server-side thing. The
[...]
> What you should do is create a standard config file and distribute it
> to your users.
Though on that note: what happens when a single user wants to connect to
multiple repositories (from multiple projects, with different owners)
that have conflicting auto-props requirements?
It really does seem like something that ought to be set on the server
rather than the client, though of course the client should be able to
"override" the automatic property when they add a file. Though I guess
it'd be a little tricky finding a place to put it (on the client), since
the client would probably need to get pushed a copy of it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: New Server Installation, Access File, and Auto-Props
Posted by Gavin Lambert <ga...@compacsort.com>.
Quoth Ryan Schmidt <ma...@ryandesign.com>:
> auto-props are a client-side thing, not a server-side thing. The
[...]
> What you should do is create a standard config file and distribute it
> to your users.
Though on that note: what happens when a single user wants to connect to
multiple repositories (from multiple projects, with different owners)
that have conflicting auto-props requirements?
It really does seem like something that ought to be set on the server
rather than the client, though of course the client should be able to
"override" the automatic property when they add a file. Though I guess
it'd be a little tricky finding a place to put it (on the client), since
the client would probably need to get pushed a copy of it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: New Server Installation, Access File, and Auto-Props
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Dec 1, 2005, at 23:17, Res Pons wrote:
> 2. I got my access file in conf/ working restricting access and
> rights. Is it possible to block access per file rather per
> directory? There're couple of files in a directory which contians
> many subdirectories that only few authorized users should modify
> but all other users should have r/w access to the subdirectories
> beneath.
I don't know whether that is possible, sorry.
> 3. I'm trying to turn on and enable the auto-props but I don't
> see /etc/subversion being created. Do I manually create this
> directory? Who should be the owner? Root or www? I copied
> "config, servers, and readme.txt" from Windows side to this newly
> created subdir and tweaked the config file and set enable-auto-
> prop=yes and created [auto-close] with file pattern entries
> underneath it like so *.txt=keyword=Id. Created a new text file,
> checked it in successfully but when I executed "svn proplist
> filename..." I did not see the new properties. Could someone
> please elaborate on this further. Does Subversion automatically
> and magically by default look for /etc/subversion and executes the
> files? I'm lost and this part is not working for me.
auto-props are a client-side thing, not a server-side thing. The
clients need to set up their config files with the auto-props they
want. Any config file in /etc/subversion is merely used as the
default for clients running on that same computer who don't have a
custom config file in their own Subversion directories. So unless
your users are logging in to the Subversion repository server with
SSH (which you said they're not) then an /etc/subversion directory on
the repository server won't do anything for anyone.
What you should do is create a standard config file and distribute it
to your users. Then you should install a pre-commit hook on the
server which verifies committed files against that master config
file, and rejects commits that do not comply. I recently posted a
link to a Python script that someone had written for this purpose.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: New Server Installation, Access File, and Auto-Props
Posted by Res Pons <po...@hotmail.com>.
Ok thanks. I'm going to test this now and convert my existing local working
folder to switch to the new server. Which has the same exact file/repo
structure. A coworker just informed me that svn Reloacate is buggy when he
tested it for me. I'm going to give it a try to find out for myself.
Thanks.
----Original Message Follows----
From: "Gavin Lambert" <ga...@compacsort.com>
To: "'Res Pons'" <po...@hotmail.com>
CC: <us...@subversion.tigris.org>
Subject: RE: New Server Installation, Access File, and Auto-Props
Date: Fri, 2 Dec 2005 19:11:17 +1300
MIME-Version: 1.0
Received: from grunt1.ihug.co.nz ([203.109.254.41]) by mc5-f16.hotmail.com
with Microsoft SMTPSVC(6.0.3790.211); Thu, 1 Dec 2005 22:13:23 -0800
Received: from 203-118-130-100.ihug.net (gavinlpc) [203.118.130.100] by
grunt1.ihug.co.nz with esmtp (Exim 3.35 #1 (Debian))id 1Ei4AZ-00053r-00;
Fri, 02 Dec 2005 19:13:19 +1300
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
Organization: Compac Sorting Equipment
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Return-Path: gavinl@compacsort.com
X-OriginalArrivalTime: 02 Dec 2005 06:13:24.0675 (UTC)
FILETIME=[80BED930:01C5F707]
Quoth Res Pons <ma...@hotmail.com>:
> Is there a way or compromise where users can just stop
> activity, leave their current working folders intact, and
> on Monday they just point their SVN-clients to the new repo
> and everything magically resolves itself and all the
> repository urls in the hidden .svn subdirs magically get
> replaced with the new server url? Any ideas to make this
> easier for both of us; user and administratorwise?
Yep -- that's what svn switch --relocate is for. (Also accessible in
Tortoise via the Relocate command.)
You can't use this to switch a working copy to any other repository (or
even an older version of the same repository), but it will work fine if
you're switching to "the same repository, but in a different place".
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar � get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: New Server Installation, Access File, and Auto-Props
Posted by Gavin Lambert <ga...@compacsort.com>.
Quoth Res Pons <ma...@hotmail.com>:
> Is there a way or compromise where users can just stop
> activity, leave their current working folders intact, and
> on Monday they just point their SVN-clients to the new repo
> and everything magically resolves itself and all the
> repository urls in the hidden .svn subdirs magically get
> replaced with the new server url? Any ideas to make this
> easier for both of us; user and administratorwise?
Yep -- that's what svn switch --relocate is for. (Also accessible in
Tortoise via the Relocate command.)
You can't use this to switch a working copy to any other repository (or
even an older version of the same repository), but it will work fine if
you're switching to "the same repository, but in a different place".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org