You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Frank Striegel <f....@easysoft.info> on 2005/06/27 08:18:22 UTC
Any known restrictions by using svn over file-protocol (file:///) ?
Hello all,
are there any known restrictions by using svn over file-protocol
(file:///) on a network-share with more than
one decelopers? Should I switch to svnserve (svn:///) or apache?
(svn 1.2, FSFS Repo)
Frank
Re: Any known restrictions by using svn over file-protocol (file:///) ?
Posted by David Weintraub <qa...@gmail.com>.
On 6/27/05, Frank Striegel <f....@easysoft.info> wrote:
> are there any known restrictions by using svn over file-protocol (file:///)
> on a network-share with more than one decelopers? Should I switch to svnserve (svn:///) or apache?
Not really a "restriction" as more of a question of security.
In order for the file:// protocol to work, that user must have direct
write access to the repository. That means any user could simply
delete all repository files, make changes in your repository, or play
around with any hooks that you've programmed.
The other protocols, svnserve and apache, isolate your repository from
direct user access. Any changes made to the source archive are logged
and, more importantly, completely reversible.
"file://" is good if you're the only user or are running through some
Subversion scenario.. However, it is so easy to setup the svnserver
protocol, it seems silly not to do it.
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Any known restrictions by using svn over file-protocol (file:///) ?
Posted by John Szakmeister <jo...@szakmeister.net>.
On Monday 27 June 2005 04:18, Frank Striegel wrote:
> Hello all,
>
>
>
> are there any known restrictions by using svn over file-protocol
> (file:///) on a network-share with more than
>
> one decelopers? Should I switch to svnserve (svn:///) or apache?
>
>
>
> (svn 1.2, FSFS Repo)
http://subversion.tigris.org/faq.html#nfs
As long as the network filesystem you're using supports the minimum
locking requirements mentioned in the FAQ, you'll be safe to share it.
That said, svnserve is a great alternative.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:keywords parsing bug
Posted by Kris Deugau <kd...@vianet.ca>.
Miha Vitorovic wrote:
> I'm not too comfortable with the issue tracker, so maybe this is
> known already. there seems to be a bug when parsing svn:keywords
> value. Specifically there seems to be a problem when a keyword is
> not delimited by spaces, i.e. the first or the last keyword may not
> work.
>
> For example:
>
> svn:keywords="Date Revision Id" -- Only $revision$ gets replaced
> like this.
>
> svn:keywords=" Date Revision Id " -- All three keywords work.
I've seen this; my guess is that the quotes end up parsed as part of
the keyword. :/ Removing the quotes works fine.
-kgd
--
Get your mouse off of there! You don't know where that email has been!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:keywords parsing bug
Posted by Miha Vitorovic <mv...@nil.si>.
"Max Bowsher" <ma...@ukf.net> wrote on 28.06.2005 05:18:04:
> >> On Jun 27, 2005, at 12:54 PM, Miha Vitorovic wrote:
> >>
> >>> For example:
> >>>
> >>> svn:keywords="Date Revision Id" -- Only $revision$ gets
> >>> replaced like
> >>> this.
> >>>
> >>> svn:keywords=" Date Revision Id " -- All three keywords work.
> >>>
> >>> I noticed this on Windows XP, command line client.
> >>
> > Kris Deugau <kd...@vianet.ca> wrote on 27.06.2005 20:35:30:
> >>
> >> I've seen this; my guess is that the quotes end up parsed as part of
> >> the keyword. :/ Removing the quotes works fine.
> >
>
> Read that 'confirmation' again. Kris' guess is correct.
> Quotes are not part of the format of the Subversion configuration files,
and
> it is an error to use them. Not a bug.
>
While I agree that it is an input error, I am also inclined to argue that
multi-value command arguments are often delimited by quotes and that
obviously many/some users include them without thinking. So the client
could either handle them correctly if they are present, or the help screen
could make it absolutely clear, that the PROPVAL treats quotes as a value,
not as a delimiter - unlike the --message parameter, for example.
That's just my $0.02, but I'll be happy to omit the quotes from now on.
Cheers,
---
Miha Vitorovic
Inženir v tehničnem področju
Customer Support Engineer
NIL Data Communications, Tivolska cesta 48, 1000 Ljubljana, Slovenia
Phone +386 1 4746 500 Fax +386 1 4746 501 http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:keywords parsing bug
Posted by Max Bowsher <ma...@ukf.net>.
Miha Vitorovic wrote:
> Kris Deugau <kd...@vianet.ca> wrote on 27.06.2005 20:35:30:
>>
>> I've seen this; my guess is that the quotes end up parsed as part of
>> the keyword. :/ Removing the quotes works fine.
>
> Ben Collins-Sussman <su...@collab.net> wrote on 27.06.2005 22:00:24:
>>
>> On Jun 27, 2005, at 12:54 PM, Miha Vitorovic wrote:
>>
>>> For example:
>>>
>>> svn:keywords="Date Revision Id" -- Only $revision$ gets
>>> replaced like
>>> this.
>>>
>>> svn:keywords=" Date Revision Id " -- All three keywords work.
>>>
>>> I noticed this on Windows XP, command line client.
>>
>>
>> Can you show us a script (or transcript) which demonstrates this?
>
> If, after someone else confirmed this, I still have to, you'll have to
> wait until tomorrow, when I get back to work.
Read that 'confirmation' again. Kris' guess is correct.
Quotes are not part of the format of the Subversion configuration files, and
it is an error to use them. Not a bug.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:keywords parsing bug
Posted by Miha Vitorovic <mv...@nil.si>.
Kris Deugau <kd...@vianet.ca> wrote on 27.06.2005 20:35:30:
>
> I've seen this; my guess is that the quotes end up parsed as part of
> the keyword. :/ Removing the quotes works fine.
Ben Collins-Sussman <su...@collab.net> wrote on 27.06.2005 22:00:24:
>
> On Jun 27, 2005, at 12:54 PM, Miha Vitorovic wrote:
>
> > For example:
> >
> > svn:keywords="Date Revision Id" -- Only $revision$ gets
> > replaced like
> > this.
> >
> > svn:keywords=" Date Revision Id " -- All three keywords work.
> >
> > I noticed this on Windows XP, command line client.
>
>
> Can you show us a script (or transcript) which demonstrates this?
If, after someone else confirmed this, I still have to, you'll have to
wait until tomorrow, when I get back to work.
Cheers,
---
Miha Vitorovic
Inženir v tehničnem področju
Customer Support Engineer
NIL Data Communications, Tivolska cesta 48, 1000 Ljubljana, Slovenia
Phone +386 1 4746 500 Fax +386 1 4746 501 http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:keywords parsing bug
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jun 27, 2005, at 12:54 PM, Miha Vitorovic wrote:
> Hi all/developers,
>
> I'm not too comfortable with the issue tracker, so maybe this is known
> already there seems to be a bug when parsing svn:keywords value.
> Specifically there seems to be a problem when a keyword is not
> delimited
> by spaces, i.e. the first or the last keyword may not work.
>
> For example:
>
> svn:keywords="Date Revision Id" -- Only $revision$ gets
> replaced like
> this.
>
> svn:keywords=" Date Revision Id " -- All three keywords work.
>
> I noticed this on Windows XP, command line client.
Can you show us a script (or transcript) which demonstrates this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
svn:keywords parsing bug
Posted by Miha Vitorovic <mv...@nil.si>.
Hi all/developers,
I'm not too comfortable with the issue tracker, so maybe this is known
already there seems to be a bug when parsing svn:keywords value.
Specifically there seems to be a problem when a keyword is not delimited
by spaces, i.e. the first or the last keyword may not work.
For example:
svn:keywords="Date Revision Id" -- Only $revision$ gets replaced like
this.
svn:keywords=" Date Revision Id " -- All three keywords work.
I noticed this on Windows XP, command line client.
Cheers,
---
Miha Vitorovic
Inženir v tehničnem področju
Customer Support Engineer
NIL Data Communications, Tivolska cesta 48, 1000 Ljubljana, Slovenia
Phone +386 1 4746 500 Fax +386 1 4746 501 http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org