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/07/14 20:55:02 UTC
Subversion 1.10.2 up for testing/signing
The 1.10.2 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.
Note that this is code-wise identical to 1.10.1; only the CHANGES file and COMMITTERS file are updated and version numbers changed.
Thanks!
- Julian
Re: Subversion 1.10.2 up for testing/signing
Posted by Branko Čibej <br...@apache.org>.
On 16.07.2018 08:08, Branko Čibej wrote:
> On 16.07.2018 00:46, Johan Corveleyn wrote:
>> On Sat, Jul 14, 2018 at 10:55 PM, Julian Foad <ju...@apache.org> wrote:
>>> The 1.10.2 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.
>>>
>>> Note that this is code-wise identical to 1.10.1; only the CHANGES file and COMMITTERS file are updated and version numbers changed.
>> I noticed that there is a difference that I didn't expect, in
>> subversion/include/svn_version.h, between the tarball and the 1.10.x
>> branch: on the branch SVN_VER_PATCH is still 0 (while it is 2 in the
>> tarball and in the tag). I don't think it's a big issue (the tarball
>> and tag are correct after all), but it's different from the 1.9
>> situation (in the 1.9.x branch SVN_VER_PATCH is 10 currently (and 9 in
>> 1.9.x@, as expected) and all previous releases.
>>
>> It seems something went wrong with the "Post-release housekeeping"
>> commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
>> (post 1.10.2): they contain an empty diff for svn_version.h ... weird.
>> Fortunately, the values in the tarball and tag are correct, so I don't
>> consider this a big issue right now ... I'm continuing tests ...
> This step is documented in HACKING, 'release.py create-tag' will bump
> the minor version on the release branch.
The last two revisions of release.py affect this area, but I haven't
looked at which one actually broke the version update ...
-- Brane
Re: Subversion 1.10.2 up for testing/signing
Posted by Branko Čibej <br...@apache.org>.
On 16.07.2018 00:46, Johan Corveleyn wrote:
> On Sat, Jul 14, 2018 at 10:55 PM, Julian Foad <ju...@apache.org> wrote:
>> The 1.10.2 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.
>>
>> Note that this is code-wise identical to 1.10.1; only the CHANGES file and COMMITTERS file are updated and version numbers changed.
> I noticed that there is a difference that I didn't expect, in
> subversion/include/svn_version.h, between the tarball and the 1.10.x
> branch: on the branch SVN_VER_PATCH is still 0 (while it is 2 in the
> tarball and in the tag). I don't think it's a big issue (the tarball
> and tag are correct after all), but it's different from the 1.9
> situation (in the 1.9.x branch SVN_VER_PATCH is 10 currently (and 9 in
> 1.9.x@, as expected) and all previous releases.
>
> It seems something went wrong with the "Post-release housekeeping"
> commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
> (post 1.10.2): they contain an empty diff for svn_version.h ... weird.
> Fortunately, the values in the tarball and tag are correct, so I don't
> consider this a big issue right now ... I'm continuing tests ...
This step is documented in HACKING, 'release.py create-tag' will bump
the minor version on the release branch.
-- Brane
Re: Subversion 1.10.2 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Mon, Jul 16, 2018 at 12:01 PM, Julian Foad <ju...@apache.org> wrote:
>>> Johan Corveleyn wrote:
>>>> It seems something went wrong with the "Post-release housekeeping"
>>>> commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
>>>> (post 1.10.2): they contain an empty diff for svn_version.h ... weird.
> [...]
>
> The 'release.py create-tag' didn't work properly because the patch version number found in the file wasn't what it expected, because I hadn't noticed it needed updating after the previous problem during rolling 1.10.0.
>
> I have fixed 'svn_version.h' manually in r1836006.
>
> I have improved 'release.py' in r1836007, r1836011, r1836012.
>
> Thanks for noticing!
Okay, perfect. Thanks for fixing :-).
--
Johan
Re: Subversion 1.10.2 up for testing/signing
Posted by Julian Foad <ju...@apache.org>.
>> Johan Corveleyn wrote:
>>> It seems something went wrong with the "Post-release housekeeping"
>>> commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
>>> (post 1.10.2): they contain an empty diff for svn_version.h ... weird.
[...]
The 'release.py create-tag' didn't work properly because the patch version number found in the file wasn't what it expected, because I hadn't noticed it needed updating after the previous problem during rolling 1.10.0.
I have fixed 'svn_version.h' manually in r1836006.
I have improved 'release.py' in r1836007, r1836011, r1836012.
Thanks for noticing!
--
- Julian
Re: Subversion 1.10.2 up for testing/signing
Posted by Julian Foad <ju...@apache.org>.
Daniel Shahaf wrote:
> Johan Corveleyn wrote on Mon, 16 Jul 2018 00:46 +0200:
> > It seems something went wrong with the "Post-release housekeeping"
> > commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
> > (post 1.10.2): they contain an empty diff for svn_version.h ... weird.
>
> An empty diff is the result of an 'svnmucc put' that didn't change the
> file. (As in, 'svn revert iota; svnmucc put iota iota')
>
> What happened is, in r1935935 STATUS said "Status of 1.10.2:" and
> svn_version.h said "#define SVN_VERSION_PATCH 0"; then release.py
> changed "2" to "3" on both of these lines. That effected the correct
> change to STATUS and no change to svn_version.h.
On releasing 1.10.0, 'release.py create-tag' failed to bump revisions on the branch [1] and so I fixed the 'STATUS' file manually in r1828869 to say '1.10.1', but I did not notice that 'svn_version.h' also should have been updated. So 'svn_version.h' remained at '1.10.0'.
> The thing is, replace_in_place() has a 'raise RuntimeError' statement
> designed to catch precisely this situation. I don't understand why it
> didn't fire.
>
> Julian, just to double check, you rolled 1.10.2 using the trunk version of
> release.py, right?
I used trunk 'release.py'. First I had to fix it [2], following that previous issue [1].
I will take a closer look now. (I'm online now, so we can discuss on IRC for a bit, until we have something definite to report here.)
[1] dev@ thread "release.py create-tag failed to update STATUS", 2018/04/11, https://lists.apache.org/thread.html/7bebefc47a85210df4b7624a4b6a5e55dc003240948a97e399934c2f@%3Cdev.subversion.apache.org%3E
[2] http://svn.apache.org/r1835936
--
- Julian
Re: Subversion 1.10.2 up for testing/signing
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Johan Corveleyn wrote on Mon, 16 Jul 2018 00:46 +0200:
> It seems something went wrong with the "Post-release housekeeping"
> commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
> (post 1.10.2): they contain an empty diff for svn_version.h ... weird.
An empty diff is the result of an 'svnmucc put' that didn't change the
file. (As in, 'svn revert iota; svnmucc put iota iota')
What happened is, in r1935935 STATUS said "Status of 1.10.2:" and
svn_version.h said "#define SVN_VERSION_PATCH 0"; then release.py
changed "2" to "3" on both of these lines. That effected the correct
change to STATUS and no change to svn_version.h.
The thing is, replace_in_place() has a 'raise RuntimeError' statement
designed to catch precisely this situation. I don't understand why it
didn't fire.
Julian, just to double check, you rolled 1.10.2 using the trunk version of
release.py, right?
Cheers,
Daniel
Re: Subversion 1.10.2 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Sat, Jul 14, 2018 at 10:55 PM, Julian Foad <ju...@apache.org> wrote:
> The 1.10.2 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.
>
> Note that this is code-wise identical to 1.10.1; only the CHANGES file and COMMITTERS file are updated and version numbers changed.
I noticed that there is a difference that I didn't expect, in
subversion/include/svn_version.h, between the tarball and the 1.10.x
branch: on the branch SVN_VER_PATCH is still 0 (while it is 2 in the
tarball and in the tag). I don't think it's a big issue (the tarball
and tag are correct after all), but it's different from the 1.9
situation (in the 1.9.x branch SVN_VER_PATCH is 10 currently (and 9 in
1.9.x@, as expected) and all previous releases.
It seems something went wrong with the "Post-release housekeeping"
commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
(post 1.10.2): they contain an empty diff for svn_version.h ... weird.
Fortunately, the values in the tarball and tag are correct, so I don't
consider this a big issue right now ... I'm continuing tests ...
--
Johan
Re: Subversion 1.10.2 up for testing/signing
Posted by Branko Čibej <br...@apache.org>.
Summary:
+1 to release (Windows)
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
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
GPG signatures committed to the dist/dev/subversion repository.
Re: Subversion 1.10.2 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Sat, Jul 14, 2018 at 10:55 PM, Julian Foad <ju...@apache.org> wrote:
> The 1.10.2 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.
>
> Note that this is code-wise identical to 1.10.1; only the CHANGES file and COMMITTERS file are updated and version numbers changed.
>
> Thanks!
> - Julian
Summary
-------
+1 to release
Platform
--------
Windows 7 SP1 (x64)
Microsoft Visual Studio 2017
Verified
--------
Signature, sha1 and sha512 for subversion-1.10.2.zip.
Contents of subversion-1.10.2.zip are identical to tags/1.10.2,
and to branches/1.10.x@1835932 (except for expected differences in
svn_version.h and svnpubsub, svnwcsub and nominate.pl (symlinks vs. file
contents), and generated files).
-- Except for subversion/include/svn_version.h, where the value of
SVN_VER_PATCH was not up to date in branches/1.10.x. This is not
a blocking issue (the value is correct in the tag and the tarball),
and was reported and discussed on dev@ (and fixed in the meantime).
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.2.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAABCgAGBQJbS8RiAAoJELWc5tYBDIqtHo4P/jCM3DfN1PS83EmYjo0eLlKC
nsEVTPRge+Rxh7VzEkU2WjHAJ/EwEyhLWsg1wia4mnNbRLg4NanGL4x8lx5lYkTe
AbdCXrOEADJ9HMAIhnE55pd7IpFKdYGC0WBQNaaoGQm+yYw0jToHs2hprdryIpCN
HLl8CQZUjV9/NBSSvdW11nV8Woz57Iwz847ECHB143xyNErS1gh2chZP9XFPK+KZ
Y1LfWmEt87RHzRKO7B2LJvTFIQh7a6s9RC4H4/Gwl1g37sLV9zolqVar3kGq+sJY
WsSAc/Cm15mFyUaL3YN3qPxaXRPHTtzm7g4YhZ1zBtmLhj2FUbrQG/Mh4tywtQyZ
jgHD1u+mar9mJYvtjudXSlJ8wLYi3wwk3EpPAUXnyaxTOianHM0XTmLLOtQKm81k
2NxHRRARiG2dBGEWRr7NUulPmKT6K4mdRu2ouyIbOm2OBlfXUh1k/xrJyBNV6ZeC
wElVapG1+GpfXU93/lt/Qc2xtoh6axP5AyyBDLVHR7Eze8+SKqFJfSMdohdYLHMt
mP+DBVUOf6F1sser53L/5i8V6nYqBs+ODm8ZHhHP5lcBgiID3IP/fkylMEKZtEbt
2MPgaEhgPlxTH78encjjb+YGG2CFmkNY1paHxVbtaVeAgv+7K33YmGFkbwYGcAIQ
yOkSqq+zrB7BooEPBmd4
=PTMU
-----END PGP SIGNATURE-----
--
Johan
Re: Subversion 1.10.2 up for testing/signing
Posted by Branko Čibej <br...@apache.org>.
Summary:
+1 to release (Unix)
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.
Platform
macOS High Sierra 10.13.6
Standard dependencies:
Apple LLVM version 9.1.0 (clang-902.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.34
SQLite 3.24.0
Serf 1.3.9
OpenSSL 1.0.2o
zlib 1.2.11
LZ4 1.8.2
utf8proc 2.1.1
BDB 18.1.25
Perl 5.28.0
Other dependencies:
Java 1.8.0_45-b14
JUnit 4.11
GPG signatures committed to the dist/dev/subversion repository.
Re: Subversion 1.10.2 up for testing/signing
Posted by Stefan <lu...@posteo.de>.
On 14/07/2018 22:55, Julian Foad wrote:
> The 1.10.2 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.
>
> Note that this is code-wise identical to 1.10.1; only the CHANGES file and COMMITTERS file are updated and version numbers changed.
>
> Thanks!
> - Julian
Post release signature.
Platform
--------
- Windows 10 (build 1803) 64-bit
- Visual Studio 2015 Update 3
- ActivePerl: 5.26.1.2601 (for OpenSSL)
- AWK: 20070501
- CMake 3.12.0 (for OpenSSL)
- NASM 2.13.03 (for OpenSSL)
- Python 2.7.15
- SCons 3.0.1 (for Apache Serf)
Verified
--------
subversion-1.10.2.tar.bz2:
Signature verified.
SHA-1: bc52ef2e671f821998ac9a5f7ebecbbcaaef83b8 (matches provided
SHA-1-checksum)
SHA-512:
ccbe860ec93a198745e40620cb7e005a85797e344a99ddbc0e24c32ad846976eae35cf5b3d62ba5751b998f0d40bbebbba72f484d92c92693bbb2112c989b129
(matches provided SHA-512-checksum)
subversion-1.10.2.tar.gz:
Signature verified.
SHA-1: 4c127b751c7804ec21a3942131467e721febc83f (matches provided
SHA-1-checksum)
SHA-512:
151f4596c756ddb616747905f6999b162547e2e4b588e02cbcab61f84e8767dcf747244198f11f2e9d22495c61c8b58d05666e1d138213be41981c5de4ccd1a8
(matches provided SHA-512-checksum)
subversion-1.10.2.zip:
Signature verified.
SHA-1: c85c11a21ac97e3734a7064b00ac962a2008e50a (matches provided
SHA-1-checksum)
SHA-512:
79cc2a2fb8b72f7839071641c3a30d0fc31070618e489608e4b9661eabc64b3b7c1a438d58b0c1bc244329120ffee3fd1ae688bbde9b69b88d7e794479620498
(matches provided SHA-512-checksum)
Contents of subversion-1.10.2.tar.bz2 equals contents of
subversion-1.10.2.tar.gz.
Contents of subversion-1.10.2.zip equals contents of
subversion-1.10.2.tar.bz2 with the expected differences:
- Windows vs. Linux line ending changes
- non-Windows-specific generated files missing in zip archive
- different paths in comments in generated header files
- differences related to symlinks in nominate.pl, svnpubsub, svnwcsub
Contents of subversion-1.10.2.zip equals contents of tags/1.10.2 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.5 (patched with MAXSVN-44,
MAXSVN-46, MAXSVN-47, MAXSVN-94, MAXSVN-120)
- 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.2o
- PCRE: 8.42
- SQLite: 3.24.0 (amalgamation)
- ZLib: 1.2.11
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-120?jql=project%20%3D%20MAXSVN%20AND%20%22Patch%20Version%2Fs%22%20%3D%201.10.2-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.2.tar.bz2:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIzBAABCAAdFiEEe4yn9kUa2JyK3Ad7N2o8/RELHJUFAltWUgkACgkQN2o8/REL
HJXcqA/7BIur5emjQExqbvEFf8AgG1MvK5U9MJbTCUxAJHjJ3cQqlLwxCu/jk8vC
KvcYwHhfVNMi4hlyStQTIbFCEjhrggq09IuT3biCZFoJHvu67wFSh1kO9rBFm+5p
YsMDL36+nctOLQQvSYN3yJRAz4vd3KA4mBmQr727Xo+WJIV7nlZl4mkquQftIdm3
DeFiIaV18mH05zv2XDAV6MAArW4gAbD4cpmrwvxLC5ODIHNcKLOA0LxtqilWlv8Q
BH+TnzIhqKmOgCgMWI59jsdhO/rUvR2bvS9PWTVJ/xrJUgauvyI+sN1CMoMHb78B
6lsZsC8aNkvAh2OrZaV0EgsOO4Wg6ayB2as8jganEpcetrkOBoBxK0//6uEQ0xjj
iFQoUwFukyOfZMzk2HIKOWD8+sAl9ao1uftHV1y2hfFrUbfG8R2W/+iezO2DDF4/
iOAcJAz/6/7pYjgvlft41Nfd8DhrELXtrdRK8RCFl9W2cXpZXcIZ/Anrj0g98K42
7nZ0VqkUoeVnb38SUPq3it0buIPbNQIDIUPhlAzICqmEQAU8U77qPBycwr0XA7DG
AZQjG3t0VoH9nrSprYJ1qVKfYf9oxKEaNolpd6c1+ncNLQq8FWycHFD0qIhR5NGU
0XHWIdlnEdLjpaJLBLd1WfFjXIAs5s5sUvJ28voX3U+rY7IV6Xs=
=fnwy
-----END PGP SIGNATURE-----
subversion-1.10.2.tar.gz:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIzBAABCAAdFiEEe4yn9kUa2JyK3Ad7N2o8/RELHJUFAltWUgkACgkQN2o8/REL
HJW6kg/+PHLtS7oQfcXwOdMXlkNFIqdjiX3eyE1unpGQxL7tYj010pv21E3uItr0
LR/F4i6lCuGKBF6rm2iI+FiWSSx0+2ejC+0KY/+j+WoYFZmOA5Ohfmc18Bc3yrtR
QS3gPh0eXj650EEO06oSu9c02zbZJN6OfjLl+EIbFZn2tUD2WW3iUuQ/k5BwkEZb
spnVz1hgBbv5H/qiUE9odOt5088hPprLkLUEImxK5R+xUUy26YX5nJJ0aoVG02t7
D4cAqGACfGPZnUoJ8R39LGzTGhcWdLlHNJItFAQDf7OzZR/hQ8EJwKYYRj5YbgF3
pteyNLRiVwrFTPKCxfx73geJrKCSTd8inh9q3yEalDiBGFKuAbHfAix1URyrNSwP
095bTxHrV3qdIpT8ZJ0RYG4Z8x6m62nd/RmH7jaUETghwEwKpz6WKOZm0RbRhOK/
TZ80mFyCkV7s/3Cch64Mm7+fQoP+HTTJKKIC5UT3B8KW3Q18+bxSs1gh5h2jsPIp
WTBX+KFIBqmmGcLSSkpBR+f8xjaT8h/hL/wxuSpLU1W0tLM2YqG0IGZpp71D0lvc
oVjhRQZ4GhEOuIPyzuCBUgx/T0jfrRWzZk97x8SS38yfUTqOb7hCIjLW2z2b44aL
qMPd8yNIX0+9j8PVyRcPyXev8nBmVAmst5sQOy9JsqaSPftNSi4=
=g71x
-----END PGP SIGNATURE-----
subversion-1.10.2.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIzBAABCAAdFiEEe4yn9kUa2JyK3Ad7N2o8/RELHJUFAltWUf4ACgkQN2o8/REL
HJVjrw//SeqSm4Iv9NyuP2GK+zpW9rpj2kpIMBcEcNGNfBgTpfL5GZXe2U8Ozffn
DKxswSCV+FP4VpLn2ZY3SC/EutPpfoFzngGG1gn+ShTst9fuZDjfOmX/xQObBAm0
D2poRC0zwgkLwW1najOvdmCxy91ursIWROUOr8ksNIIgy+PV1tj6FFEnJsgOmisB
BTtoSAaejveMm7TQ8xxVMqC7wr1Huuqm+JzYO3of6bX9Cu8b/NlGg8DgY0DS2cMD
yENMCASjP2fauFPeQMz5oSRw1Aj3eSWjIYqeQ2QSeqHNT2+gTjDADTFMPtwTPeQh
P4qPZKoqTg6VYdQSTat7ssMUSpNb7PMrs/JhWD7wZpmZxKjOeYYmwXkQDFzExVC5
BfKKhsCaH65ctXpqursQVnjGuXg1lHcEzu3+KI1SQBSTlXpOXLM+wwQO1vJa8fPp
0CGCq4qScqRunQrwKq5iOuzL/C+nfiHoT9QBConFhfzgdXK1vRjWjnFxMy0+8g+T
yvNiOYzEScNPPMmN5Dpe1a1a+4dSQEfBvgK6Jocv35vGP02o1oUkdmA3MQBxoMfz
ppjuj0iRuaG8OQxCeQHAAMLR+4CD6GH0xLLyMp3wL3bwj3rxuCi0rlPR7pSdXjw8
Zlqn749973SoUZdpTpMHryHnKYQH5mjXV5pN1R3clWmFXRDwm34=
=DKZZ
-----END PGP SIGNATURE-----
Regards,
Stefan