You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Stefan Sperling <st...@elego.de> on 2020/05/20 12:34:41 UTC

Subversion 1.14.0 up for testing/signing

The 1.14.0 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!

This release is essentially identical to 1.14.0-rc2 except for
the designation of the version. The full diff between 1.14.0-rc2
and 1.14.0 release artifacts is shown below.


diff -urN subversion-1.14.0-rc2/subversion/bindings/swig/perl/native/core.c subversion-1.14.0/subversion/bindings/swig/perl/native/core.c
--- subversion-1.14.0-rc2/subversion/bindings/swig/perl/native/core.c	Wed Apr  8 12:00:47 2020
+++ subversion-1.14.0/subversion/bindings/swig/perl/native/core.c	Wed May 20 14:21:00 2020
@@ -53178,12 +53178,12 @@
   } while(0) /*@SWIG@*/;
   /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
     SV *sv = get_sv((char*) SWIG_prefix "SVN_VER_TAG", TRUE | 0x2 | GV_ADDMULTI);
-    sv_setsv(sv, SWIG_FromCharPtr(" (Release Candidate 2)"));
+    sv_setsv(sv, SWIG_FromCharPtr(" (r1876290)"));
     SvREADONLY_on(sv);
   } while(0) /*@SWIG@*/;
   /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
     SV *sv = get_sv((char*) SWIG_prefix "SVN_VER_NUMTAG", TRUE | 0x2 | GV_ADDMULTI);
-    sv_setsv(sv, SWIG_FromCharPtr("-rc2"));
+    sv_setsv(sv, SWIG_FromCharPtr(""));
     SvREADONLY_on(sv);
   } while(0) /*@SWIG@*/;
   /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
@@ -53198,12 +53198,12 @@
   } while(0) /*@SWIG@*/;
   /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
     SV *sv = get_sv((char*) SWIG_prefix "SVN_VER_NUMBER", TRUE | 0x2 | GV_ADDMULTI);
-    sv_setsv(sv, SWIG_FromCharPtr("1.14.0-rc2"));
+    sv_setsv(sv, SWIG_FromCharPtr("1.14.0"));
     SvREADONLY_on(sv);
   } while(0) /*@SWIG@*/;
   /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
     SV *sv = get_sv((char*) SWIG_prefix "SVN_VERSION", TRUE | 0x2 | GV_ADDMULTI);
-    sv_setsv(sv, SWIG_FromCharPtr("1.14.0-rc2 (Release Candidate 2)"));
+    sv_setsv(sv, SWIG_FromCharPtr("1.14.0 (r1876290)"));
     SvREADONLY_on(sv);
   } while(0) /*@SWIG@*/;
   /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
diff -urN subversion-1.14.0-rc2/subversion/bindings/swig/python/core.c subversion-1.14.0/subversion/bindings/swig/python/core.c
--- subversion-1.14.0-rc2/subversion/bindings/swig/python/core.c	Wed Apr  8 12:00:07 2020
+++ subversion-1.14.0/subversion/bindings/swig/python/core.c	Wed May 20 14:20:22 2020
@@ -40645,12 +40645,12 @@
   SWIG_Python_SetConstant(d, "SVN_VER_PATCH",SWIG_From_long((long)(0)));
   SWIG_Python_SetConstant(d, "SVN_VER_MICRO",SWIG_From_long((long)(0)));
   SWIG_Python_SetConstant(d, "SVN_VER_LIBRARY",SWIG_From_long((long)(1)));
-  SWIG_Python_SetConstant(d, "SVN_VER_TAG",SWIG_FromCharPtr(" (Release Candidate 2)"));
-  SWIG_Python_SetConstant(d, "SVN_VER_NUMTAG",SWIG_FromCharPtr("-rc2"));
+  SWIG_Python_SetConstant(d, "SVN_VER_TAG",SWIG_FromCharPtr(" (r1876290)"));
+  SWIG_Python_SetConstant(d, "SVN_VER_NUMTAG",SWIG_FromCharPtr(""));
   SWIG_Python_SetConstant(d, "SVN_VER_REVISION",SWIG_From_long((long)(1876290)));
   SWIG_Python_SetConstant(d, "SVN_VER_NUM",SWIG_FromCharPtr("1.14.0"));
-  SWIG_Python_SetConstant(d, "SVN_VER_NUMBER",SWIG_FromCharPtr("1.14.0-rc2"));
-  SWIG_Python_SetConstant(d, "SVN_VERSION",SWIG_FromCharPtr("1.14.0-rc2 (Release Candidate 2)"));
+  SWIG_Python_SetConstant(d, "SVN_VER_NUMBER",SWIG_FromCharPtr("1.14.0"));
+  SWIG_Python_SetConstant(d, "SVN_VERSION",SWIG_FromCharPtr("1.14.0 (r1876290)"));
   SWIG_Python_SetConstant(d, "svn_prop_entry_kind",SWIG_From_long((long)(svn_prop_entry_kind)));
   SWIG_Python_SetConstant(d, "svn_prop_wc_kind",SWIG_From_long((long)(svn_prop_wc_kind)));
   SWIG_Python_SetConstant(d, "svn_prop_regular_kind",SWIG_From_long((long)(svn_prop_regular_kind)));
diff -urN subversion-1.14.0-rc2/subversion/bindings/swig/ruby/core.c subversion-1.14.0/subversion/bindings/swig/ruby/core.c
--- subversion-1.14.0-rc2/subversion/bindings/swig/ruby/core.c	Wed Apr  8 12:01:19 2020
+++ subversion-1.14.0/subversion/bindings/swig/ruby/core.c	Wed May 20 14:21:29 2020
@@ -46747,12 +46747,12 @@
   rb_define_const(mCore, "SVN_VER_PATCH", SWIG_From_int((int)(0)));
   rb_define_const(mCore, "SVN_VER_MICRO", SWIG_From_int((int)(0)));
   rb_define_const(mCore, "SVN_VER_LIBRARY", SWIG_From_int((int)(1)));
