Re: tortoise 1.7 - error on repository manipulation

Le 28/10/2011 10:51, Daniel Shahaf a écrit :
> Erwane, can you provide a minimal server configuration that reproduces
> the bug? The svn devs used 1.7 clients against a 1.6.17 svn.apache.org
> for a long time without seeing any such errors, so I suspect the issue
> is due to your configuration triggering some edge case.

I'm doing that on a virtualbox, taking a time :)

Le 28/10/2011 11:00, Philip Martin a écrit :
> That's a v2 protocol problem. The v2 protocol is only used when both
> client and server are 1.7. If you add "SVNAdvertiseV2Protocol off" to
> the 1.7 Apache config file then clients should use the v1 protocol.
>
> Do the error messages really have two '*' characters in the URL or is
> that an email artifact?
>
> Is your 1.7 server a write-through proxy to a 1.6 master? That won't
> work unless you disable the v2 protocol because the 1.6 master will not
> understand the v2 protocol.
>
> Is there some proxy or filter between the client and server that is
> corrupting the ULR?

There is no * ine the message, it's "bold" format. real message is :

/svn/site/!svn/me path not found

On my new server, i'm using :
- apache-2.2.21
- apache-ant-1.8.2_1
- apr-ipv6-devrandom-gdbm-db48-mysql55-1.4.5.1.3.12_1
- p5-subversion-1.7.1
- subversion-1.7.1

So, the subversion server is 1.7.1 and client is 1.7.1 too :)
i've tried to create an new fresh repository on my server, gived the
good rights and do the first commit. same error.

The only proxy is apache + mod_dav. mod_deflate and mod_ssl too, but
when i deactivating them, it's the same.

Le 28/10/2011 11:41, Stefan Sperling a écrit :
> A shot in the dark: Is it possible that you accidentally loaded
> mod_dav_svn from Subversion 1.7 and mod_authz_svn from Subversion 1.6?
>
> Because this looks as if the client thinks the server supports HTTPv2,
> but the server does not actually support it. Which is weird, because
> mod_dav_svn apparently negotiated HTTPv2 with the client, so it
> should work.
>
> The only possible explanation I can come up with is that parts
> of your server are running 1.6 code, and other parts are running
> 1.7 code.

No, because i do a fresh install and rebuild everything since.
I will retry to rebuild.

The install of my virtualbox, for Daniel Shahaf, maybe solved the
problem, in local.
If it's work with minimal configuration, something goes wrong in my
apache config.

Thanks everyone for helping me :)

-- 
Erwane Breton
      Phea
Tel: 09 51 20 23 23
Mob: 06 76 46 54 61