Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of brane@wandisco.com designates
 74.125.83.54 as permitted sender)
Message-ID: <531322C5.4070402@wandisco.com>
Date: Sun, 02 Mar 2014 13:23:33 +0100
From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@wandisco.com>
Organization: WANdisco
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: users@subversion.apache.org
Subject: Re: Can't move temporary on update.
References: <52D45348.7000807@gmx.de> <52D45B64.80502@gmx.de>
 <52D46EAD.4040307@reser.org> <5313017E.8010907@gmx.de>
 <53130A91.9020905@gmx.de>
In-Reply-To: <53130A91.9020905@gmx.de>
Content-Type: multipart/alternative;
 boundary="------------080705010509000906070100"

This is a multi-part message in MIME format.
--------------080705010509000906070100
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 02.03.2014 11:40, Stefan wrote:
> Hi,
>
> I came up with an even easier repro case. It seems to suffice to
> trigger the problem by simply committing the problematic file to an
> empty local repository and having avast installed.
> To whom should I send the repro-case (it requires the zipped-exe-file).

The problem is obviously caused by the virus scanner. If it's renaming
files from under Subversion's nose, there's really nothing we can do
about it.

-- Brane


-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com

--------------080705010509000906070100
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 02.03.2014 11:40, Stefan wrote:<br>
    </div>
    <blockquote cite="mid:53130A91.9020905@gmx.de" type="cite">Hi,
      <br>
      <br>
      I came up with an even easier repro case. It seems to suffice to
      trigger the problem by simply committing the problematic file to
      an empty local repository and having avast installed.
      <br>
      To whom should I send the repro-case (it requires the
      zipped-exe-file).<br>
    </blockquote>
    <br>
    The problem is obviously caused by the virus scanner. If it's
    renaming files from under Subversion's nose, there's really nothing
    we can do about it.<br>
    <br>
    -- Brane<br>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <span style="font-face:sans-serif;font-size:9pt;line-height:18pt">Branko
        Čibej <span style="color: #f90">|</span> <span
          style="font-weight:bold">Director of Subversion</span>
        <br>
        WANdisco <span style="color: #f90">//</span> <span
          style="font-style:oblique">Non-Stop Data</span>
        <br>
        <span style="color: #ccc">e.</span> <a class="moz-txt-link-abbreviated" href="mailto:brane@wandisco.com">brane@wandisco.com</a></span></div>
  </body>
</html>

--------------080705010509000906070100--