The former is an svn-export from the 1.9.10 tag, the latter is from the
unpacked tarball. I understand the difference in the time zone but I
don't know why our release script exports from the branch, not from the
tag? I'd sort of call that a bug ...
On 08.01.2019 20:19, Branko Čibej wrote:
> New issues:
> - 'make check-javahl' has become more verbose, printing this in every test:
> WARNING in native method: JNI call made without checking
> exceptions when required to from CallObjectMethodV
Most of these seem to have been fixed in 1.10.4 (which I tested with the
same version of Java as 1.9.10), and 1.11.1 with Java 11 doesn't report
any. So all this verbosity seems to be just a side effect of new checks
and warnings in newer Java (patch) releases, not anything that happened
on the branch.
Windows 7 SP1 (x64)
Microsoft Visual Studio 2013
Signature, sha1 and sha512 for subversion-1.9.10.zip.
Contents of subversion-1.9.10.zip are identical to tags/1.9.10, and
to branches/1.9.x@1850359 (except for expected differences in svn_version.h
and svnpubsub, svnwcsub and nominate.pl (symlinks vs. file contents), and
[ Release build ] x [ fsfs ] x [ file | svn | http ]
On Mon, Jan 07, 2019 at 12:46:24PM +0000, Julian Foad wrote:
> The 1.9.10 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.
Troy Curtis Jr wrote:
> Summary: +1 to release
> Tested: [bdb | fsfs] x [ra_local | ra_svn | ra_serf]
> swig bindings
> javahl bindings
> Tests fail for me with ctypes-python, but since I don't see ctypes-python listed as verified in the other email, I presume this is a known issue?
I don't think that's known. Please could you send the details. In rolling the tarballs, I tested ctypes-python and it passed on my system.