You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Julian Foad <ju...@apache.org> on 2018/03/29 13:17:00 UTC

Subversion1.10.0-rc2 up for testing/signing

The 1.10.0-rc2 release artifacts are now available for testing/signing.
Please get the tarballs from
   https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.

Thanks!

Re: Subversion1.10.0-rc2 up for testing/signing

Posted by Branko Čibej <br...@apache.org>.
Summary:

    +1 to release (Unix)

Platform

    macOS High Sierra 10.13.3

    Standard dependencies:
      Apple LLVM version 9.0.0 (clang-900.0.39.2)
      ruby 2.3.3p222 (2016-11-21 revision 56859)
      Python 2.7.10

    Dependencies from Homebrew:
      APR 1.6.3
      APR-Util 1.6.1
      httpd 2.4.29
      SQLite 3.22.0
      Serf 1.3.9
      OpenSSL 1.0.2n
      zlib 1.2.11
      LZ4 1.8.1.2
      utf8proc 2.1
      BDB 6.2.32
      Perl 5.26.1
      Swig 3.0.12

    Other dependencies:
      Java 1.8.0_45-b14
      JUnit 4.11

Verified:

  - Tarball contents and signatures
  - check ((fsfs, bdb) × (local, svnserve, dav))
  - check-all-javahl
  - check-swig-py
  - check-swig-rb
  - check-swig-pl

Known issues:

  - 'make check-swig-py' requires 'make install install-swig-py'.
    Probably a side effect of macOS "security" features related to the
    use of the DYLD_LIBRARY_PATH environment variable.

  - 'make check-swig-rb' requires 'make install install-swig-rb'.
    Probably a side effect of macOS "security" features related to the
    use of the DYLD_LIBRARY_PATH environment variable.

 GPG signatures committed to the dist/dev/subversion repository.


Re: Subversion1.10.0-rc2 up for testing/signing

Posted by Branko Čibej <br...@apache.org>.
Summary:

    +1 to release (Windows)

Platform

    Windows 10 Pro x64

    Build tools:
      Microsoft Visual Studio Professional 2015
      CMake 3.2.3
      SCons 2.3.4 (patched for MSVC14)

    Source dependencies:
      APR 1.5.2
      APR-Util 1.5.4
      zlib 1.2.8
      httpd 2.4.16 with pcre-8.37
      SQLite 3.8.8.3 (amalgamated)
      Serf 1.3.8
      OpenSSL 1.0.2

    Other dependencies:
      Python 2.7.9
      Perl 5.26.1 (Strawberry Perl)
      Ruby 2.3.3
      Swig 3.0.12
      Java 1.8.0_45-b14
      JUnit 4.11

Verified:

  Tarball contents and signatures

  (fsfs) x (local, svnserve, serf)
  check-javahl
  check-swig-py
  check-swig-pl

Known issues:

  * Ruby 2.x bindings do not build with VS2015

GPG signatures committed to the dist/dev/subversion repository.


Re: Subversion1.10.0-rc2 up for testing/signing

Posted by Stefan Fuhrmann <st...@apache.org>.
On 29.03.2018 15:17, Julian Foad wrote:
> The 1.10.0-rc2 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!
>
Summary:

   +1 to release

Platform

   Ubuntu 16.04.4 x64, Linux 4.13.0-37-lowlatency x86_64

   Standard dependencies:
     Apache 2.4.18, worker MPM
     APR 1.5.2
     APR-Util 1.5.4
     BDB 5.3.28
     GCC 5.4.0
     JUnit 4.12
     libmagic 5.25
     libtool, libtool-bin 2.4.6
     OpenJDK-8 8u162
     OpenSSL 1.0.2g
     Perl 5.22.1
     Python 2.7.12
     Ruby 2.3.1p112
     Serf 1.3.8
     SQLite 3.11.0
     Swig 2.0.12
     utf8proc 1.3.1
     zlib 1.2.8

   Manually installed and in-tree dependencies:
     ctypesgen svn-r151

Verified:

   Tarball contents and signatures

   (fsfs, bdb, fsx) x (local, svnserve, serf)
   check-swig-py
   check-swig-pl
   check-swig-rb
   check-javahl
   check-ctypes-python

   ./get-deps.sh

   All relevant tests passed, see known issues.

Known issues:

   (Ubuntu issue) ./configure needed global variables set to make LTO work:
                  AR="gcc-ar" NM="gcc-nm" RANLIB=gcc-ranlib
   (Linux issue) running BDB tests concurrently requires max open files
                 to be set to at least 1024.
   (Perl tests) Several warnings due to closing invalid file handles
   (Java tests) 3 warnings about JNI local refs exceeding capacity

GPG Signatures committed to the dist/dev/subversion repository.



Re: Subversion1.10.0-rc2 up for testing/signing

Posted by Johan Corveleyn <jc...@gmail.com>.
On Thu, Mar 29, 2018 at 3:17 PM, Julian Foad <ju...@apache.org> wrote:
> The 1.10.0-rc2 release artifacts are now available for testing/signing.
> Please get the tarballs from
>   https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!

Summary
-------
+1 to release

