> -Original Message-
> From: Bert Huijben [mailto:b...@qqmail.nl]
> Sent: dinsdag 14 mei 2013 15:20
> To: 'Mark Phippard'; 'Ben Reser'
> Cc: 'Subversion Development'
> Subject: RE: 1.8.0-rc1 up for testing/signing
>
>
>
On 14.05.2013 15:19, Bert Huijben wrote:
>
>> -Original Message-
>> From: Mark Phippard [mailto:markp...@gmail.com]
>> Sent: vrijdag 10 mei 2013 17:43
>> To: Ben Reser
>> Cc: Subversion Development
>> Subject: Re: 1.8.0-rc1 up for testing/signing
>
> -Original Message-
> From: Mark Phippard [mailto:markp...@gmail.com]
> Sent: vrijdag 10 mei 2013 17:43
> To: Ben Reser
> Cc: Subversion Development
> Subject: Re: 1.8.0-rc1 up for testing/signing
>
> On Wed, May 8, 2013 at 12:40 PM, Mark Phippard
> wrote:
On Wed, May 8, 2013 at 2:22 AM, Branko Čibej wrote:
> It seems obvious that we'll not release this tarball after all, given
> the svnserve threading problems. I tested it anyway and it looks good,
> bar a few nits and a failure in the ctypes-python bindings test that
> don't recall being reported
On Fri, May 10, 2013 at 2:29 PM, Mark Phippard wrote:
> On Fri, May 10, 2013 at 12:43 PM, Ben Reser wrote:
>> On Wed, May 8, 2013 at 9:40 AM, Mark Phippard wrote:
>>> I am using a new build process and using VS 2012, so I am sure that is
>>> the problem. But I am getting 49 test failures. I am
On Fri, May 10, 2013 at 12:43 PM, Ben Reser wrote:
> On Wed, May 8, 2013 at 9:40 AM, Mark Phippard wrote:
>> I am using a new build process and using VS 2012, so I am sure that is
>> the problem. But I am getting 49 test failures. I am attaching the
>> fails.log but I do not think it lends much
On 10.05.2013 18:56, Mark Phippard wrote:
> On Fri, May 10, 2013 at 12:50 PM, Branko Čibej wrote:
>> On 10.05.2013 18:47, Mark Phippard wrote:
>>> FWIW, I do not agree with you on the syntax though. file:///foo Has
>>> always worked on Windows to access C:\foo The drive letter was only
>>> needed
On Fri, May 10, 2013 at 12:50 PM, Branko Čibej wrote:
> On 10.05.2013 18:47, Mark Phippard wrote:
>> FWIW, I do not agree with you on the syntax though. file:///foo Has
>> always worked on Windows to access C:\foo The drive letter was only
>> needed to access other drives.
>
> Well ... file:///foo
On 10.05.2013 18:47, Mark Phippard wrote:
> FWIW, I do not agree with you on the syntax though. file:///foo Has
> always worked on Windows to access C:\foo The drive letter was only
> needed to access other drives.
Well ... file:///foo is converted to (local) path \foo wich is a
drive-relative pat
On Fri, May 10, 2013 at 12:33 PM, Branko Čibej wrote:
> On 10.05.2013 18:22, Mark Phippard wrote:
>> On Fri, May 10, 2013 at 11:42 AM, Mark Phippard wrote:
>>> On Wed, May 8, 2013 at 12:40 PM, Mark Phippard wrote:
I am using a new build process and using VS 2012, so I am sure that is
t
On 10.05.2013 18:44, C. Michael Pilato wrote:
> On 05/10/2013 11:18 AM, Philip Martin wrote:
>> "C. Michael Pilato" writes:
>>
>>> I removed the system-installed APR and APR-Util. Still seeing the problem.
>>> I'm a bit confused because the library appears (via ldd, at least) to be
>>> linking a
On 05/10/2013 11:18 AM, Philip Martin wrote:
> "C. Michael Pilato" writes:
>
>> I removed the system-installed APR and APR-Util. Still seeing the problem.
>> I'm a bit confused because the library appears (via ldd, at least) to be
>> linking against the correct apr-util (and was doing so before
On Wed, May 8, 2013 at 9:40 AM, Mark Phippard wrote:
> I am using a new build process and using VS 2012, so I am sure that is
> the problem. But I am getting 49 test failures. I am attaching the
> fails.log but I do not think it lends much ideas. I tried running
> with --verbose but the output
On 10.05.2013 18:22, Mark Phippard wrote:
> On Fri, May 10, 2013 at 11:42 AM, Mark Phippard wrote:
>> On Wed, May 8, 2013 at 12:40 PM, Mark Phippard wrote:
>>> I am using a new build process and using VS 2012, so I am sure that is
>>> the problem. But I am getting 49 test failures. I am attachi
On Fri, May 10, 2013 at 11:42 AM, Mark Phippard wrote:
> On Wed, May 8, 2013 at 12:40 PM, Mark Phippard wrote:
>> I am using a new build process and using VS 2012, so I am sure that is
>> the problem. But I am getting 49 test failures. I am attaching the
>> fails.log but I do not think it lends
"C. Michael Pilato" writes:
> I removed the system-installed APR and APR-Util. Still seeing the problem.
> I'm a bit confused because the library appears (via ldd, at least) to be
> linking against the correct apr-util (and was doing so before I removed the
> system-install versions, even).
Th
On Wed, May 8, 2013 at 12:40 PM, Mark Phippard wrote:
> I am using a new build process and using VS 2012, so I am sure that is
> the problem. But I am getting 49 test failures. I am attaching the
> fails.log but I do not think it lends much ideas. I tried running
> with --verbose but the output
"C. Michael Pilato" writes:
> I removed the system-installed APR and APR-Util. Still seeing the problem.
> I'm a bit confused because the library appears (via ldd, at least) to be
> linking against the correct apr-util (and was doing so before I removed the
> system-install versions, even).
Tr
On 05/07/2013 08:23 AM, Branko Čibej wrote:
> On 07.05.2013 14:06, C. Michael Pilato wrote:
>> My guess is also that the build was picking up the older system
>> apr-util version, but I haven't been able to verify that yet.
>
> All I can suggest (assuming you're on Linux) is to check the RPATH
>
It seems obvious that we'll not release this tarball after all, given
the svnserve threading problems. I tested it anyway and it looks good,
bar a few nits and a failure in the ctypes-python bindings test that
don't recall being reported yet.
-- Brane
Summary:
+0 to release
Platform
Ma
On Wed, May 8, 2013 at 1:00 PM, Bert Huijben wrote:
>> -Original Message-
>> From: Ivan Zhakov [mailto:i...@visualsvn.com]
>> Sent: woensdag 8 mei 2013 01:46
>> To: Subversion Development
>> Subject: Re: Thread issues in svnserve (was Re: 1.8.0-rc1 up for
&g
> -Original Message-
> From: Ivan Zhakov [mailto:i...@visualsvn.com]
> Sent: woensdag 8 mei 2013 01:46
> To: Subversion Development
> Subject: Re: Thread issues in svnserve (was Re: 1.8.0-rc1 up for
> testing/signing)
>
> On Sun, May 5, 2013 at 8:27 PM, Ivan Z
On Sun, May 5, 2013 at 8:27 PM, Ivan Zhakov wrote:
> On Sun, May 5, 2013 at 6:36 PM, Ivan Zhakov wrote:
>> On Sat, May 4, 2013 at 4:01 PM, Ivan Zhakov wrote:
>>> On Sat, May 4, 2013 at 4:34 AM, Ben Reser wrote:
Here it is: the first Release Candidate for Subversion 1.8.0. You can
fet
On Tue, May 7, 2013 at 7:56 AM, Paul Burba wrote:
> Minor issue, but
> https://dist.apache.org/repos/dist/dev/subversion/subversion-1.8.0-rc1.zip
> differs from
> https://svn.apache.org/repos/asf/subversion/branches/1.8.x@1478983
> in an unexpected way. The links in these two svnpubsub files are
On Fri, May 3, 2013 at 8:34 PM, Ben Reser wrote:
> Here it is: the first Release Candidate for Subversion 1.8.0. You can
> fetch the proposed tarballs from here:
> https://dist.apache.org/repos/dist/dev/subversion
>
> The magic rev is r1478983
Hi Ben,
Minor issue, but
https://dist.apache.org/
On 07.05.2013 14:06, C. Michael Pilato wrote:
> My guess is also that the build was picking up the older system
> apr-util version, but I haven't been able to verify that yet.
All I can suggest (assuming you're on Linux) is to check the RPATH
encoded in the binary modules created by the ctypes bi
On 05/06/2013 04:39 PM, Branko Čibej wrote:
> On 06.05.2013 21:42, C. Michael Pilato wrote:
>> On 05/06/2013 03:11 PM, Branko Čibej wrote:
>>> It's always worked that way for me, but then, my APR doesn't change that
>>> often. Sounds like a different APR is loaded at runtime than was
>>> compiled a
On Mon, May 6, 2013 at 3:42 PM, C. Michael Pilato wrote:
> On 05/06/2013 03:11 PM, Branko Čibej wrote:
>> It's always worked that way for me, but then, my APR doesn't change that
>> often. Sounds like a different APR is loaded at runtime than was
>> compiled against; but I can't understand why lib
On 06.05.2013 21:42, C. Michael Pilato wrote:
> On 05/06/2013 03:11 PM, Branko Čibej wrote:
>> It's always worked that way for me, but then, my APR doesn't change that
>> often. Sounds like a different APR is loaded at runtime than was
>> compiled against; but I can't understand why libsvn_subr wou
On Mon, May 6, 2013 at 11:37 AM, Mark Phippard wrote:
> My Windows system is not setup to build 1.8.x in the sense that I have
> been building 1.7.x with a set of dependencies I built a fairly long
> time ago and have pretty much just left in tact from release to
> release and are now old and out
On 05/06/2013 03:11 PM, Branko Čibej wrote:
> It's always worked that way for me, but then, my APR doesn't change that
> often. Sounds like a different APR is loaded at runtime than was
> compiled against; but I can't understand why libsvn_subr would use the
> apr_crypto API?
See libsvn_subr/crypt
On 06.05.2013 20:59, C. Michael Pilato wrote:
> On 05/06/2013 02:43 PM, Daniel Shahaf wrote:
>> C. Michael Pilato wrote on Mon, May 06, 2013 at 14:30:02 -0400:
>>> Having trouble with ctypes-python tests. I get the following error via the
>>> tarball and also when trying to run the same tests on t
On 05/06/2013 02:43 PM, Daniel Shahaf wrote:
> C. Michael Pilato wrote on Mon, May 06, 2013 at 14:30:02 -0400:
>> Having trouble with ctypes-python tests. I get the following error via the
>> tarball and also when trying to run the same tests on trunk:
[...]
>> Any ideas if this is a false alarm
C. Michael Pilato wrote on Mon, May 06, 2013 at 14:30:02 -0400:
> On 05/03/2013 08:34 PM, Ben Reser wrote:
> > Here it is: the first Release Candidate for Subversion 1.8.0. You can
> > fetch the proposed tarballs from here:
> > https://dist.apache.org/repos/dist/dev/subversion
>
> Having troubl
My Windows system is not setup to build 1.8.x in the sense that I have
been building 1.7.x with a set of dependencies I built a fairly long
time ago and have pretty much just left in tact from release to
release and are now old and out of date. It would make sense to
update to the latest versions
On 05/03/2013 08:34 PM, Ben Reser wrote:
> Here it is: the first Release Candidate for Subversion 1.8.0. You can
> fetch the proposed tarballs from here:
> https://dist.apache.org/repos/dist/dev/subversion
Having trouble with ctypes-python tests. I get the following error via the
tarball and a
On Sun, May 5, 2013 at 6:02 AM, Stefan Sperling wrote:
> The CHANGES file in the tarball is incomplete. At the very least, it
> lacks some cleanup and a projected release date. Do we really want to
> issue the 1.8.0 release with an incomplete CHANGES file?
Of course not, but this file won't be 1.
On Sun, May 5, 2013 at 6:36 PM, Ivan Zhakov wrote:
> On Sat, May 4, 2013 at 4:01 PM, Ivan Zhakov wrote:
>> On Sat, May 4, 2013 at 4:34 AM, Ben Reser wrote:
>>> Here it is: the first Release Candidate for Subversion 1.8.0. You can
>>> fetch the proposed tarballs from here:
>>> https://dist.apa
On Sat, May 4, 2013 at 4:01 PM, Ivan Zhakov wrote:
> On Sat, May 4, 2013 at 4:34 AM, Ben Reser wrote:
>> Here it is: the first Release Candidate for Subversion 1.8.0. You can
>> fetch the proposed tarballs from here:
>> https://dist.apache.org/repos/dist/dev/subversion
>>
> I've got crash in s
> -Original Message-
> From: Stefan Sperling [mailto:s...@elego.de]
> Sent: zondag 5 mei 2013 15:03
> To: Ben Reser
> Cc: Subversion Development
> Subject: Re: 1.8.0-rc1 up for testing/signing
>
> On Fri, May 03, 2013 at 05:34:49PM -0700, Ben Reser wrote:
> >
On Fri, May 03, 2013 at 05:34:49PM -0700, Ben Reser wrote:
> Here it is: the first Release Candidate for Subversion 1.8.0. You can
> fetch the proposed tarballs from here:
> https://dist.apache.org/repos/dist/dev/subversion
>
> The magic rev is r1478983
Summary: +1 to release
My only concern
On Fri, May 03, 2013 at 05:34:49PM -0700, Ben Reser wrote:
> Here it is: the first Release Candidate for Subversion 1.8.0. You can
> fetch the proposed tarballs from here:
> https://dist.apache.org/repos/dist/dev/subversion
>
> The magic rev is r1478983
>
> This is a release candidate, meaning
On Sat, May 4, 2013 at 4:15 AM, Daniel Shahaf wrote:
> Ben Reser wrote on Fri, May 03, 2013 at 22:40:57 -0700:
>> The notice in the file sounds like a good idea, but I'll need to tweak
>> the bot to do it. Maybe I'll have some time to do it tomorrow.
>
> r1479077.
Thanks, I added a comment in r1
On Sat, May 4, 2013 at 4:34 AM, Ben Reser wrote:
> Here it is: the first Release Candidate for Subversion 1.8.0. You can
> fetch the proposed tarballs from here:
> https://dist.apache.org/repos/dist/dev/subversion
>
I've got crash in svnserve when running 32-bit test suite over svn://
protocol
Ben Reser wrote on Fri, May 03, 2013 at 22:40:57 -0700:
> The notice in the file sounds like a good idea, but I'll need to tweak
> the bot to do it. Maybe I'll have some time to do it tomorrow.
r1479077.
On Fri, May 3, 2013 at 10:12 PM, Daniel Shahaf wrote:
> That's a little confusing workflow: "To approve a backport, move it to
> the end of the file, unless the RM said the file on dev@ is frozen".
Well the branch isn't really frozen. It's just restricted to things
that don't restart our soak.
Ben Reser wrote on Fri, May 03, 2013 at 17:34:49 -0700:
> Reminder that the STATUS file is still for 1.8.0, please be careful
> about moving changes to the approved section and only move changes
> that appropriate to be merged at this point (i.e. changes that would not
> restart our soak).
That's
47 matches
Mail list logo
