Re: Subversion 1.6.18 released

2012-04-14 Thread Stefan Sperling
On Fri, Apr 13, 2012 at 10:38:52PM +0200, Johan Corveleyn wrote: On Thu, Apr 12, 2012 at 3:15 PM, Stefan Sperling s...@apache.org wrote: I'm happy to announce the release of Apache Subversion 1.6.18. [...] For this release, the following people have provided PGP signatures:   C.

Re: Subversion 1.6.18 released

2012-04-14 Thread Daniel Shahaf
Stefan Sperling wrote on Sat, Apr 14, 2012 at 15:32:04 +0200: I suppose in the future we should mark the .asc files as text instead of binary and set their eol-style to 'native'. Agreed. r1326103

Ev2 and Authz

2012-04-14 Thread Hyrum K Wright
Good morning (in some parts of the world)! I've been doing some poking around with Ev2 and copy operations on the ev2-export branch, and have some observations which merit discussion. In the working copy and elsewhere, all versioned nodes map to a repos_relpath, and I've found it greatly

svn_checksum__from_digest() core dump on invalid input

2012-04-14 Thread Blair Zajac
In tracking down spurious coredumps we have in our custom RPC server, I found one in svn_checksum__from_digest() due to bad input: svn_checksum_t * svn_checksum__from_digest(const unsigned char *digest, svn_checksum_kind_t kind, apr_pool_t

Re: Subversion 1.6.18 released

2012-04-14 Thread Johan Corveleyn
On Sat, Apr 14, 2012 at 3:32 PM, Stefan Sperling s...@apache.org wrote: On Fri, Apr 13, 2012 at 10:38:52PM +0200, Johan Corveleyn wrote: On Thu, Apr 12, 2012 at 3:15 PM, Stefan Sperling s...@apache.org wrote: I'm happy to announce the release of Apache Subversion 1.6.18. [...] For this

Use 1.7.7 for next release (was: Re: 1.7.5 in one/two weeks?)

2012-04-14 Thread Konstantin Kolinko
2012/4/12 Daniel Shahaf danie...@apache.org: We released 1.6.18 today and 1.7.4 just over a month ago.  There are a few useful items merged already, and STATUS has a truckload of pending changes. Shall we roll 1.7.5 in two weeks from today?  If we can clear STATUS and roll next Thursday

Re: Use 1.7.7 for next release (was: Re: 1.7.5 in one/two weeks?)

2012-04-14 Thread Blair Zajac
On 4/14/12 12:24 PM, Konstantin Kolinko wrote: 2012/4/12 Daniel Shahafdanie...@apache.org: We released 1.6.18 today and 1.7.4 just over a month ago. There are a few useful items merged already, and STATUS has a truckload of pending changes. Shall we roll 1.7.5 in two weeks from today? If we

Re: Use 1.7.7 for next release (was: Re: 1.7.5 in one/two weeks?)

2012-04-14 Thread Hyrum K Wright
On Sat, Apr 14, 2012 at 2:31 PM, Blair Zajac bl...@orcaware.com wrote: On 4/14/12 12:24 PM, Konstantin Kolinko wrote: 2012/4/12 Daniel Shahafdanie...@apache.org: We released 1.6.18 today and 1.7.4 just over a month ago.  There are a few useful items merged already, and STATUS has a truckload

Re: Use 1.7.7 for next release (was: Re: 1.7.5 in one/two weeks?)

2012-04-14 Thread Greg Stein
On Sat, Apr 14, 2012 at 15:31, Blair Zajac bl...@orcaware.com wrote: On 4/14/12 12:24 PM, Konstantin Kolinko wrote: 2012/4/12 Daniel Shahafdanie...@apache.org: We released 1.6.18 today and 1.7.4 just over a month ago.  There are a few useful items merged already, and STATUS has a truckload

Re: Use 1.7.7 for next release

2012-04-14 Thread Stefan Küng
On 14.04.2012 21:31, Blair Zajac wrote: On 4/14/12 12:24 PM, Konstantin Kolinko wrote: 2012/4/12 Daniel Shahafdanie...@apache.org: We released 1.6.18 today and 1.7.4 just over a month ago. There are a few useful items merged already, and STATUS has a truckload of pending changes. Shall we

Re: Use 1.7.7 for next release

2012-04-14 Thread Greg Stein
On Sat, Apr 14, 2012 at 16:15, Stefan Küng tortoise...@gmail.com wrote: On 14.04.2012 21:31, Blair Zajac wrote: On 4/14/12 12:24 PM, Konstantin Kolinko wrote: 2012/4/12 Daniel Shahafdanie...@apache.org: We released 1.6.18 today and 1.7.4 just over a month ago. There are a few useful items

Re: Use 1.7.7 for next release

2012-04-14 Thread Stefan Küng
On 14.04.2012 22:28, Greg Stein wrote: I have a proposal: Skip several numbers and name the next release as 1.7.7. Justification: to align with TortoiseSVN, which is 1.7.6 now. There is a lot of Subversion exception! threads on users@ where TortoiseSVN version is visible. For example [1]. I

Re: Use 1.7.7 for next release

2012-04-14 Thread Stefan Küng
On 14.04.2012 22:40, Hyrum K Wright wrote: On Sat, Apr 14, 2012 at 3:36 PM, Stefan Küngtortoise...@gmail.com wrote: On 14.04.2012 22:28, Greg Stein wrote: I have a proposal: Skip several numbers and name the next release as 1.7.7. Justification: to align with TortoiseSVN, which is 1.7.6

Re: Use 1.7.7 for next release

2012-04-14 Thread Greg Stein
On Apr 14, 2012 4:46 PM, Stefan Küng tortoise...@gmail.com wrote: On 14.04.2012 22:40, Hyrum K Wright wrote: On Sat, Apr 14, 2012 at 3:36 PM, Stefan Küngtortoise...@gmail.com wrote: On 14.04.2012 22:28, Greg Stein wrote: I have a proposal: Skip several numbers and name the next release

Re: Use 1.7.7 for next release

2012-04-14 Thread Stefan Küng
On 14.04.2012 23:46, Greg Stein wrote: So I'll keep the first three version numbers the same in the future for interim releases (in case I have to create one). But I guess if you want to improve the current situation, there's not much I can do. Hyrum is suggesting we release 1.7.5, and

Re: Use 1.7.7 for next release

2012-04-14 Thread Mark Phippard
On Sat, Apr 14, 2012 at 5:52 PM, Stefan Küng tortoise...@gmail.com wrote: On 14.04.2012 23:46, Greg Stein wrote:   So I'll keep the first three version numbers the same in the future for interim releases (in case I have to create one).   But I guess if you want to improve the current

Re: Use 1.7.7 for next release (was: Re: 1.7.5 in one/two weeks?)

2012-04-14 Thread Daniel Shahaf
Konstantin Kolinko wrote on Sat, Apr 14, 2012 at 23:24:57 +0400: 2012/4/12 Daniel Shahaf danie...@apache.org: We released 1.6.18 today and 1.7.4 just over a month ago.  There are a few useful items merged already, and STATUS has a truckload of pending changes. Shall we roll 1.7.5 in two

Faster build/check times

2012-04-14 Thread Daniel Shahaf
Trying to enumerate ways to reduce build times. Faster builds: - export CONFIG_SHELL=/bin/sh (minimal sh preferred) - out-of-tree build (i.e., run 'configure' in an empty dir), with the build tree in a tmpfs - disable unneeded components (eg, swig, bdb) when they're not needed - pass '-q' to