Platform
--------
Windows 7 SP1 (x64)
Microsoft Visual Studio 2017

Verified
--------
Signature, sha1 and sha512 for subversion-1.10.0-rc2.zip.

Contents of subversion-1.10.0-rc2.zip are identical to tags/1.10.0-rc2,
and to branches/1.10.x@1827917 (except for expected differences in
svn_version.h and svnpubsub, svnwcsub and nominate.pl (symlinks vs. file
contents), and generated files).

Tested
------
[ Release build x86 ] x [ fsfs ] x [ file | svn | http ]
check-javahl

Results
-------
All tests pass.

Dependencies
------------
Httpd 2.4.29 (pcre 8.41, apr 1.6.3, apr-iconv 1.22, apr-util 1.6.1, expat 2.2.5)
Apr 1.6.3
Apr-Util 1.6.1
OpenSSL 1.0.2n
Serf 1.3.9
SQLite 3.22.0.0
ZLib 1.2.11

Other tools
-----------
Perl 5.20 (Strawberry Perl)
Python 2.7.9
JDK 1.8.0_161 (x86)
JUnit 4.12

Signature
---------

subversion-1.10.0-rc2.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABCgAGBQJawBP1AAoJELWc5tYBDIqtxkkQAL4NM0dfSQ7FWN0ufhHYgUYj
5lsYYUwp86+i0sbjKVrpXJ5FoYuCnKCD2ihGtEWfBqXb+gzo4DH1dXc185DRH8qb
O9dONHC1uKARILx+scVMthprvoq5wKFGYY1uxLQWbRdp5dYSL6Uopd+h8BNYcYvj
P9isiryHXZSczoocosT2bNKqIEuNQ33aD4i7VeLw8WcVjkqgzXCfR7hoTqzBoKI0
lET1I/xyAmN9bHbtbj45WbmBaTfi+qoRZtEz7EV5EuxvKPZ9TODGxlwKhhAYG7fF
pLsM+7/PEfGLmb9hrAWYk+ZkMCIyIpAuqvCqFLzsU8exGpfSF0P1hfly7Su1CNxq
BFhtUAzIlPaUU1AHRUx9tJ/uwPWNxpgxsm7QB6+7m+egtl/Lgozix4SybjU+8AZ9
tHvJzN8tu3MMaFubh06veU8AFn2uPy2fWsusb8jFgf/20M57nYryonCfuUXnCWQn
jLlvAWFsfHA9Pg9ZomtIVAT+Dbxfy9PtrdI4/GaCzGglmdS1ncccEEp2fH+yoxOG
9rzLfHN6Hk9dvfOP7GPFp4Tc0hUd6d4/J88Ll3Vh+kpJwl91YD5N92D1cAnb/L2D
UYCTeOv9sPKDgZVlUa/rTLkeEomF6rDOwDZvIQy2Dwb5Z2CDc0vuncjp0aUZ8TXo
rzgiDFXmHQddg3WXnFq8
=Uio8
-----END PGP SIGNATURE-----

-- 
Johan

Re: Warnings from the bindings

Posted by Branko Čibej <br...@apache.org>.
On 07.04.2018 21:20, Philip Martin wrote:
> Branko Čibej <br...@apache.org> writes:
>
>> I'll take another look. At the very least this should be using the local
>> frame manager object, which is exception-safe, unlike explicitly pushing
>> and popping the frame.
> ImmutableList::for_each iterates and constructs arbitrary types T.  The
> problem occurs when T is ExternalItem as the constructor generates local
> refs from the get_string_field and get_revision_field calls.  It's
> possible that we should modify ExternalItem to avoid doing this, but
> for_each should also work with arbitrary types and so for_each should
> use a local frame.  I've comitted the for_each change.

Looks good, thanks!

-- Brane

Re: Warnings from the bindings

Posted by Philip Martin <ph...@codematters.co.uk>.
Branko Čibej <br...@apache.org> writes:

> I'll take another look. At the very least this should be using the local
> frame manager object, which is exception-safe, unlike explicitly pushing
> and popping the frame.

ImmutableList::for_each iterates and constructs arbitrary types T.  The
problem occurs when T is ExternalItem as the constructor generates local
refs from the get_string_field and get_revision_field calls.  It's
possible that we should modify ExternalItem to avoid doing this, but
for_each should also work with arbitrary types and so for_each should
use a local frame.  I've comitted the for_each change.

-- 
Philip

Re: Warnings from the bindings

Posted by Branko Čibej <br...@apache.org>.
On 07.04.2018 00:25, Philip Martin wrote:
> Philip Martin <ph...@codematters.co.uk> writes:
>
>>        Iterator iter(get_iterator());
>>        while (iter.has_next())
>> +      {
>> +        m_env.PushLocalFrame(10);
>>          function(T(m_env, NativeT(iter.next())));
>> +        m_env.PopLocalFrame();
>> +      }
>>        return function;
> Rewriting as:
>
>       while (iter.has_next())
>       {
>         NativeT nt(iter.next());
>         m_env.PushLocalFrame(10);
>         T t(m_env, nt);
>         function(t);
>         m_env.PopLocalFrame();
>       }
>
> also removes the warning, but if I move the T construction before the
> PushLocalframe then the warning returns.  T is JavaHL:ExternalItem.

