Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <531D757A.1050005@zmdi.com>
Date: Mon, 10 Mar 2014 09:19:06 +0100
From: Holger Schmidt <Holger.Schmidt@zmdi.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.12) Gecko/20130110 Thunderbird/10.0.12
MIME-Version: 1.0
To: <users@subversion.apache.org>
CC: Holger Schmidt <Holger.Schmidt@zmdi.com>
Subject: Re: Update in excluded directory schedules files for deletion
References: <53149F0D.1070804@zmdi.com>
In-Reply-To: <53149F0D.1070804@zmdi.com>
X-SafeGuard_MailGateway: Version: 6.00.1.12740 SGMG_SOPHOS Date:
 20140310081907Z
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-purgate-relay-fid: relay-9b77e0
X-purgate-sourceid: 1WMvQR-0008Hw-NZ
X-purgate-Ad: Checked for spam and viruses by eXpurgate(R),
 see www.eleven.de for details.
X-purgate-ID: 151534::1394439548-000022CE-5E9B9046/0-0/0-0
X-purgate: clean
X-purgate-type: clean
X-purgate-relay-bid: relay-3cc1a3
X-Virus-Checked: Checked by ClamAV on apache.org

On 03.03.2014 16:26, Holger Schmidt wrote:
> Hi,
>
> Can someone please look at this issue, I think it is a bug. I have a
> working copy with some directories, some have private files in them. I
> don't need one of the directories and exclude it from the working copy
> with "svn up --set-depth=exclude". The directory remains because there
> were private files. If I change into the excluded directory I can query
> the status and update! The update reports a tree conflict. If I choose
> "mark resolved" the directory is scheduled for deletion. Is this
> intended behavior? I would expect that an excluded directory is like a
> private directory, i.e. no status and update is possible. I think it is
> dangerous if an update schedules something for deletion. It's an update,
> not a remove. Tested with version 1.8.8 compiled on
> x86_64-unknown-linux-gnu.
>
> Try these commands:
>
> svnadmin create repo
> svn co file://`pwd`/repo wc
> svn mkdir wc/dir
> echo a > wc/dir/file1
> svn add wc/dir/file1
> svn ci -m "Added data." wc
> cd wc/
> echo b > dir/file2
> svn up --set-depth=exclude dir
> cd dir/
> svn st -u
> svn up
> svn ci

Hi,

Was someone able to reproduce this?  Would you consider it to be a bug?

Thanks,
Holger