-  rb_define_const(mCore, "SVN_VER_TAG", SWIG_FromCharPtr(" (Release Candidate 2)"));
-  rb_define_const(mCore, "SVN_VER_NUMTAG", SWIG_FromCharPtr("-rc2"));
+  rb_define_const(mCore, "SVN_VER_TAG", SWIG_FromCharPtr(" (r1876290)"));
+  rb_define_const(mCore, "SVN_VER_NUMTAG", SWIG_FromCharPtr(""));
   rb_define_const(mCore, "SVN_VER_REVISION", SWIG_From_int((int)(1876290)));
   rb_define_const(mCore, "SVN_VER_NUM", SWIG_FromCharPtr("1.14.0"));
-  rb_define_const(mCore, "SVN_VER_NUMBER", SWIG_FromCharPtr("1.14.0-rc2"));
-  rb_define_const(mCore, "SVN_VERSION", SWIG_FromCharPtr("1.14.0-rc2 (Release Candidate 2)"));
+  rb_define_const(mCore, "SVN_VER_NUMBER", SWIG_FromCharPtr("1.14.0"));
+  rb_define_const(mCore, "SVN_VERSION", SWIG_FromCharPtr("1.14.0 (r1876290)"));
   
   SwigClassSvn_version_t.klass = rb_define_class_under(mCore, "Svn_version_t", rb_cObject);
   SWIG_TypeClientData(SWIGTYPE_p_svn_version_t, (void *) &SwigClassSvn_version_t);
diff -urN subversion-1.14.0-rc2/subversion/include/svn_version.h subversion-1.14.0/subversion/include/svn_version.h
--- subversion-1.14.0-rc2/subversion/include/svn_version.h	Wed Apr  8 11:59:11 2020
+++ subversion-1.14.0/subversion/include/svn_version.h	Wed May 20 14:19:40 2020
@@ -93,7 +93,7 @@
  *
  * Always change this at the same time as SVN_VER_NUMTAG.
  */
-#define SVN_VER_TAG        " (Release Candidate 2)"
+#define SVN_VER_TAG        " (r1876290)"
 
 
 /** Number tag: a string describing the version.
@@ -108,7 +108,7 @@
  *
  * Always change this at the same time as SVN_VER_TAG.
  */
