On Nov 17, 2011, at 07:39, Sergey Skvortsov wrote:
> Do you really believe that normal admin is not smart enough to read docs?
Based on years of answering questions on this list: yes, sometimes. :)
Hi,
We're currently looking at moving our SVN repositories off of a Windows
2003 physical machine to a 2008 VM (in VMWare vCentre). This is to allow
easier replication to our DR site through the veeam replication software.
Has anyone done this before, and if so, are there any gotchas that we need
On Thu, Nov 17, 2011 at 8:02 PM, Daniel Shahaf wrote:
> Johan Corveleyn wrote on Thu, Nov 17, 2011 at 13:55:51 +0100:
>> On Thu, Nov 17, 2011 at 1:02 PM, Philip Martin
>> wrote:
>> > Attila Nagy writes:
>> >
>> >> On 11/16/11 18:40, Philip Martin wrote:
>> >>> Attila Nagy writes:
>> >>>
>>
Johan Corveleyn wrote on Thu, Nov 17, 2011 at 13:55:51 +0100:
> On Thu, Nov 17, 2011 at 1:02 PM, Philip Martin
> wrote:
> > Attila Nagy writes:
> >
> >> On 11/16/11 18:40, Philip Martin wrote:
> >>> Attila Nagy writes:
> >>>
> I use pysvn for this and basically the code looks like this (in
Philip Martin writes:
> I don't understand the "provided ..." bit. It seems to be flat out
> wrong.
Don't take that the wrong way: "It" refers to the code.
--
Philip
Stefan Sperling writes:
> I agree that special-casing the root_dir seems unnecessary even in the
> mirroring case, provided that nested Locations are supposed to work.
I don't understand the "provided ..." bit. It seems to be flat out
wrong. If I fix the line then nested mirroring works when u
On Thu, Nov 17, 2011 at 02:37:36PM +, Philip Martin wrote:
> The order of parent and child in Subversion's INHERIT_VALUE macro only
> has an effect when nesting one Subversion location in another. When not
> nested the parent root_dir is NULL and the child value will be used
> whatever the ord
Stefan Sperling writes:
> Yes, of course it works with SVNParentPath. But I suspect that is
> a result of implementation rather than concious design.
Perhaps, but the line that stops it working looks like an outright bug.
newconf->root_dir = INHERIT_VALUE(child, parent, root_dir);
The orde
On Thu, Nov 17, 2011 at 05:39:37PM +0400, Sergey Skvortsov wrote:
> For example, our practice of layout organizing (simplified example):
>
> /svn
> /devops
> /infra
> /src
> /personal
> /user1
> /user2
> /project
> /prj1
> /prj2
>
Hi,
Von: Vyacheslav Zholudev [mailto:vyacheslav.zholu...@gmail.com]
>> That said, why are you so sure you must use exactly 1.4? Subversion
>> 1.7 can create, read, and write 1.4 repositories. And there have been
>> significant performance improvements in the past four years...
> I just have
On 17.11.2011 16:44, Stefan Sperling wrote:
On Thu, Nov 17, 2011 at 11:50:20AM +, Philip Martin wrote:
Stefan Sperling writes:
How do we avoid ambiguity when handling requests to nested Locations?
How can a client access a folder /bar inside a repository at Location /svn
if another reposi
On Thu, Nov 17, 2011 at 1:02 PM, Philip Martin
wrote:
> Attila Nagy writes:
>
>> On 11/16/11 18:40, Philip Martin wrote:
>>> Attila Nagy writes:
>>>
I use pysvn for this and basically the code looks like this (in python):
def update_perms():
for path in propchg:
On Thu, Nov 17, 2011 at 11:50:20AM +, Philip Martin wrote:
> Stefan Sperling writes:
>
> > How do we avoid ambiguity when handling requests to nested Locations?
> > How can a client access a folder /bar inside a repository at Location /svn
> > if another repository exists at a nested Location
On Wed, 16 Nov 2011 17:40:55 +, Philip Martin wrote:
...
> It might be faster to run a recursive propget,
It might also be erroneous. I noticed in an 1.5/1.6 setup that
a recursive propget over a big subtree simply fails to yield *all*
relevant properties. That is, a
svn pg -R svn:externals
Attila Nagy writes:
> On 11/16/11 18:40, Philip Martin wrote:
>> Attila Nagy writes:
>>
>>> I use pysvn for this and basically the code looks like this (in python):
>>> def update_perms():
>>> for path in propchg:
>>> proplist = svn.propget('file:permissions', path)
>>> if
Stefan Sperling writes:
> How do we avoid ambiguity when handling requests to nested Locations?
> How can a client access a folder /bar inside a repository at Location /svn
> if another repository exists at a nested Location /svn/bar?
Yes, I was surprised too! If we assume that /svn and /svn/fo
On 11/16/11 18:40, Philip Martin wrote:
Attila Nagy writes:
I use pysvn for this and basically the code looks like this (in python):
def update_perms():
for path in propchg:
proplist = svn.propget('file:permissions', path)
if not os.path.islink(path) and proplist.has_key
On Thu, Nov 17, 2011 at 11:01:39AM +, Philip Martin wrote:
> [Adding dev]
>
> Philip Martin writes:
>
> > Sergey Skvortsov writes:
> >
> >> Also, in 1.7 reading repos is working fine:
> >>
> >> "OPTIONS /svn/foo/bar HTTP/1.1" 200
> >> "REPORT /svn/foo/bar/!svn/me HTTP/1.1" 200
> >>
> >> bu
Philip Martin writes:
> [Adding dev]
Gah! Got the address wrong. I'll start a thread on dev.
--
Philip
[Adding dev]
Philip Martin writes:
> Sergey Skvortsov writes:
>
>> Also, in 1.7 reading repos is working fine:
>>
>> "OPTIONS /svn/foo/bar HTTP/1.1" 200
>> "REPORT /svn/foo/bar/!svn/me HTTP/1.1" 200
>>
>> but only POST fails:
>> "POST /svn/foo/bar/!svn/me HTTP/1.1" 500
>>
>> So the problem is
Sergey Skvortsov writes:
> Also, in 1.7 reading repos is working fine:
>
> "OPTIONS /svn/foo/bar HTTP/1.1" 200
> "REPORT /svn/foo/bar/!svn/me HTTP/1.1" 200
>
> but only POST fails:
> "POST /svn/foo/bar/!svn/me HTTP/1.1" 500
>
> So the problem is not in Apache or configuration but in mod_dav_svn
On 17.11.2011 11:35, Cooke, Mark wrote:
-Original Message-
From: Sergey Skvortsov [mailto:s...@protey.ru]
Sent: 17 November 2011 07:09
Subject: Re: "svn commit" does not work with SVNParentPath in
location and 1.7-client (HTTPv2)
I disagree. This cite is irrelevant to my issue.
It
22 matches
Mail list logo
