New MaxSVN releases (incl. 1.8.17 and 1.9.5)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

New MaxSVN releases (incl. 1.8.17 and 1.9.5)

Stefan Hett
Hi,

I'm happy to announce the release of new MaxSVN versions today:
- 1.7.22-6
- 1.8.17-1
- 1.9.5-1
- trunk-dev-r1771118-1

These versions were built with an updated set of dependencies/build tools:
- VS 2015 Update 3
- ActivePerl 5.24.0.2400
- CMake 3.7.0
- NASM 2.12.02 (replacing usage of ml64.exe)
- Python 2.7.12
- SCons 2.5.1
- Apache httpd 2.4.23
- Apache Serf 1.3.9
- Expat 2.2.0
- Neon 0.30.2
- OpenSSL 1.0.2j
- PCRE 8.39
- SQLite 3.15.1

Highlights in these versions are:

- improved SVN test coverage
    - tests cover for tests requiring elevated privileges
    - ensuring deployed content is actually tested
    - MaxSVN 1.7.x: [fsfs] x [ra_local | ra_serf (http) | ra_neon (http)]
    - MaxSVN 1.8.x: [fsfs] x [ra_local | ra_serf (http)]
    - MaxSVN 1.9.x: [fsfs | fsx] x [ra_local | ra_serf (http)]
    - MaxSVN trunk: [fsfs | fsx] x [ra_local | ra_serf (http) | ra_serf
(https)]
- All MaxSVN versions ship with all available standard SVN tools now.
- MaxSVN trunk: Contains the svn mergeinfo normalizer tool again which
was missed in the previous version.
- MaxSVN trunk: Contains a fix for a deadlock condition when utilizing
the experimental fsx filesystem.
- Notable build environment changes
    - Apache httpd builds integrate OpenSSL now (for https-testcoverage
and to make a step towards a feature complete SVN build environment).
    - OpenSSL is built using NASM now (previous builds relied on the
Microsoft assembler (ml64.exe).

Please note that normally we'd have shipped this version with OpenSSL
1.1.0c. However, we decided to postpone an upgrade to OpenSSL 1.1.0 for
the time being due to Apache httpd not having a compatible release
available just yet.

MaxSVN homepage: http://www.luke1410.de/typo3/index.php?id=97
MaxSVN bugtracker: http://www.luke1410.de:8090/browse/MAXSVN



About MaxSVN
MaxSVN is a highly experimental distribution of Apacheā„¢ SubversionĀ®
(SVN) for Windows.
MaxSVN is ***NOT*** meant/designed for production use. If you are
looking for an SVN distribution for daily use, please check out the
alternative SVN distributions for Windows. A partial list is provided
here: https://subversion.apache.org/packages.html#windows

MaxSVN's main purpose is to be used for development of Subversion itself
and for providing a distribution which can be used to test
features/builds as early as possible.
The aim is to provide:
- a distribution which tests SVN against the latest build tools and
dependencies on Windows
- provide early access to versions of SVN while they are in development
- provide a distribution which can be used to debug/test issues yourself
(by providing symbol files)

Regards,
Stefan



smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: New MaxSVN releases (incl. 1.8.17 and 1.9.5)

Johan Corveleyn-3
On Fri, Feb 24, 2017 at 2:43 AM, Stefan <[hidden email]> wrote:
...
> Please note that normally we'd have shipped this version with OpenSSL
> 1.1.0c. However, we decided to postpone an upgrade to OpenSSL 1.1.0 for
> the time being due to Apache httpd not having a compatible release
> available just yet.

I also tried updating some of my dependencies when testing alpha2, and
noticed that serf also fails to link with OpenSSL 1.1.0e (latest
release). I guess it depends on some 1.0.* API that's no longer there
(I don't have the exact failure anymore -- in case others don't see
it, I'll retry it and post the error). Perhaps this is a known issue
for the serf specialists on this list (maybe it's already fixed on
serf@trunk ?), but I'm just putting it out here.

--
Johan
Reply | Threaded
Open this post in threaded view
|

Re: New MaxSVN releases (incl. 1.8.17 and 1.9.5)

Stefan Hett-2
On 2/24/2017 11:06 AM, Johan Corveleyn wrote:

> On Fri, Feb 24, 2017 at 2:43 AM, Stefan <[hidden email]> wrote:
> ...
>> Please note that normally we'd have shipped this version with OpenSSL
>> 1.1.0c. However, we decided to postpone an upgrade to OpenSSL 1.1.0 for
>> the time being due to Apache httpd not having a compatible release
>> available just yet.
> I also tried updating some of my dependencies when testing alpha2, and
> noticed that serf also fails to link with OpenSSL 1.1.0e (latest
> release). I guess it depends on some 1.0.* API that's no longer there
> (I don't have the exact failure anymore -- in case others don't see
> it, I'll retry it and post the error). Perhaps this is a known issue
> for the serf specialists on this list (maybe it's already fixed on
> serf@trunk ?), but I'm just putting it out here.
Yes, Apache Serf 1.3.9 also doesn't build out of the box with OpenSSL
1.1.0(c). Patches are on record at [1] but the issue is currently
restricted from the public. Restrictions are expected to get lifted in a
week or two. In principle it's just some lib file/include folder changes
plus a small code change.
Same goes for Neon 0.30.2 btw. The patches I'd have applied are listed
here, if anybody cares [2].

[1] http://www.luke1410.de:8090/browse/MAXSVN-83
[2] http://www.luke1410.de:8090/browse/MAXSVN-86

--
Regards,
Stefan Hett