-#define SVN_VER_NUMTAG     "-rc2"
+#define SVN_VER_NUMTAG     ""
 
 
 /** Revision number: The repository revision number of this release.
diff -urN subversion-1.14.0-rc2/subversion/po/subversion.pot subversion-1.14.0/subversion/po/subversion.pot
--- subversion-1.14.0-rc2/subversion/po/subversion.pot	Wed Apr  8 11:59:41 2020
+++ subversion-1.14.0/subversion/po/subversion.pot	Wed May 20 14:19:56 2020
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: dev@subversion.apache.org\n"
-"POT-Creation-Date: 2020-04-08 09:59+0000\n"
+"POT-Creation-Date: 2020-05-20 12:19+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EM...@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL...@li.org>\n"

Re: Subversion 1.14.0 up for testing/signing

Posted by James McCoy <ja...@jamessan.com>.
On Wed, May 20, 2020 at 02:34:41PM +0200, Stefan Sperling wrote:
> The 1.14.0 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!
> 
> This release is essentially identical to 1.14.0-rc2 except for
> the designation of the version. The full diff between 1.14.0-rc2
> and 1.14.0 release artifacts is shown below.

Confirmed diff and committed my signatures. +1 to release.

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

Re: Subversion 1.14.0 up for testing/signing

Posted by Johan Corveleyn <jc...@gmail.com>.
On Tue, May 26, 2020 at 11:06 AM Johan Corveleyn <jc...@gmail.com> wrote:
>
> On Wed, May 20, 2020 at 2:35 PM Stefan Sperling <st...@elego.de> wrote:
> >
> > The 1.14.0 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.
>
> Summary
> -------
> +1 to release (Windows)
>
> Platform
> --------
> Windows 10 x64 (Version 1903)
> Microsoft Visual Studio 2019 Community Edition (Version 16.5.3)
>
> Verified
> --------
> Signature and sha512 for subversion-1.14.0.zip.
>
> Contents of subversion-1.14.0.zip are identical to tags/1.14.0,
> and to branches/1.14.x@1876290 (except for expected differences in
> svn_version.h and svnpubsub, svnwcsub and nominate.pl (symlinks vs. file
> contents), and generated files).
>
> Tested
> ------
> [ Release build x64 ] x [ fsfs ] x [ file | svn | http ]
> javahl
> swig-python
>
> I applied the following fixes for known testsuite and (swig-)building issues:
>
> Merged from trunk, for building swig-python bindings with swig 4:
> - r1877338 (Fix differences of SWIG_PY_OPTS between Unix and Windows.
>             Enable building with Swig 4)
>
> Merged from trunk, testsuite fixes for running the testsuite with Python 3:
> - r1876707 (Escape special characters in path when construct expected
> output regex.)
> - r1876734 (subversion/tests/cmdline/blame_tests.py (blame_youngest_to_oldest):
>             Use svntest.main.file_write to avoid end of line conversion.)
> - r1877318 (Fix svnrdump tests on Windows with Python 3)
> - r1877712 (entries-dump: Escape string-typed attribute values when serializing
>             them as Python string literals.)
>
> Applied following testsuite patches for running the testsuite with Python 3:
> - py38-windows-add-dll-directory--v2.diff posted by jun66j5 on
> 2020-05-11 in dev@ thread
>   "[PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows"
> - sain_keep_eol_style_win_patch_20200506.txt,
>       fix_svnadmin_tests_patch.txt,
>       fix_svndumpfilter_tests_patch.txt
>   posted by futatuki on 2020-05-06 in dev@ thread
>   "Problems running testsuite on Windows with Python 3"
> - Patch remove-uses-of-os-dup2.diff posted by jun66j5 on 2020-05-08 in
> dev@ thread
>   "Problems running testsuite on Windows with Python 3"
> - Patch fix-entries-dump-patch.txt posted by futatuki on 2020-05-26 in
> dev@ thread
>   "One more issue in tests on Windows with Python 3"
>
> Results
> -------
> All tests pass.
>
> Dependencies
> ------------
> Httpd 2.4.43 (apr 1.6.5, apr-util 1.6.1,
>               pcre 8.44, expat 2.2.9, openssl 1.1.1g)
> Apr 1.6.5
> Apr-Util 1.6.1
> OpenSSL 1.1.1g
> Serf 1.3.9
> SQLite 3.31.1.0
> ZLib 1.2.11
> (bundled lz4 1.7.5)
> (bundled utf8proc 2.1.0)
>
> Other tools
> -----------
> Perl 5.30.2 (Strawberry Perl)
> Python 3.8.2
> AdoptOpenJDK 11.0.6
> JUnit 4.12

Forgot to add:
Swig 4.0.1

-- 
Johan

Re: Subversion 1.14.0 up for testing/signing

Posted by Johan Corveleyn <jc...@gmail.com>.
On Wed, May 27, 2020 at 4:53 PM Johan Corveleyn <jc...@gmail.com> wrote:
>
> On Wed, May 27, 2020 at 4:43 PM Nathan Hartman <ha...@gmail.com> wrote:
> >
> > On Tue, May 26, 2020 at 10:02 PM Yasuhito FUTATSUKI <fu...@poem.co.jp> wrote:
> > > >> Should any of these be added to https://subversion.apache.org/docs/release-notes/1.14#issues ?
> > > >
> > > > Yes, all of them I think.
> > > > I thought first to wait whether we can still commit some / most of
> > > > them, and nominate for backport. It's easier to refer to revisions
> > > > than to patches. But OTOH we don't necessarily have to wait for that.
> > >
> > > Now I commited all my patches in above list, and nominated for back port,
> > > as a test suite fix group of patches (all my commit of my patch above
> > > are in this group).
> >
> > Were there any patches by Jun that still need to be committed /
> > nominated for backport?
> >
> > Nathan
>
> Yes, these two patches are really also needed:
>
> > > - py38-windows-add-dll-directory--v2.diff posted by jun66j5 on 2020-05-11 in dev@ thread
> > >   "[PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows"
>
> (or a variation thereof ... I see that several patches were posted in
> that thread, I'm not sure anymore which is which :-))
>
> > > - Patch remove-uses-of-os-dup2.diff posted by jun66j5 on 2020-05-08 in dev@ thread
> > >   "Problems running testsuite on Windows with Python 3"
>
> (without this one, our python tests refuse to run if you start the
> testsuite without --log-to-stdout, unless you set the
> PYTHONLEGACYWINDOWSSTDIO envvar -- we can always mention this as a
> workaround though).
>
> I'd like to leave the honor to Jun to commit them :-).

Ping.

Jun, the above two patches seem quite important for running our
testsuite on Windows with Python 3.
It would be nice if you could commit them yourself, and nominate them
for backport to 1.14.x.

(perhaps there are also others, I might have missed something)

Thanks,
-- 
Johan

Re: Subversion 1.14.0 up for testing/signing

Posted by Johan Corveleyn <jc...@gmail.com>.
On Wed, May 27, 2020 at 4:43 PM Nathan Hartman <ha...@gmail.com> wrote:
>
> On Tue, May 26, 2020 at 10:02 PM Yasuhito FUTATSUKI <fu...@poem.co.jp> wrote:
> > >> Should any of these be added to https://subversion.apache.org/docs/release-notes/1.14#issues ?
> > >
> > > Yes, all of them I think.
> > > I thought first to wait whether we can still commit some / most of
> > > them, and nominate for backport. It's easier to refer to revisions
> > > than to patches. But OTOH we don't necessarily have to wait for that.
> >
> > Now I commited all my patches in above list, and nominated for back port,
> > as a test suite fix group of patches (all my commit of my patch above
> > are in this group).
>
> Were there any patches by Jun that still need to be committed /
> nominated for backport?
>
> Nathan

Yes, these two patches are really also needed:

> > - py38-windows-add-dll-directory--v2.diff posted by jun66j5 on 2020-05-11 in dev@ thread
> >   "[PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows"

(or a variation thereof ... I see that several patches were posted in
that thread, I'm not sure anymore which is which :-))

> > - Patch remove-uses-of-os-dup2.diff posted by jun66j5 on 2020-05-08 in dev@ thread
> >   "Problems running testsuite on Windows with Python 3"

(without this one, our python tests refuse to run if you start the
testsuite without --log-to-stdout, unless you set the
PYTHONLEGACYWINDOWSSTDIO envvar -- we can always mention this as a
workaround though).

I'd like to leave the honor to Jun to commit them :-).

Of course it would be best for clarity of our release notes that you
could refer to proper revisions, if possible. So I'm not sure how long
you can wait for that, or that you should already include a reference
to the patches as "wip" ...

--
Johan

Re: Subversion 1.14.0 up for testing/signing

Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, May 26, 2020 at 10:02 PM Yasuhito FUTATSUKI <fu...@poem.co.jp> wrote:
> >> Should any of these be added to https://subversion.apache.org/docs/release-notes/1.14#issues ?
> >
> > Yes, all of them I think.
> > I thought first to wait whether we can still commit some / most of
> > them, and nominate for backport. It's easier to refer to revisions
> > than to patches. But OTOH we don't necessarily have to wait for that.
>
> Now I commited all my patches in above list, and nominated for back port,
> as a test suite fix group of patches (all my commit of my patch above
> are in this group).

Were there any patches by Jun that still need to be committed /
nominated for backport?

Nathan

Re: Subversion 1.14.0 up for testing/signing

Posted by Yasuhito FUTATSUKI <fu...@poem.co.jp>.
On 2020/05/27 4:04, Johan Corveleyn wrote:
> On Tue, May 26, 2020 at 8:42 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>>
>> Johan Corveleyn wrote on Tue, 26 May 2020 11:06 +0200:
>>> I applied the following fixes for known testsuite and (swig-)building issues:
>>>
>>> Merged from trunk, for building swig-python bindings with swig 4:
>>> - r1877338 (Fix differences of SWIG_PY_OPTS between Unix and Windows.
>>>             Enable building with Swig 4)
>>>
>>> Merged from trunk, testsuite fixes for running the testsuite with Python 3:
>>> - r1876707 (Escape special characters in path when construct expected
>>> output regex.)
>>> - r1876734 (subversion/tests/cmdline/blame_tests.py (blame_youngest_to_oldest):
>>>             Use svntest.main.file_write to avoid end of line conversion.)
>>> - r1877318 (Fix svnrdump tests on Windows with Python 3)
>>> - r1877712 (entries-dump: Escape string-typed attribute values when serializing
>>>             them as Python string literals.)
>>>
>>> Applied following testsuite patches for running the testsuite with Python 3:
>>> - py38-windows-add-dll-directory--v2.diff posted by jun66j5 on 2020-05-11 in dev@ thread
>>>   "[PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows"
>>> - sain_keep_eol_style_win_patch_20200506.txt,
          -> r1878142

>>>       fix_svnadmin_tests_patch.txt,
          -> r1878143

>>>       fix_svndumpfilter_tests_patch.txt
          -> r1878144

>>>   posted by futatuki on 2020-05-06 in dev@ thread
>>>   "Problems running testsuite on Windows with Python 3"
>>> - Patch remove-uses-of-os-dup2.diff posted by jun66j5 on 2020-05-08 in dev@ thread
>>>   "Problems running testsuite on Windows with Python 3"
>>> - Patch fix-entries-dump-patch.txt posted by futatuki on 2020-05-26 in dev@ thread
>>>   "One more issue in tests on Windows with Python 3"
      -> r1878141
>>
>> Should any of these be added to https://subversion.apache.org/docs/release-notes/1.14#issues ?
> 
> Yes, all of them I think.
> I thought first to wait whether we can still commit some / most of
> them, and nominate for backport. It's easier to refer to revisions
> than to patches. But OTOH we don't necessarily have to wait for that.

Now I commited all my patches in above list, and nominated for back port,
as a test suite fix group of patches (all my commit of my patch above
are in this group).

Cheers,
-- 
Yasuhito FUTATSUKI <fu...@yf.bsdclub.org>

Re: Subversion 1.14.0 up for testing/signing

Posted by Johan Corveleyn <jc...@gmail.com>.
On Tue, May 26, 2020 at 8:42 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>
> Johan Corveleyn wrote on Tue, 26 May 2020 11:06 +0200:
> > I applied the following fixes for known testsuite and (swig-)building issues:
> >
> > Merged from trunk, for building swig-python bindings with swig 4:
> > - r1877338 (Fix differences of SWIG_PY_OPTS between Unix and Windows.
> >             Enable building with Swig 4)
> >
> > Merged from trunk, testsuite fixes for running the testsuite with Python 3:
> > - r1876707 (Escape special characters in path when construct expected
> > output regex.)
> > - r1876734 (subversion/tests/cmdline/blame_tests.py (blame_youngest_to_oldest):
> >             Use svntest.main.file_write to avoid end of line conversion.)
> > - r1877318 (Fix svnrdump tests on Windows with Python 3)
> > - r1877712 (entries-dump: Escape string-typed attribute values when serializing
> >             them as Python string literals.)
> >
> > Applied following testsuite patches for running the testsuite with Python 3:
> > - py38-windows-add-dll-directory--v2.diff posted by jun66j5 on 2020-05-11 in dev@ thread
> >   "[PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows"
> > - sain_keep_eol_style_win_patch_20200506.txt,
> >       fix_svnadmin_tests_patch.txt,
> >       fix_svndumpfilter_tests_patch.txt
> >   posted by futatuki on 2020-05-06 in dev@ thread
> >   "Problems running testsuite on Windows with Python 3"
> > - Patch remove-uses-of-os-dup2.diff posted by jun66j5 on 2020-05-08 in dev@ thread
> >   "Problems running testsuite on Windows with Python 3"
> > - Patch fix-entries-dump-patch.txt posted by futatuki on 2020-05-26 in dev@ thread
> >   "One more issue in tests on Windows with Python 3"
>
> Should any of these be added to https://subversion.apache.org/docs/release-notes/1.14#issues ?

Yes, all of them I think.
I thought first to wait whether we can still commit some / most of
them, and nominate for backport. It's easier to refer to revisions
than to patches. But OTOH we don't necessarily have to wait for that.

-- 
Johan

Re: Subversion 1.14.0 up for testing/signing

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Johan Corveleyn wrote on Tue, 26 May 2020 11:06 +0200:
> I applied the following fixes for known testsuite and (swig-)building issues:
> 
> Merged from trunk, for building swig-python bindings with swig 4:
> - r1877338 (Fix differences of SWIG_PY_OPTS between Unix and Windows.
>             Enable building with Swig 4)
> 
> Merged from trunk, testsuite fixes for running the testsuite with Python 3:
> - r1876707 (Escape special characters in path when construct expected
> output regex.)
> - r1876734 (subversion/tests/cmdline/blame_tests.py (blame_youngest_to_oldest):
>             Use svntest.main.file_write to avoid end of line conversion.)
> - r1877318 (Fix svnrdump tests on Windows with Python 3)
> - r1877712 (entries-dump: Escape string-typed attribute values when serializing
>             them as Python string literals.)
> 
> Applied following testsuite patches for running the testsuite with Python 3:
> - py38-windows-add-dll-directory--v2.diff posted by jun66j5 on 2020-05-11 in dev@ thread
>   "[PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows"
> - sain_keep_eol_style_win_patch_20200506.txt,
>       fix_svnadmin_tests_patch.txt,
>       fix_svndumpfilter_tests_patch.txt
>   posted by futatuki on 2020-05-06 in dev@ thread
>   "Problems running testsuite on Windows with Python 3"
> - Patch remove-uses-of-os-dup2.diff posted by jun66j5 on 2020-05-08 in dev@ thread
>   "Problems running testsuite on Windows with Python 3"
> - Patch fix-entries-dump-patch.txt posted by futatuki on 2020-05-26 in dev@ thread
>   "One more issue in tests on Windows with Python 3"

Should any of these be added to https://subversion.apache.org/docs/release-notes/1.14#issues ?

Re: Subversion 1.14.0 up for testing/signing

Posted by Johan Corveleyn <jc...@gmail.com>.
On Wed, May 20, 2020 at 2:35 PM Stefan Sperling <st...@elego.de> wrote:
>
> The 1.14.0 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.

Summary
-------
+1 to release (Windows)

Platform
--------
Windows 10 x64 (Version 1903)
Microsoft Visual Studio 2019 Community Edition (Version 16.5.3)

Verified
--------
Signature and sha512 for subversion-1.14.0.zip.

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

Tested
------
[ Release build x64 ] x [ fsfs ] x [ file | svn | http ]
javahl
swig-python

I applied the following fixes for known testsuite and (swig-)building issues:

Merged from trunk, for building swig-python bindings with swig 4:
- r1877338 (Fix differences of SWIG_PY_OPTS between Unix and Windows.
            Enable building with Swig 4)

Merged from trunk, testsuite fixes for running the testsuite with Python 3:
- r1876707 (Escape special characters in path when construct expected
output regex.)
- r1876734 (subversion/tests/cmdline/blame_tests.py (blame_youngest_to_oldest):
            Use svntest.main.file_write to avoid end of line conversion.)
- r1877318 (Fix svnrdump tests on Windows with Python 3)
- r1877712 (entries-dump: Escape string-typed attribute values when serializing
            them as Python string literals.)

Applied following testsuite patches for running the testsuite with Python 3:
- py38-windows-add-dll-directory--v2.diff posted by jun66j5 on
2020-05-11 in dev@ thread
  "[PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows"
- sain_keep_eol_style_win_patch_20200506.txt,
      fix_svnadmin_tests_patch.txt,
      fix_svndumpfilter_tests_patch.txt
  posted by futatuki on 2020-05-06 in dev@ thread
  "Problems running testsuite on Windows with Python 3"
- Patch remove-uses-of-os-dup2.diff posted by jun66j5 on 2020-05-08 in
dev@ thread
  "Problems running testsuite on Windows with Python 3"
- Patch fix-entries-dump-patch.txt posted by futatuki on 2020-05-26 in
dev@ thread
  "One more issue in tests on Windows with Python 3"

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

Dependencies
------------
Httpd 2.4.43 (apr 1.6.5, apr-util 1.6.1,
              pcre 8.44, expat 2.2.9, openssl 1.1.1g)
Apr 1.6.5
Apr-Util 1.6.1
OpenSSL 1.1.1g
Serf 1.3.9
SQLite 3.31.1.0
ZLib 1.2.11
(bundled lz4 1.7.5)
(bundled utf8proc 2.1.0)

Other tools
-----------
Perl 5.30.2 (Strawberry Perl)
Python 3.8.2
AdoptOpenJDK 11.0.6
JUnit 4.12

Signature
---------

subversion-1.14.0.zip:
-----BEGIN PGP SIGNATURE-----

iQIcBAABCgAGBQJezDDpAAoJELWc5tYBDIqt1OoQALlgOq97zfzRTnGROVdRPe2b
L9/jNnwwZ0ceVWYzrr4lGZUXDSfkA/Q2l86FXEBZFb9CP+B45a8AUG4bQL4cmz1C
88/QrxR2cOLkRp94Vq5l35Vn4brMQCGxXvV13j7q0G9Oi47DYzmUuS3na/4+olZh
/axf4kBXo2DyEEs5Ng8zqNgbdBgHqUUQEWQ2sR0F8lWZqQmA9tyGsTsWbgs26C+c
COUTBVLVUJnGxEVN3sMXPlQfXURjZquUqcWbkL7455JWleuXg/WuoHRc5YbFIHLU
9zL9n5OuF37JcedUIy0Rkh9kI9jq/O6QQIIPX9HMPEjUDqsJo48O6NjXe4FLp+Qg
ABy9RvmHLBWHkujIpyJkMfrcdi6oYnqqOg9NHN+46l74Px5m9NXnaDOim1YVxad4
I9L34oFtNa3Af/oN1p3DP4PA42/L4woCw0if+rfsDq40ZxPRsjHzA/ja6scbO5A1
pSdE+Gwde/j2uYCx2m0EtGkRcPu/n5mHKNt2t7LjaTtmqQ8SKBHY1KHmu9je8sfh
+xSYW80C0vp8zctbsfObolipugCIZvO4hr0uzpbRkttckqqmdNPsGbSrtXIXjhp2
TnirWMJfVtQCLPOzkFccOo44AIoTZq364oSMD/8Ph1qZMhrqykNp6K08dKrCTMVW
5uqPs3pMDItAib1HSPaW
=vs0u
-----END PGP SIGNATURE-----



--
Johan

Re: Subversion 1.14.0 up for testing/signing

Posted by Julian Foad <ju...@apache.org>.
Stefan Sperling wrote:
> The 1.14.0 release artifacts are now available for testing/signing.

+1 for release (Unix).

Tested on Ubuntu 18.04:
   (serf, ra-svn, ra-local) x (fsfs, bdb)
   javahl
   swig-py, swig-pl, swig-rb

Note: could not get ctypes-python bindings tests to work. Signing 
despite this, on the understanding that these are already known to be 
deficient.

- Julian

Re: Subversion 1.14.0 up for testing/signing

Posted by Branko Čibej <br...@apache.org>.
On 20.05.2020 14:34, Stefan Sperling wrote:
> The 1.14.0 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!
>
> This release is essentially identical to 1.14.0-rc2 except for
> the designation of the version. The full diff between 1.14.0-rc2
> and 1.14.0 release artifacts is shown below.


+1 to release. I checked the diff from -rc2 and committed my signatures
to the repository.

-- Brane

Re: Subversion 1.14.0 up for testing/signing

Posted by Branko Čibej <br...@apache.org>.
On 26.05.2020 12:16, Stefan Sperling wrote:
> On Wed, May 20, 2020 at 02:34:41PM +0200, Stefan Sperling wrote:
>> The 1.14.0 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!
> The current 1.14.0 signature count is 1x windows and 2x unix.
>
> I was planning to release tomorrow, one week after posting the tarballs
> for signing. Is anyone still planning to add their signature?
>
> Note that you do not strictly need to re-test, since the tarballs are
> identical to -r2, as shown below.

I'm in the middle of doing my own diffs on the release tarballs, give me
an hour or so.

-- Brane

Re: Subversion 1.14.0 up for testing/signing

Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, May 26, 2020 at 6:36 AM Branko Čibej <br...@apache.org> wrote:

> You're guessing correctly. Natahan? I predict you have a draft mail
> prepared somewhere. :)


Yes. :-)

Summary: +1 to release (unix)

Platform: Debian "Buster" Linux 4.19.0-8-rt-amd64 x86_64

Tested: [fsfs] x [ra_local | ra_svn | ra_serf]
        swig bindings (ruby, python, perl)

Test results: All passed.

Verified signatures and sha512 sums match:
* subversion-1.14.0-rc2.tar.bz2
* subversion-1.14.0-rc2.tar.gz

Verified tarball and tag contents:
* Contents of subversion-1.14.0.tar.{gz,bz2} are identical to those of
  subversion-1.14.0-rc2.tar.{gz,bz2} except expected differences
  (re-branding).
* Contents of 1.14.0 tag match contents of 1.14.0-rc2 tag except
  expected differences ($HeadURL$, SVN_VER_TAG, SVN_VER_NUMTAG).
* Contents of subversion-1.14.0.tar.{gz,bz2} match contents of 1.14.0
  tag except expected differences (generated files, $HeadURL$).

Notes:
* I did not test bdb this time. However, I did test bdb against all
  ra for 1.14.0-rc2 on 10 Apr 2020 and all tests passed. The bdb
  backend is deprecated and is not recommended for new repositories.
* I did not test ctypes-python bindings.
* I don't have the setup to test JavaHL.

Dependencies:
bdb:        18.1.32
bzip2:      1.0.6
gettext:    0.19.8.1
GNU-iconv:  1.15
apr:        1.5.2
apr-util:   1.5.4
httpd:      2.4.37
serf:       1.4.x
cyrus-sasl: 2.1.27
sqlite:     3160200
lz4:        1.7.5
libssl:     OpenSSL 1.1.1d  10 Sep 2019
swig:       3.0.12
py3c:       1.1
python:     3.7.5
perl:       5.28.1
ruby:       2.4.4

Signatures:

subversion-1.14.0.tar.gz:
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEP45GfLM2bjAT4RINWD8ArfmBw58FAl7G0AIACgkQWD8ArfmB
w59vsw//X7fTWsWhoBPNlIN1kYB4SaN4oU098wigzpyCwPNxQeFsSuhdMEqzJeRb
XQm8HS1OKCyQ/H4ar/Q2xRHK448HuxWe4CcTyLiEaleGGj4HVw2ICcSdQTeZybG7
nBInHjyCnkaOw1c8uEa7fhdJr4/nsmBUwDGqlKCXtCZE8FGwlnzy5TLHt36AQXno
gzx1cM8UUlQEVTpA9lgZlu98Y76UbkIIDkvqkgJ+RVcoojMEGKLEhbjusOtxbmfa
eGiP881xBzl022DWPXAyeIT2b8rUY7nTRk4BOBypRfTWGvT1zmfVZC/Pv7Wj+GqW
OCFEINKCsOpRfeA6TYUgW3pmw2oj1R0KSy1hXnIuSikT0gUyWOthHicsbEfcVlIo
w8VXK498JkIP6NDIci6yE1EUEMCjXcHpEq0S8uhmuPkjhMLb/rNtKRqjN9jBNj8j
QRXv5G0eD9Zc0i09VcUxO7yJAdQFjPE2ktRoBIt2FGBr/TnH5MzImIlwqYA1CYuw
umCnTAa+SUkUkRWq4glnb5IGSkJsQuChhFpLzqZmWe9v2jYQ8ZNMtj2hvgnwdPEg
9oMIJaMJn3I6jyl61FSfTUhT82JbS4O1YrSPivIwJPV/hBxksuG99/zGJbds6Rbs
TNPwASj86xDjbVLeLkVmsyVhuPQeO+8m2D5ytvGj8iAtkRH1aLM=
=o87d
-----END PGP SIGNATURE-----

subversion-1.14.0.tar.bz2:
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEP45GfLM2bjAT4RINWD8ArfmBw58FAl7Gz/0ACgkQWD8ArfmB
w5/Wnw/+LfYn2xtWm2bVj31xBplaffGmqkVozOQsPeUq646TXonbbGjtgPoXgc6+
IxGf9f0Tuob9KhmCStcTMYOMAnStZI/pC19mMZ4ei6S9qcnbJFXB+Ph+5JUWpmuk
UrgNsn/V+icFOkL1v50J0m+WrJIm+36wJe2CLw4VEdPGO+8GIUycGUuDEnJUz9vt
srGRWoj2FQbVLPqIzuGcgFquU3ct0zpVgoAYSpNMk7dUcwY15EszU2l1V43FJPG0
praRulvy5SZFltLqNdNH8xEWpOraDoZmKdatrObCfsTO6xMvOdKpNba7W7PRZei1
Q9CdaSigQlEEjXAUX/Vn4ZjEGwMND564NJ5IXfMQ/c4MNLCZNtE6aWR80xALCGmQ
i7bJSlIPbKsVkJpN5nkiBma3cypUreyegxGnxuUUnDRbZkAGs+LQh2JiRtNOBu2t
q3ZN+N6pdLn984IdsGpDLvt4O0L54wpRtobeDtWLmc6o9E+kZmqQBcj0pGV0bmxc
+z/qH3oPYOuN9Ehiyll9eS7pZHGGtzbL7V/hxuwJ2PTh5W1Rcg+mhg9lpFCfr9+H
2teIUbfxRlyTiIZ4/0CvuM/PIVvdQdIh1fQWpYtYHEXSjc7Q9QzHrCGF1O2UceAj
5oU4lT90mJ0a6sOA+h17cTz90RvqsCVQG2d7Y0iE4ENMGIAoiRQ=
=I97x
-----END PGP SIGNATURE-----

Cheers,
Nathan

Re: Subversion 1.14.0 up for testing/signing

Posted by Branko Čibej <br...@apache.org>.
On 26.05.2020 12:34, Johan Corveleyn wrote:
> On Tue, May 26, 2020 at 12:16 PM Stefan Sperling <st...@elego.de> wrote:
>> On Wed, May 20, 2020 at 02:34:41PM +0200, Stefan Sperling wrote:
>>> The 1.14.0 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!
>> The current 1.14.0 signature count is 1x windows and 2x unix.
> I was wondering about that. Nathan committed his signature to the
> repository, but did not post a reply with his "+1" here. Is that
> explicit "+1" vote here required to make a signature / vote valid?
>
> I'm guessing: sig is valid when it is committed. But in the end it's
> the amount of "votes" that counts, and the vote is only done by
> sending a reply to dev@. Or am I guessing wrong?

You're guessing correctly. Natahan? I predict you have a draft mail
prepared somewhere. :)

-- Brane

Re: Subversion 1.14.0 up for testing/signing

Posted by Johan Corveleyn <jc...@gmail.com>.
On Tue, May 26, 2020 at 12:16 PM Stefan Sperling <st...@elego.de> wrote:
>
> On Wed, May 20, 2020 at 02:34:41PM +0200, Stefan Sperling wrote:
> > The 1.14.0 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!
>
> The current 1.14.0 signature count is 1x windows and 2x unix.

I was wondering about that. Nathan committed his signature to the
repository, but did not post a reply with his "+1" here. Is that
explicit "+1" vote here required to make a signature / vote valid?

I'm guessing: sig is valid when it is committed. But in the end it's
the amount of "votes" that counts, and the vote is only done by
sending a reply to dev@. Or am I guessing wrong?

-- 
Johan

Re: Subversion 1.14.0 up for testing/signing

Posted by Stefan Sperling <st...@elego.de>.
On Wed, May 20, 2020 at 02:34:41PM +0200, Stefan Sperling wrote:
> The 1.14.0 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!

The current 1.14.0 signature count is 1x windows and 2x unix.

I was planning to release tomorrow, one week after posting the tarballs
for signing. Is anyone still planning to add their signature?

Note that you do not strictly need to re-test, since the tarballs are
identical to -r2, as shown below.

> This release is essentially identical to 1.14.0-rc2 except for
> the designation of the version. The full diff between 1.14.0-rc2
> and 1.14.0 release artifacts is shown below.
> 
> 
> diff -urN subversion-1.14.0-rc2/subversion/bindings/swig/perl/native/core.c subversion-1.14.0/subversion/bindings/swig/perl/native/core.c
> --- subversion-1.14.0-rc2/subversion/bindings/swig/perl/native/core.c	Wed Apr  8 12:00:47 2020
> +++ subversion-1.14.0/subversion/bindings/swig/perl/native/core.c	Wed May 20 14:21:00 2020
> @@ -53178,12 +53178,12 @@
>    } while(0) /*@SWIG@*/;
>    /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
>      SV *sv = get_sv((char*) SWIG_prefix "SVN_VER_TAG", TRUE | 0x2 | GV_ADDMULTI);
> -    sv_setsv(sv, SWIG_FromCharPtr(" (Release Candidate 2)"));
> +    sv_setsv(sv, SWIG_FromCharPtr(" (r1876290)"));
>      SvREADONLY_on(sv);
>    } while(0) /*@SWIG@*/;
>    /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
>      SV *sv = get_sv((char*) SWIG_prefix "SVN_VER_NUMTAG", TRUE | 0x2 | GV_ADDMULTI);
> -    sv_setsv(sv, SWIG_FromCharPtr("-rc2"));
> +    sv_setsv(sv, SWIG_FromCharPtr(""));
>      SvREADONLY_on(sv);
>    } while(0) /*@SWIG@*/;
>    /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
> @@ -53198,12 +53198,12 @@
>    } while(0) /*@SWIG@*/;
>    /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
>      SV *sv = get_sv((char*) SWIG_prefix "SVN_VER_NUMBER", TRUE | 0x2 | GV_ADDMULTI);
> -    sv_setsv(sv, SWIG_FromCharPtr("1.14.0-rc2"));
> +    sv_setsv(sv, SWIG_FromCharPtr("1.14.0"));
>      SvREADONLY_on(sv);
>    } while(0) /*@SWIG@*/;
>    /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
>      SV *sv = get_sv((char*) SWIG_prefix "SVN_VERSION", TRUE | 0x2 | GV_ADDMULTI);
> -    sv_setsv(sv, SWIG_FromCharPtr("1.14.0-rc2 (Release Candidate 2)"));
> +    sv_setsv(sv, SWIG_FromCharPtr("1.14.0 (r1876290)"));
>      SvREADONLY_on(sv);
>    } while(0) /*@SWIG@*/;
>    /*@SWIG:/tmp/svn-rel/prefix/share/swig/3.0.12/perl5/perltypemaps.swg,65,%set_constant@*/ do {
> diff -urN subversion-1.14.0-rc2/subversion/bindings/swig/python/core.c subversion-1.14.0/subversion/bindings/swig/python/core.c
> --- subversion-1.14.0-rc2/subversion/bindings/swig/python/core.c	Wed Apr  8 12:00:07 2020
> +++ subversion-1.14.0/subversion/bindings/swig/python/core.c	Wed May 20 14:20:22 2020
> @@ -40645,12 +40645,12 @@
>    SWIG_Python_SetConstant(d, "SVN_VER_PATCH",SWIG_From_long((long)(0)));
>    SWIG_Python_SetConstant(d, "SVN_VER_MICRO",SWIG_From_long((long)(0)));
>    SWIG_Python_SetConstant(d, "SVN_VER_LIBRARY",SWIG_From_long((long)(1)));
> -  SWIG_Python_SetConstant(d, "SVN_VER_TAG",SWIG_FromCharPtr(" (Release Candidate 2)"));
> -  SWIG_Python_SetConstant(d, "SVN_VER_NUMTAG",SWIG_FromCharPtr("-rc2"));
> +  SWIG_Python_SetConstant(d, "SVN_VER_TAG",SWIG_FromCharPtr(" (r1876290)"));
> +  SWIG_Python_SetConstant(d, "SVN_VER_NUMTAG",SWIG_FromCharPtr(""));
>    SWIG_Python_SetConstant(d, "SVN_VER_REVISION",SWIG_From_long((long)(1876290)));
>    SWIG_Python_SetConstant(d, "SVN_VER_NUM",SWIG_FromCharPtr("1.14.0"));
> -  SWIG_Python_SetConstant(d, "SVN_VER_NUMBER",SWIG_FromCharPtr("1.14.0-rc2"));
> -  SWIG_Python_SetConstant(d, "SVN_VERSION",SWIG_FromCharPtr("1.14.0-rc2 (Release Candidate 2)"));
> +  SWIG_Python_SetConstant(d, "SVN_VER_NUMBER",SWIG_FromCharPtr("1.14.0"));
> +  SWIG_Python_SetConstant(d, "SVN_VERSION",SWIG_FromCharPtr("1.14.0 (r1876290)"));
>    SWIG_Python_SetConstant(d, "svn_prop_entry_kind",SWIG_From_long((long)(svn_prop_entry_kind)));
>    SWIG_Python_SetConstant(d, "svn_prop_wc_kind",SWIG_From_long((long)(svn_prop_wc_kind)));
>    SWIG_Python_SetConstant(d, "svn_prop_regular_kind",SWIG_From_long((long)(svn_prop_regular_kind)));
> diff -urN subversion-1.14.0-rc2/subversion/bindings/swig/ruby/core.c subversion-1.14.0/subversion/bindings/swig/ruby/core.c
> --- subversion-1.14.0-rc2/subversion/bindings/swig/ruby/core.c	Wed Apr  8 12:01:19 2020
> +++ subversion-1.14.0/subversion/bindings/swig/ruby/core.c	Wed May 20 14:21:29 2020
> @@ -46747,12 +46747,12 @@
>    rb_define_const(mCore, "SVN_VER_PATCH", SWIG_From_int((int)(0)));
>    rb_define_const(mCore, "SVN_VER_MICRO", SWIG_From_int((int)(0)));
>    rb_define_const(mCore, "SVN_VER_LIBRARY", SWIG_From_int((int)(1)));
> -  rb_define_const(mCore, "SVN_VER_TAG", SWIG_FromCharPtr(" (Release Candidate 2)"));
> -  rb_define_const(mCore, "SVN_VER_NUMTAG", SWIG_FromCharPtr("-rc2"));
> +  rb_define_const(mCore, "SVN_VER_TAG", SWIG_FromCharPtr(" (r1876290)"));
> +  rb_define_const(mCore, "SVN_VER_NUMTAG", SWIG_FromCharPtr(""));
>    rb_define_const(mCore, "SVN_VER_REVISION", SWIG_From_int((int)(1876290)));
>    rb_define_const(mCore, "SVN_VER_NUM", SWIG_FromCharPtr("1.14.0"));
> -  rb_define_const(mCore, "SVN_VER_NUMBER", SWIG_FromCharPtr("1.14.0-rc2"));
> -  rb_define_const(mCore, "SVN_VERSION", SWIG_FromCharPtr("1.14.0-rc2 (Release Candidate 2)"));
> +  rb_define_const(mCore, "SVN_VER_NUMBER", SWIG_FromCharPtr("1.14.0"));
> +  rb_define_const(mCore, "SVN_VERSION", SWIG_FromCharPtr("1.14.0 (r1876290)"));
>    
>    SwigClassSvn_version_t.klass = rb_define_class_under(mCore, "Svn_version_t", rb_cObject);
>    SWIG_TypeClientData(SWIGTYPE_p_svn_version_t, (void *) &SwigClassSvn_version_t);
> diff -urN subversion-1.14.0-rc2/subversion/include/svn_version.h subversion-1.14.0/subversion/include/svn_version.h
> --- subversion-1.14.0-rc2/subversion/include/svn_version.h	Wed Apr  8 11:59:11 2020
> +++ subversion-1.14.0/subversion/include/svn_version.h	Wed May 20 14:19:40 2020
> @@ -93,7 +93,7 @@
>   *
>   * Always change this at the same time as SVN_VER_NUMTAG.
>   */
> -#define SVN_VER_TAG        " (Release Candidate 2)"
> +#define SVN_VER_TAG        " (r1876290)"
>  
>  
>  /** Number tag: a string describing the version.
> @@ -108,7 +108,7 @@
>   *
>   * Always change this at the same time as SVN_VER_TAG.
>   */
> -#define SVN_VER_NUMTAG     "-rc2"
> +#define SVN_VER_NUMTAG     ""
>  
>  
>  /** Revision number: The repository revision number of this release.
> diff -urN subversion-1.14.0-rc2/subversion/po/subversion.pot subversion-1.14.0/subversion/po/subversion.pot
> --- subversion-1.14.0-rc2/subversion/po/subversion.pot	Wed Apr  8 11:59:41 2020
> +++ subversion-1.14.0/subversion/po/subversion.pot	Wed May 20 14:19:56 2020
> @@ -8,7 +8,7 @@
>  msgstr ""
>  "Project-Id-Version: PACKAGE VERSION\n"
>  "Report-Msgid-Bugs-To: dev@subversion.apache.org\n"
> -"POT-Creation-Date: 2020-04-08 09:59+0000\n"
> +"POT-Creation-Date: 2020-05-20 12:19+0000\n"
>  "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
>  "Last-Translator: FULL NAME <EM...@ADDRESS>\n"
>  "Language-Team: LANGUAGE <LL...@li.org>\n"
>