I'll take another look. At the very least this should be using the local
frame manager object, which is exception-safe, unlike explicitly pushing
and popping the frame.

-- Brane

Re: Warnings from the bindings

Posted by Philip Martin <ph...@codematters.co.uk>.
Philip Martin <ph...@codematters.co.uk> writes:

>        Iterator iter(get_iterator());
>        while (iter.has_next())
> +      {
> +        m_env.PushLocalFrame(10);
>          function(T(m_env, NativeT(iter.next())));
> +        m_env.PopLocalFrame();
> +      }
>        return function;

Rewriting as:

      while (iter.has_next())
      {
        NativeT nt(iter.next());
        m_env.PushLocalFrame(10);
        T t(m_env, nt);
        function(t);
        m_env.PopLocalFrame();
      }

also removes the warning, but if I move the T construction before the
PushLocalframe then the warning returns.  T is JavaHL:ExternalItem.

-- 
Philip

Re: Warnings from the bindings

Posted by Philip Martin <ph...@codematters.co.uk>.
Philip Martin <ph...@codematters.co.uk> writes:

> Branko Čibej <br...@apache.org> writes:
>
>> And I don't see these, either. I checked the code and we explicitly use
>> a JNI local frame in the core loop of unparseExternals. Try as I might,
>> I can't see where all those local references could be coming from.
>
> ImmutableList::for_each appears to be the problem.  The following ugly
> hack is not correct but does resolve the warning:

That is more complicated than necessary.  iter.has_next is not the
problem, just the function call.  Probably this is still fixing the
symptom rather than the underlying problem:

Index: subversion/bindings/javahl/native/jniwrapper/jni_list.hpp
===================================================================
--- subversion/bindings/javahl/native/jniwrapper/jni_list.hpp	(revision 1828477)
+++ subversion/bindings/javahl/native/jniwrapper/jni_list.hpp	(working copy)
@@ -173,7 +173,11 @@ class ImmutableList : public BaseImmutableList
     {
       Iterator iter(get_iterator());
       while (iter.has_next())
+      {
+        m_env.PushLocalFrame(10);
         function(T(m_env, NativeT(iter.next())));
+        m_env.PopLocalFrame();
+      }
       return function;
     }
 };

-- 
Philip

Re: Warnings from the bindings

Posted by Philip Martin <ph...@codematters.co.uk>.
Branko Čibej <br...@apache.org> writes:

> And I don't see these, either. I checked the code and we explicitly use
> a JNI local frame in the core loop of unparseExternals. Try as I might,
> I can't see where all those local references could be coming from.

ImmutableList::for_each appears to be the problem.  The following ugly
hack is not correct but does resolve the warning:

Index: subversion/bindings/javahl/native/jniwrapper/jni_list.hpp
===================================================================
--- subversion/bindings/javahl/native/jniwrapper/jni_list.hpp	(revision 1828477)
+++ subversion/bindings/javahl/native/jniwrapper/jni_list.hpp	(working copy)
@@ -172,8 +172,18 @@ class ImmutableList : public BaseImmutableList
   F for_each(F function) const
     {
       Iterator iter(get_iterator());
-      while (iter.has_next())
+      while (true)
+      {
+        m_env.PushLocalFrame(10);
+	bool has_next = iter.has_next();
+	if (!has_next)
+	{
+          m_env.PopLocalFrame();
+	  break;
+	}
         function(T(m_env, NativeT(iter.next())));
+        m_env.PopLocalFrame();
+      }
       return function;
     }
 };

-- 
Philip

Re: Warnings from the bindings

Posted by Branko Čibej <br...@apache.org>.
On 03.04.2018 13:28, Stefan Fuhrmann wrote:
> On 30.03.2018 00:27, Philip Martin wrote:
>

>> WARNING in native method: JNI call made without checking exceptions when required to from CallStaticObjectMethod
> Seen these in alpha2 but not in rc2. Java8 has
> been updated since then. 

I don't see this on OSX with 1.8.0_45-b14.


>> but it's not clear to me which bit of source code is responsible.  There
>> are also warnings for:
>>
>> WARNING: JNI local refs: 33, exceeds capacity: 32
>>   at org.apache.subversion.javahl.util.PropLib.unparseExternals(Native Method)
>>   at org.apache.subversion.javahl.SVNUtil.unparseExternals(SVNUtil.java:790)
> Those are a known issue. There used to be 10-ish
> such warnings and now they are down to 3. I vaguely
> recall that there had been an actual fix and we are
> now seeing the remaining unpatched occurrences.

And I don't see these, either. I checked the code and we explicitly use
a JNI local frame in the core loop of unparseExternals. Try as I might,
I can't see where all those local references could be coming from.

-- Brane


Re: Warnings from the bindings

