Here is some more info:
First I show the results of the svnversion, showing the mixed revision.
Then I do a svn merge (with -allow-mixed-revisions) and get the E195020 error
Then I do an svn up
Then another svnversion still showing the mixed revision
Then finally the merge showing the problem still
On Tue, Mar 31, 2015 at 2:19 AM, Johan Corveleyn wrote:
...
> I think I've found a workaround: it seems the tree walk by mod_dav is
> avoided when the request has a header Depth with value 0. I've tried
> adding
>
>
> RequestHeader set Depth 0
>
Apparently this workaround is spe
Only to record.
I solved the problem looking for ephemeral properties on commit. They are
only sent for 1.8 clients.
To do this I changed my start-commit hook was to this:
#!/usr/bin/env python
# The start-commit hook is invoked before a Subversion txn is created
# in the process of doing a com
The stackoverflow issue seems to be similar, I cant confirm it's the same issue
however, since there is no "tell tail sign of failure"
However, I am using 1.8.11, and the article implies this bug has been fixed
since 1.7.0
Scott
From: Scott Aron Bloom [mailto:sc...@towel42.com]
Sent: Tuesday,
Sorry for asking without proprer documentation read and thanks.
There is a way to "detect" that the log message is not sent because of an
older client version?
My intent is to block the commit early if I can.
On Tuesday, March 31, 2015 at 12:28:37 PM UTC-3, Andreas Stieger wrote:
>
> Hello,
>
Hello,
> validate the log message [...] start-commit [...]
> [...]
> if the client is using an older version (like 1.7) the commit message
> obtained
> using svnlook is always empty durng the start-commit. In this case the commit
> message is available only during pre-commit.
Yes, and this
Hi, I'm trying to validate the log message using the new 1.8 start-commit
capability of inspect the transaction beeing created.
My problem is that if the client is using an older version (like 1.7) the
commit message obtained using svnlook is always empty durng the
start-commit. In this case th
Hello.
Firstly I'd like to say thank you, Pete, for bringing up this issue
and discussing it so clearly.
I had a think about this the other day and chatted with the others on IRC [1].
I picked this old email from this thread to reply to, as it's got me
in the CC and is as good a one as any to re
Sorry, I misunderstood your question. Svn up succeeds but does not fix th3
svn merge issue.
I'll look at the stack overflow issue since we do have a bunch of externals.
~~Scott
Original message
From: Johan Corveleyn
Date:03/31/2015 02:29 (GMT-08:00)
To: Scott Aron Bloom
On 31.03.2015 14:43, Mark Phippard wrote:
>> On Mar 31, 2015, at 8:13 AM, Johan Corveleyn wrote:
>>
>>> On Tue, Mar 31, 2015 at 2:19 AM, Johan Corveleyn wrote:
On Sun, Mar 29, 2015 at 7:57 PM, Johan Corveleyn wrote:
> On Sat, Mar 28, 2015 at 5:09 PM, Bert Huijben wrote:
>
>
>>>
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: dinsdag 31 maart 2015 14:13
> To: users@subversion.apache.org
> Cc: Bert Huijben; Philip Martin; Ben Reser
> Subject: Re: Branching slow 1.8.11 https
>
> On Tue, Mar 31, 2015 at 2:19 AM, Johan Corveleyn
> wr
> On Mar 31, 2015, at 8:13 AM, Johan Corveleyn wrote:
>
>> On Tue, Mar 31, 2015 at 2:19 AM, Johan Corveleyn wrote:
>>> On Sun, Mar 29, 2015 at 7:57 PM, Johan Corveleyn wrote:
On Sat, Mar 28, 2015 at 5:09 PM, Bert Huijben wrote:
> -Original Message-
> From: Joh
On Tue, Mar 31, 2015 at 2:19 AM, Johan Corveleyn wrote:
> On Sun, Mar 29, 2015 at 7:57 PM, Johan Corveleyn wrote:
>> On Sat, Mar 28, 2015 at 5:09 PM, Bert Huijben wrote:
>>>
>>>
-Original Message-
From: Johan Corveleyn [mailto:jcor...@gmail.com]
Sent: vrijdag 27 maart 2015
I'm happy to announce the release of Apache Subversion 1.7.20.
This release addresses two security issues:
CVE-2015-0248: Subversion mod_dav_svn and svnserve are vulnerable to a
remotely triggerable assertion DoS vulnerability for certain
requests with dynamica
I'm happy to announce the release of Apache Subversion 1.8.13.
This release addresses 3 security issues.
CVE-2015-0202: Subversion HTTP servers with FSFS repositories are
vulnerable to a remotely triggerable excessive memory
use with certain REPORT requests.
Please read http://subversion.apache.org/mailing-lists.html before sending
another useless "request".
Thanks.
unsubscribe
On Tue, Mar 31, 2015 at 2:56 AM, Scott Aron Bloom wrote:
>
>
>
> ~~Scott
>
> Original message
> From: Johan Corveleyn
> Date:03/30/2015 12:48 (GMT-08:00)
> To: Scott Aron Bloom
> Cc: users@subversion.apache.org
> Subject: Re: Issue in svn E195020
>
>
>> Its has been common, tha
18 matches
Mail list logo