Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 4 Aug 2015 15:20:20 +0200
From: Stefan Sperling <stsp@elego.de>
To: Branko =?utf-8?B?xIxpYmVq?= <brane@apache.org>,
        Subversion Development <dev@subversion.apache.org>
Subject: Re: Subversion 1.7.21 up for testing/signing
Message-ID: <20150804132020.GX30785@ted.stsp.name>
Mail-Followup-To: Branko =?utf-8?B?xIxpYmVq?= <brane@apache.org>,
	Subversion Development <dev@subversion.apache.org>
References: <55B5C05E.5030407@apache.org>
 <20150727165627.GC2207@ted.stsp.name>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20150727165627.GC2207@ted.stsp.name>
User-Agent: Mutt/1.5.23 (2014-03-12)

On Mon, Jul 27, 2015 at 06:56:27PM +0200, Stefan Sperling wrote:
> On Mon, Jul 27, 2015 at 07:23:42AM +0200, Branko Čibej wrote:
> > The 1.7.21 release artefacts 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_neon | ra_serf]
>         swig bindings
>         javahl bindings
> 
> Test results: All passed, except libsvn_subr/mergeinfo-test 6 and 10 which had
>               occasional failures (segfaults) due to a one-byte read past a
>               string buffer. This is not a regression from 1.7.20 -- the same
>               problem can be reproduced there. The problem does not occur with
>               1.8.x, 1.9.x, and trunk. Earlier reported here:
>               http://mail-archives.apache.org/mod_mbox/subversion-dev/201412.mbox/%3C20141210134456.GA24470%40ted.stsp.name%3E
> 
>               The swig Ruby tests segfaulted, too. This is also not a new issue.
> 	      Probably needs a merge of r1604999 to get fixed.

I re-ran my tests with r1694012 applied to 1.7.21 and the results
where as decribed above.

So my signature for 1.7.21 is still valid.

I would release 1.7.21 with a note that advises end users about the test
suite problem and include the diff of r1694012 in the release announcement.
This way, end users who wish to verify their binaries by running the test
suite can still do so.

> Platform: OpenBSD 5.8 amd64
> 
> Dependencies:
> bdb:        4.7.25
> GNU-iconv:  1.14
> apr:        1.5.1
> apr-util:   1.5.3
> httpd:      2.2.29
> neon:       0.30.0
> serf:       1.3.8
> cyrus-sasl: 2.1.25
> sqlite:     3080500
> openssl:    2.2
> swig:       2.0.11
> python:     2.7.8
> perl:       5.20.2
> ruby:       1.8.7-p358
> java:       1.7.0_80
> 
> Signatures:
> 
> subversion-1.7.21.tar.gz
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> 
> iQEcBAABAgAGBQJVtmAUAAoJEE99uqmaWblzThIH/3dDzymitlXHVKHc+/+nUqn1
> 1VjDT/MNdSkd2SHmrAdNvDJeXwdlcGjgePD1wqbUqxXzfB8CClOIbpfE4TzZkaEW
> pGHST6GFSkrb+Zz9coft05WG3xLZa7zYrzq4UJ7VukIQ9WyepW+h3vcdQ4M4hh+u
> vj68ZOyhFH/jTrwF5z5vvDrrSsO2tytkuiLeij7U7iipELj8fgNxF7tNgv9HWuy2
> h3opnH5GmJjP6STIdPZwSbdjIh4JeciBYPIY6agSn9/IA0Q4mmiS3L91yjcd5EN5
> 2WR+PofHwIYO8YXrft3cEAiRzftRLpiB9IjdQh0fLiDYMYp+XIpQ9++raTwZxa0=
> =PhI9
> -----END PGP SIGNATURE-----
> 
> subversion-1.7.21.tar.bz2
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> 
> iQEcBAABAgAGBQJVtmAaAAoJEE99uqmaWblzl1YH/iry7uhxZXRQK5UmTDgMqeIY
> daOfu7np1h4hbkYM27JkiF9fmZl8Gr3YWLOJj0BgBG+9QbHRfu53DxNnd8V0HjFY
> vty8sBJPlJz2tKhRSPkx1xo3UGKYXGmXSU0fjwLYDJzD6xeB+sLTewTIVZCxBu09
> vHEXp0+z30lbEdiho+GwPqWob0BFiI7MA6uJpFlRNrVnOhNtcO8AU3vwaA0YUgAU
> LG7YKZN6eK1vVHIs1z8+5q41pb7lQr2DjTXQRry9Yi6DKH2n5STnDcg4nqyQlXOp
> Ml9YK/LOlJ6S+0IHNEMPsp7L2olZbk7lahPNqshzpg82r8J1ZUqq4iVjXOyuTPs=
> =SbZ9
> -----END PGP SIGNATURE-----