Posted by Stefan Fuhrmann <st...@apache.org>.
On 30.03.2018 00:27, Philip Martin wrote:
> Philip Martin<ph...@codematters.co.uk>  writes:
>
>>    +1 to release
> The swig-pl tests produce warnings for:
>
> Warning: unable to close filehandle $out_fh properly: Bad file descriptor at /home/pm/sw/subversion/sign/build/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm line 58.
FWIW, I see the same on Ubuntu 16.04.4 and
they have been present in alpha2 already.
> Core.pm:58 is a call to apr_terminate() so perhaps pool cleanup is
> attempting to close a file that has been already closed.
>
> The JavaHL tests produce warnings for:
>
> WARNING in native method: JNI call made without checking exceptions when required to from CallStaticObjectMethod
Seen these in alpha2 but not in rc2. Java8 has
been updated since then.
> but it's not clear to me which bit of source code is responsible.  There
> are also warnings for:
>
> WARNING: JNI local refs: 33, exceeds capacity: 32
>    at org.apache.subversion.javahl.util.PropLib.unparseExternals(Native Method)
>    at org.apache.subversion.javahl.SVNUtil.unparseExternals(SVNUtil.java:790)
Those are a known issue. There used to be 10-ish
such warnings and now they are down to 3. I vaguely
recall that there had been an actual fix and we are
now seeing the remaining unpatched occurrences.

-- Stefan^2.



Re: Warnings from the bindings

Posted by Philip Martin <ph...@codematters.co.uk>.
Stefan Sperling <st...@apache.org> writes:

> On Fri, Mar 30, 2018 at 09:29:47AM +0200, Branko Čibej wrote:
>> I've never seen either of these warnings and I don't see what could've
>> changed on the 1.10.x branch to make them suddenly start appearing.
>
> The Perl one happens on OpenBSD as well. It is not new. I don't exactly
> know when it started but I believe it started before 1.10 was branched.

Yes, I didn't mean to imply that any of these are new.  It's possible
the JavaHL ones started when I switched from Java 8 to Java 9.

-- 
Philip

Re: Warnings from the bindings

Posted by Stefan Sperling <st...@apache.org>.
On Fri, Mar 30, 2018 at 09:29:47AM +0200, Branko Čibej wrote:
> On 30.03.2018 00:27, Philip Martin wrote:
> > Philip Martin <ph...@codematters.co.uk> writes:
> >
> >>   +1 to release
> > The swig-pl tests produce warnings for:
> >
> > Warning: unable to close filehandle $out_fh properly: Bad file descriptor at /home/pm/sw/subversion/sign/build/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm line 58.
> >
> > Core.pm:58 is a call to apr_terminate() so perhaps pool cleanup is
> > attempting to close a file that has been already closed.
> >
> > The JavaHL tests produce warnings for:
> >
> > WARNING in native method: JNI call made without checking exceptions when required to from CallStaticObjectMethod
> >
> > but it's not clear to me which bit of source code is responsible.  There
> > are also warnings for:
> >
> > WARNING: JNI local refs: 33, exceeds capacity: 32
> >   at org.apache.subversion.javahl.util.PropLib.unparseExternals(Native Method)
> >   at org.apache.subversion.javahl.SVNUtil.unparseExternals(SVNUtil.java:790)
> 
> I've never seen either of these warnings and I don't see what could've
> changed on the 1.10.x branch to make them suddenly start appearing.

The Perl one happens on OpenBSD as well. It is not new. I don't exactly
know when it started but I believe it started before 1.10 was branched.

https://ci.apache.org/builders/svn-bb-openbsd/builds/62/steps/Test%20bindings/logs/testlog-swig-pl

