Re: Subversion On Windows Server

2021-03-05 Thread Daniel Sahlberg
Den fre 5 mars 2021 kl 15:11 skrev Uwe Jans :

> Hi all,
>
> searching the web I found "tested on Windows Server 2012, 2008, 2003".
> Is there a plan to test Subversion against Windows Server 2019?
>
> We have been using Subversion for many years, running on Windows Server
> 2012 supported by our IT department.
> Since Microsoft will stop supporting Windows Server 2012 in 2023, our
> systems will be upgraded to Windows Server 2019.
> Our IT department refuses to install Subversion as long as there is no
> statement about test results under Windows Server 2019.
>

The Subversion project doesn't provide any binary packages and you will
probably get better answers by check with whoever supply the client and/or
server that you are using. For example, if you are using VisualSVN Server
then you should check with them, if you are using TortoiseSVN then you
should check with them.

That being said, I'm using Subversion on Windows 2019 and Windows 10
without any problems.

Kind regards,
Daniel Sahlberg


Subversion On Windows Server

2021-03-05 Thread Uwe Jans

  
  
Hi all,
  
  searching the web I found "tested on Windows Server 2012, 2008,
  2003".
  Is there a plan to test Subversion against Windows Server 2019?
  
  We have been using Subversion for many years, running on Windows
  Server 2012 supported by our IT department.
  Since Microsoft will stop supporting Windows Server 2012 in 2023,
  our systems will be upgraded to Windows Server 2019.
  Our IT department refuses to install Subversion as long as there
  is no statement about test results under Windows Server 2019.
-- 
Best regards
Dipl.-Phys. Uwe Jans
Emmi-Kurzke-Str. 13, D-24306 Ploen

  



Re: Compilation of Subversion on Windows Server 2008 is failing

2016-03-15 Thread Daniel Shahaf
subhadarsan das wrote on Tue, Mar 15, 2016 at 11:09:29 +:
> Hi Team,
> We are trying to install subversion 1.9.3 on Windows 2008 Server with Apache 
> Haus 2.4 which already has APRĀ  and OpenSSL compiled into it. We however have 
> ignored the optional packages and sticking to core packages only. We have 
> Visual Studio 2015 Community Edition installed on our machine.
> 
> However, after running 'python gen-make.py --vsnet-vesion=2015' we still are 
> not getting the subversion_vcnet.sln created. Output of the gen-make.py 
> reports this warning message:
> 
> "WARNING: errno intersects APR error codes: ..."
> There are few numeric codes that are reported with the above warning.
> Any help would be appreciated. Also, please let us know if you need more 
> information.

This warning means, that when svn prints an error message of the form
"svn: E02 (errno=ENOENT)", where 02 is one of the numeric values
printed in the error message, the numeric value will be correct but the
symbolic value "ENOENT" part might be wrong, since two different symbols
map to the same numeric value.

The warning is, in fact, possibly premature: it happens whenever the
Python and APR data sources define a mapping for the same numeric value,
but doesn't check whether the mapped string values are different.

I've now fixed both of these issues: https://svn.apache.org/r1735179

That warning by itself is mostly harmless, and isn't what stops your
*.sln file from being created.  That said, I don't know whether that
warning is normal in windows builds or indicative of some deeper
problem.

Cheers,

Daniel

> Regards,Subha


Compilation of Subversion on Windows Server 2008 is failing

2016-03-15 Thread subhadarsan das
Hi Team,
We are trying to install subversion 1.9.3 on Windows 2008 Server with Apache 
Haus 2.4 which already has APRĀ  and OpenSSL compiled into it. We however have 
ignored the optional packages and sticking to core packages only. We have 
Visual Studio 2015 Community Edition installed on our machine.

However, after running 'python gen-make.py --vsnet-vesion=2015' we still are 
not getting the subversion_vcnet.sln created. Output of the gen-make.py reports 
this warning message:

"WARNING: errno intersects APR error codes: ..."
There are few numeric codes that are reported with the above warning.
Any help would be appreciated. Also, please let us know if you need more 
information.
Regards,Subha