> De : David Darj [mailto:z...@alagazam.net] 
> Envoyé : lundi 7 février 2011 18:12
> À : RIBEIRO Philippe (i-BP)
> Cc : users@subversion.apache.org
> Objet : Re: TR: Problem upgrading to Subversion 1.6.15 on 
> Apache 2.0.64 / or on Apache 2.2.17
> 
> 
> On 2011-02-07 14:47, RIBEIRO Philippe (i-BP) wrote: 
> 
>       Hello,
>        
>       Our machine is a Windows Server with :
>       - Windows Server 2003 SP2
>       - Subversion 1.4.3 (installed with svn-1.4.3-setup.exe)
>       - Apache 2.0.59 (installed with 
> apache_2.0.59-win32-x86-no_ssl.msi)
>        
>       And it works very well !
>        
>       I want to upgrade to last stable version of Subversion 
> (1.6.15) and
>       last stable version of Apache 2.0 (2.0.64).
>        
>       1 ) I uninstall Apache 2.0.59, and suppress Apache 
> installation from
>         disk
>       2 ) I uninstall Subversion 1.4.3, and suppress Subversion
>        installation from disk
>       4 ) I install Subversion 1.6.15 (installed with 
>        Setup-Subversion-1.6.15.msi)
>       3 ) I install Apache 2.0.64 (httpd-2.0.64-win32-x86-no_ssl.msi)
>       4 ) I copy mod_dav_svn.so and mod_authz_svn.so from subversion
>        installation/bin to Apache Installation\modules
>         
>       5 ) I add the 2 lines in httpd.conf : 
>           LoadModule dav_svn_module modules/mod_dav_svn.so
>           LoadModule authz_svn_module modules/mod_authz_svn.so
>       6 ) I remove character # from httpd.conf :
>           #LoadModule dav_module modules/mod_dav.so
>           #LoadModule dav_fs_module modules/mod_dav_fs.so
>        
>       When I restart Apache Service, I have the following message :
>       Syntax error on line 174 of 
>       D:\Apache Group\Apache2\conf\httpd.conf:
>       API module structure 'dav_svn_module' in file 
>       D:\Subversion\bin\mod_dav_svn.so is garbled - expected
>       signature 41503230 but saw 41503232 - perhaps this is 
>       not an Apache module DSO, or was compiled for a 
>       different Apache version ?
>        
>       Remark1 : I tried to install last version of Apache 2.2 
> (2.2.17) 
>        with httpd-2.2.17-win32-x86-no_ssl.msi, instead of 
>        Apache 2.0.64. I have the same problem.
>       Remark2 : There are many articles on forums, but no-one 
> gives me a correct procedure.
>        
>       I've been trying many things for 2 days and it doens't 
> still work. I 
>        would be very grateful to you for helping me.
>        
>       Thank you very much.
>        
>       P. RIBEIRO    
>       
> 
> Hi
> 
> If you are using my binaries from win32svn on sourceforge (or 
> from alagazam.net) they will NOT work on Apache 2.0.x
> You will need to upgrade to Apache 2.2.x
> 
> /David a.k.a. Alagazam
> 
> > -----Original Message-----
> From: RIBEIRO Philippe (i-BP) 
> Sent: 08 February 2011 08:32
> To: David Darj
> Cc: users@subversion.apache.org
> Subject: RE: TR: Problem upgrading to Subversion 1.6.15 on 
> Apache 2.0.64 / or on Apache 2.2.17
> 
> Hi David,
>  
> Yes I am using binaries from win32svn on Sourceforge : I 
> downloaded  Setup-Subversion-1.6.15.msi
> from the site, and installed Subversion by executing the .msi.
>  
> When installing Apache 2.2.X (Apache 2.2.17 which is the last 
> stable version), it doesn't work either.
> I use mod_auth_sspi.so 1.0.4.0, anf I have the following 
> error message :
>  
> API module structure ' sspi_auth_module' in file 
> D:\Subversion\bin\mod_ auth_ sspi.so is garbled - expected
> signature 4150323 20 but saw 4150323 02 - perhaps this is 
> not an Apache module DSO, or was compiled for a 
> different Apache version ?
> 
>  
> Do you know where I could find a version of mod_auth_sspi 
> which works with apache 2.2.17 ?
> Thanks a lot.
> P. RIBEIRO
> Philippe RIBEIRO
> 
First, why is apache looking in D:\Subversion\bin\ for modules (how have you 
managed that, I'm intrigued?)

Next, I assume you are using sspi to authenticate against an AD domain ~ why 
not use the properly supported mod_authnz_ldap ~ I know it takes a while to get 
working but it is supported and does work...

When I looked into this, mod_auth_sspi had been unmaintained for several years 
and there appear to be known issues in the latest versions (some of the 
slightly earlier versions are better, apparently).

~ mark c

Reply via email to