JavaHL doesn't even build on OpenBSD anymore these days, so no idea.
(I don't think anybody would need JavaHL on this platform.)

Re: Warnings from the bindings

Posted by James McCoy <ja...@jamessan.com>.
On Fri, Mar 30, 2018 at 09:29:47AM +0200, Branko Čibej wrote:
> On 30.03.2018 00:27, Philip Martin wrote:
> > Philip Martin <ph...@codematters.co.uk> writes:
> >
> >>   +1 to release
> > The swig-pl tests produce warnings for:
> >
> > Warning: unable to close filehandle $out_fh properly: Bad file descriptor at /home/pm/sw/subversion/sign/build/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm line 58.
> >
> > Core.pm:58 is a call to apr_terminate() so perhaps pool cleanup is
> > attempting to close a file that has been already closed.
> >
> > The JavaHL tests produce warnings for:
> >
> > WARNING in native method: JNI call made without checking exceptions when required to from CallStaticObjectMethod
> >
> > but it's not clear to me which bit of source code is responsible.  There
> > are also warnings for:
> >
> > WARNING: JNI local refs: 33, exceeds capacity: 32
> >   at org.apache.subversion.javahl.util.PropLib.unparseExternals(Native Method)
> >   at org.apache.subversion.javahl.SVNUtil.unparseExternals(SVNUtil.java:790)
> 
> I've never seen either of these warnings and I don't see what could've
> changed on the 1.10.x branch to make them suddenly start appearing.

They're not new.  They've been happening for the past 2 years in Debian.
It looks like they popped up when we started building with Java 8.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Re: Warnings from the bindings

Posted by Branko Čibej <br...@apache.org>.
On 30.03.2018 00:27, Philip Martin wrote:
> Philip Martin <ph...@codematters.co.uk> writes:
>
>>   +1 to release
> The swig-pl tests produce warnings for:
>
> Warning: unable to close filehandle $out_fh properly: Bad file descriptor at /home/pm/sw/subversion/sign/build/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm line 58.
>
> Core.pm:58 is a call to apr_terminate() so perhaps pool cleanup is
> attempting to close a file that has been already closed.
>
> The JavaHL tests produce warnings for:
>
> WARNING in native method: JNI call made without checking exceptions when required to from CallStaticObjectMethod
>
> but it's not clear to me which bit of source code is responsible.  There
> are also warnings for:
>
> WARNING: JNI local refs: 33, exceeds capacity: 32
>   at org.apache.subversion.javahl.util.PropLib.unparseExternals(Native Method)
>   at org.apache.subversion.javahl.SVNUtil.unparseExternals(SVNUtil.java:790)

I've never seen either of these warnings and I don't see what could've
changed on the 1.10.x branch to make them suddenly start appearing.

-- Brane

Re: Warnings from the bindings

Posted by Philip Martin <ph...@codematters.co.uk>.
Philip Martin <ph...@codematters.co.uk> writes:

> WARNING in native method: JNI call made without checking exceptions
> when required to from CallStaticObjectMethod
>
> but it's not clear to me which bit of source code is responsible.

This might be a false alarm.  From

https://github.com/dropbox/djinni/issues/152#issuecomment-157220326

if I do

  echo 'public class Foo { public static void main(String[] args) throws Exception { } }' > Foo.java
  javac Foo.java
  java -Xcheck:jni Foo

I see the same warning as above.

-- 
Philip

Warnings from the bindings

Posted by Philip Martin <ph...@codematters.co.uk>.
Philip Martin <ph...@codematters.co.uk> writes:

>   +1 to release

The swig-pl tests produce warnings for:

Warning: unable to close filehandle $out_fh properly: Bad file descriptor at /home/pm/sw/subversion/sign/build/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm line 58.

Core.pm:58 is a call to apr_terminate() so perhaps pool cleanup is
attempting to close a file that has been already closed.

The JavaHL tests produce warnings for:

WARNING in native method: JNI call made without checking exceptions when required to from CallStaticObjectMethod

but it's not clear to me which bit of source code is responsible.  There
are also warnings for:

WARNING: JNI local refs: 33, exceeds capacity: 32
  at org.apache.subversion.javahl.util.PropLib.unparseExternals(Native Method)
  at org.apache.subversion.javahl.SVNUtil.unparseExternals(SVNUtil.java:790)

-- 
Philip

Re: Subversion1.10.0-rc2 up for testing/signing

Posted by Philip Martin <ph...@codematters.co.uk>.
Cummary:

  +1 to release

Platform:

  Debian/stable (stretch 64-bit)

Tested:

  (local, svn, serf, serf/v1) x (fsfs, fsfs/pack/shard, bdb, fsx)
  (svn, serf) x (fsfs/block)
  swig-pl, swig-py, swig-rb, ctypes-python
  (javahl, tigris-javahl) x (fsfs, bdb, fsx)

Results:

  All tests PASS except ra-test 13 over http v1 (this is a known
  failure).

Local dependencies:

  apache2-dev : 2.4.25-3+deb9u3
  libapr1-dev : 1.5.2-5
  libaprutil1-dev : 1.5.4-3
  libdb5.3-dev : 5.3.28-12+deb9u1
  libsasl2-dev : 2.1.27~101-g0780600+dfsg-3
  libserf-dev : 1.3.9-3
  libsqlite3-dev : 3.16.2-5+deb9u1
  perl : 5.24.1-3+deb9u2
  python2.7-dev : 2.7.13-2+deb9u2
  ruby-dev : 1:2.3.3
  openjdk-9-jdk-headless: 9~b181-4~bpo9+1

subversion-1.10.0-rc2.tar.bz2

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEqER5D7V0NgbulZIHdteI4e0aWZwFAlq9YnEACgkQdteI4e0a
WZzCegf/cmI9Vr3LPJXjK00te1Tmf1GbRrbIxSdFLONvGYGtSaxaaCGPWJ0TTEom
zl06sfuQO5yz9kJ2PvSatonKSYoTxEaG2daLfBe7K/bwWdFTgsDsyDp454IfCvtR
ZHK5x9O7L6KaigfArsX9+BG2aBFzFlGwYc6UqriwsvOaBAcdXoUwTqnarcWb32aU
KUJkQyy+x6DAQKzYtKJn9ygEvZXpgBQPhnCdTFT2PyyZaAPJlOV39SNOUHbitT0+
jxGuRUyCn8J9ynF6cCd78mjxoSkIXuhH9n+obgNucoPGEjfib6iAH5UNE4oGRzVD
EOmd0MXP8U8x7OsBVgSkPwlp7VbK2A==
=Liy8
-----END PGP SIGNATURE-----

subversion-1.10.0-rc2.tar.gz

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEqER5D7V0NgbulZIHdteI4e0aWZwFAlq9YnEACgkQdteI4e0a
WZwcCQf+OEjArSNn2aokhwHjVLc2w25AgiAxYzPsvnzX0XXQG1LsFjRLTmCEUO8n
bq8N9begwhMHp58+6KUSYyjbD0KAWQQWarIxgvO6r6WS3WukNa15WzR4rJmjAp07
v2WT+HBBG01v4rMFHiBCOgCQMmdzvcBeLH52hgk4KBwrwHBjCtzRsKTR+Uyx/TuK
9LvHA7nWBC8XOpKa0PSvqhAIzhocAd57LLpUwPfa5PYSSD0LQ8o18TnTXEQiiGbK
mJVgODzTEeDMQxfez6gnkpIJNcqt0g4a2d+9PgE0D/FE6aLifObzXP9Zoh+diR3z
KnLNeyWz5epJg7SE3jUCngV/SoclNQ==
=RhQc
-----END PGP SIGNATURE-----

-- 
Philip

Re: Subversion1.10.0-rc2 up for testing/signing

Posted by Stefan Sperling <st...@apache.org>.
On Thu, Mar 29, 2018 at 02:17:00PM +0100, Julian Foad wrote:
> The 1.10.0-rc2 release artifacts are now available for testing/signing.
> Please get the tarballs from
>   https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
> 
> Thanks!

Summary: +1 to release

Tested: [bdb | fsfs] x [ra_local | ra_svn | ra_serf]
        swig bindings

Test results: All passed.

Platform: OpenBSD 6.3 amd64

Dependencies:
bdb:        4.7.25
GNU-iconv:  1.15
apr:        1.5.2
apr-util:   1.5.4
httpd:      2.2.32
serf:       1.3.9
cyrus-sasl: 2.1.25
sqlite:     3160200
lz4:        1.7.5
libssl:     LibreSSL 2.7.0
swig:       3.0.12
python:     2.7.13
perl:       5.24.3
ruby:       2.4.2

Signatures:

subversion-1.10.0-rc2.tar.gz
-----BEGIN PGP SIGNATURE-----

iQEcBAABAgAGBQJavhrtAAoJEE99uqmaWblz4c4H/0ONSE2RYv0N4sypTP7lUWlq
53XVdlKY7LVkXure4CRlgkLBglV2aoafufxIUNFB4K3GfE7RK17fxfkkpuLW3dAr
4GKDvj6qfBh7i9N7bg07hrTG0Tvza/CuLkoR0C9w18PqjdpAFniuw+ojsR72sZSQ
IyYPJtIZVi47mUJ4JaCKXVaHr8fUWPf00ZN2ZAqeOCt9RsvE3bG4S9VepPD3CS43
P/QteNtPniPFl/goFJSlB5MAHfijNuG1weCommYLmXBs7p83GYTi5il80VFZT85x
1hS8vz9ZejPjKhGiqWqf1ObGj20KlT4zygUdQylvaCyUav42XjJILMBEity4Df4=
=NQWp
-----END PGP SIGNATURE-----

subversion-1.10.0-rc2.tar.bz2
-----BEGIN PGP SIGNATURE-----

iQEcBAABAgAGBQJavhrwAAoJEE99uqmaWblz0N0H/19VPFLHPzvXnuzJ9q2it2zX
3916IWcofrWCPk5aEGHU7OVLwB/gOKRlH3Ye/jsnI5NJLAI3iFgOGqd6rb2muepC
9GwO6tn5TsKg60X3LgxJsPGQGy95ZVwzqwRnyikOW7MlSj8viZHSIWZXGOp+ZHV3
20DiaKAj/rwCo3B+V5V4oc9e0swa3edwx+32setj8W4OwPuiIJMl6D1S/BtvLFFG
MGQDUcCsXdmtJ2LPahRkPOUSl7iVIheAT0lb86kcL0it+nz+LiUrcgbg1OB4kYfI
REjQIvMGEJZKVgu71yU1j2D31BJWy8QGrRdBwrYKPSQpNIigtqhREN2+iqsUP/A=
=xWPI
-----END PGP SIGNATURE-----

Re: Subversion1.10.0-rc2 up for testing/signing

Posted by Stefan <lu...@posteo.de>.
On 29/03/2018 15:17, Julian Foad wrote:
> The 1.10.0-rc2 release artifacts are now available for testing/signing.
> Please get the tarballs from
>   https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!

Summary
-------
    +1 to release

Platform
--------
    - Windows 10 (build 1709) 64-bit
    - Visual Studio 2015 Update 3

    - ActivePerl: 5.24.0.2400 (for OpenSSL)
    - AWK: 20070501
    - CMake 3.7.0 (for OpenSSL)
    - NASM 2.12.02 (for OpenSSL)
    - Python 2.7.12
    - SCons 2.5.1 (for Apache Serf)

Verified
--------
subversion-1.10.0-rc2.tar.bz2:
    Signature verified.
    SHA-1: 8d79006f0ae53536d7c1d28bbf86f677042f3e9b (matches provided
SHA-1-checksum)
    SHA-512:
42e604f4888f801236a280a6ac6f27a5c4b158d87c81a50d235ec7915bf29ebe05cdd716b6b1f6851f326ffb8c9c4d608b06f20114e690d81eb91b6869083307
(matches provided SHA-512-checksum)

subversion-1.10.0-rc2.tar.gz:
    Signature verified.
    SHA-1: 44d224ad63f3bdef33bb1dbca67609b2d936cf58 (matches provided
SHA-1-checksum)
    SHA-512:
4a80e251a91d047b71c7fbb50455598c2cbb31c0f7700637f2232fdd84a1e0d8890b9a155846eb7e843ac40c2ecaf462c10258f8d46ab5fda5e742908868f5e2
(matches provided SHA-512-checksum)

subversion-1.10.0-rc2.zip:
    Signature verified.
    SHA-1: f984d499cb5f522fd2c796d15ccbdb21cd83ba8c (matches provided
SHA-1-checksum)
    SHA-512:
b3ce527f38999bd98cb1067bad20091f5250a36875cd23ad8b16de28f1a58a140b39d217b2aa84ffec0faf453e3c7da75ee5ac543b20ab823fc4a9d393f57571
(matches provided SHA-512-checksum)

Contents of subversion-1.10.0-rc2.tar.bz2 equals contents of
subversion-1.10.0-rc2.tar.gz.
Contents of subversion-1.10.0-rc2.zip equals contents of
subversion-1.10.0-rc2.tar.bz2 with the expected differences:
    - Windows vs. Linux line ending changes
    - non-Windows-specific generated files missing in zip archive
    - different time stamp in subversion\po\subversion.pot
    - different paths in comments in generated header files
Contents of subversion-1.10.0-rc2.zip equals contents of tags/1.10.0-rc2
with the expected differences:
    - differences related to svn-keywords in files (URL, timestamps)
    - differences related to symlinks in nominate.pl, svnpubsub, svnwcsub
    - generated header files and subversion.pot file only present in zip
archive
    - excluded folders from zip archive: contrib, notes
    - excluded files from zip archive: STATUS

Dependencies
------------
    - APR: 1.5.2 (patched with MAXSVN-42, MAXSVN-43, MAXSVN-94)
    - APRICONV: 1.2.1 (patched with MAXSVN-45, MAXSVN-46)
    - APRUTIL: 1.5.4 with Expat 2.2.0 (patched with MAXSVN-44,
MAXSVN-46, MAXSVN-47, MAXSVN-76, MAXSVN-94)
    - Apache httpd: 2.4.23 (patched with MAXSVN-48, MAXSVN-91)
    - Apache Serf: 1.3.9 (patched with MAXSVN-51, MAXSVN-84)
    - OpenSSL: 1.0.2j
    - PCRE: 8.39
    - SQLite: 3.15.1 (amalgamation)
    - ZLib: 1.2.8

Patches applied to SVN
----------------------
    - MAXSVN-59 (build file generation fix related to locating
apr-binaries in httpd/srclib-directory)
    - MAXSVN-65 (test fixes due to drive-letter issue)
    - MAXSVN-93 (disabled patch-test #69)

Patches mentioned above can be downloaded here:
http://www.luke1410.de:8090/browse/MAXSVN-94?jql=project%20%3D%20MAXSVN%20AND%20%22Patch%20Version%2Fs%22%20%3D%201.10.0-alpha3-1

Tested
------
    - [fsfs | fsx] x [ra_local | ra_svn | ra_serf (http) | ra_serf
(https)] x [64-bit] x [release]

Results
-------
    General issues (i.e. issues not specific to my test/build environment):
    - several tests deadlock, when testing fsx (circumventing by
applying the patch for MAXSVN-94) - see
http://mail-archives.apache.org/mod_mbox/subversion-dev/201701.mbox/%3Cfc54e934-7135-18d5-84fa-8ec5695af3af%40gmx.de%3E

    Issues specific to my test/build environment:
    - Build error due to apr-detection issue on my environment
(circumventing by applying the patch for MAXSVN-59)- see
http://mail-archives.apache.org/mod_mbox/subversion-dev/201607.mbox/%3Ce9a90843-fc66-e0ea-0e94-75ab89eefbc2%40posteo.de%3E
    - patch-test #69 failure due to AV interruption (circumventing by
applying the patch for MAXSVN-93) - see
https://svn.haxx.se/dev/archive-2017-01/0075.shtml
    - checkout-test #14 and update-test #31 failure due to drive letter
issue (circumventing by applying the patch for MAXSVN-65) - see
http://mail-archives.apache.org/mod_mbox/subversion-dev/201607.mbox/%3Cf6f6e917-0b31-e87c-22e7-68cce2b601e9%40posteo.de%3E

Signatures
----------
subversion-1.10.0-rc2.tar.bz2:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJaxDBZAAoJEDdqPP0RCxyVH6cP/2R20gEtszNQ6fLliZjzuheY
Hm0wwZ5EgLMnyaqSMxjH2Sm/yCBHrY6k9tC+vxViv9k56X8iuucqyYjtRCxkQG5+
UfoyCSnoFcZcFoQ2YvEf0gqADBcB5Dnp+CtfQQaaYpN77/126A7X7l8Lm1yWlvN0
DQvqCtHCVnRjPVxqUDYX/ERl1bkvyJDhuAQcNnTK9B+y0q01CDJHEdWCbbNCFreE
fuhP2sTYvbJnEExNLVP/JDL/et34o/62rU0xD6qKpRxgEvBKxcYcG5E5ywhmm/Od
A1bHpZrUgZYHKqX61C5T3F+WxnTqyxowXdvbiNOK+svR/o73Ds+B7yjFGmvlFJW3
alDibtTIPPgwsUYPEUadp8AZtg4IFjmLnbSmMcE8eI0ob2/w4Y5EKhwafMmzKICw
bhR7fTbGC+36mcXLixY7+zj8sPjB3p9I94QMyWHzm5ozKNf2S1SnztaK2Xs5vZrY
3Y0ovR0Gzb9vEgjXkR8BQmTZzXjaJCQ1+hqgC9z1uwJN6vgRChzditGOUwUWmdye
9OZUs/n4Dy0hNZwLF3WgnZDTUpxJ/VS7/hoiwW+mGOjs31VzR/KtIR/s6r8k1KKA
WKmAMzLhDNvj6eIxhFDm35OvsX8FIVz1J42VoI4xG52htNN2MVq5oCWnN00hirY5
d34GDYJ95ezdluZPn/o+
=V7Zr
-----END PGP SIGNATURE-----

subversion-1.10.0-rc2.tar.gz:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJaxDBeAAoJEDdqPP0RCxyV2HIP/286nPjMv76kpHU9BugpXbL/
iN8AkoQDAaPz6hbtF7JE5/fybiVpDXXpPz+Bhs8KJ6SlkiSApgKT31B3uJmnuXLi
8a3qYCjtkPQi25Ra0j43ZCLk5+y73INtl/z5M5IqDAuWAXNELow2N02FGY6EDpR5
gh209g5um8/1R3K1m4nmNXGGWRAb2NtkAi44Rx+FmtQ5/8P+4d2JQS6O9lxs62G1
pglWOl6DzagQ6XJ2UegacXDTYWBCkPhrf45SCDJsvqNmvIDTDRNg6CLcH9Rb9ZZj
mtj3ODUU0s5kt8TOstAyJdUSFf96pYraDW5NAJ5d82m6LzoevRBDcGk58iQJjvRf
Q9iBZKblIe3xOxX7wAJYjp05H3g6+GuE/5bjVWQJEDfEygv9TcxH67WGVh7JK3KT
H/PVVDODzIm9IT9vUhKS3whEloU9wrWPnI64uoLjGe1/j1ncvuuB16irBHY3Bqaz
zviMTCnSFZekkIjRVEm4hQhkn4tEEiNo54L1JccOYLRpEt4l8IzCQZjtldTc6p6w
+AfDmuGcYqNKBgPPR6BlAsuNTovoy1UKFj54o9id0RcPGofUIrw3ukJ6ifitRtrD
IuIXbVio69D4+lO6EyHaVD6eD70MzPlvd01TSu5Zi4sugJ2k8r/NCXIVIBRVyub2
/MfGf0n9j0b36wqclbJS
=A2CX
-----END PGP SIGNATURE-----

subversion-1.10.0-rc2.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJaxDBfAAoJEDdqPP0RCxyVWOIQAIK8WFXbd0SysJMevEsjvYqS
l2DJlKE8m97NBamyy8pi+JuYuqRxuGtkJwgULrhzBBoA3X3iiStjnfoKlAROUlkF
ySrUTAiUf4KyNxjaajWIc86ib7MqgmXEtFoQZPXZqp4w6blYErno1MgF3MJM7PDg
Jlsuzc+vTS3CJIsU3Z7kkSQdjl7zD3ZjhyQdYhjVS3J1I5pCbloKeM1TLVrq4bfX
tF5nwe7KSezXkJMxvHhRxWblvhZyYBxAF//zpM4h91E6DJTOJ8g27ja4bZnfr7Ko
CrmiEuXIjGymoPjR9E2til3ErP+UgHhE3h1eOLh/McLBQ51dsc9Rnh2gRU03NxAS
IHE8Zc39OcCFgTsGIT+LTI0a9g2eLKYDTI6yixFjeqbsmPQyfh4P/Gih2+HrEEfN
QrsSK8joncW0/TCFJq6q2foEWy6gsiyphWAjeb12P/zhgGSAIlpQLghUGy4N3lj8
mwH4U7wt+GIJ6DaKfdmkgt4dkKUmm/H2+bG9i60KAOQCoIPW29bwoNhJyA/SQ7L0
dFtJ9GPRDbUKPF5HtB/PC+8nCiPEe/GXMtNdrKVSH3UCED301l39WqiaFz2cCabQ
9Icj/h83LygpBt8ZypKrxrYbfvfvgdtDG9CVLO9Q7W7q9c7PFxn8vGHZ/tQFty4O
VMJ5c89c8qj4zXHAwbuX
=obbI
-----END PGP SIGNATURE-----