[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion allows delete operation on an already deleted file

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 17 Feb 2009 20:29:52 +0000

On Wed, Feb 18, 2009 at 01:43:02AM +0530, vinay i wrote:
>
> Hello Ryan,
> Did you get a chance to look into this? Should I report this as a bug
> request on the Subversion website?
> Thanks,
> Vinay
>
> On Mon, Feb 16, 2009 at 2:10 PM, vinay i <[1]vinay.indresh_at_gmail.com>
> wrote:
>
> Yes. Please follow the below steps to reproduce the behavior. Do
> you think it is bug or am I missing something?
> Thanks,
> Vinay

This bug has been fixed in trunk and 1.6 as part of the tree conflicts
effort. Try it out, you will get an out of date error instead of a
double-delete.

Stefan

> /indreshv/duplicate> svn checkout
> file:///indreshv/test/trunk/src/java java1
> A java1/a.java
> A java1/b.java
> A java1/c.java
> A java1/d.java
> A java1/new.java
> Checked out revision 153.
> /indreshv/duplicate> svn checkout
> file:///indreshv/test/trunk/src/java java2
> A java2/a.java
> A java2/b.java
> A java2/c.java
> A java2/d.java
> A java2/new.java
> Checked out revision 153.
> /indreshv/duplicate> cd java1
> /indreshv/duplicate/java1> ls
> a.java b.java c.java d.java new.java
> /indreshv/duplicate/java1> svn delete new.java
> D new.java
> indreshv_at_invest1:/u/indreshv/duplicate/java1> svn commit -m
> "deleting new.java" .
> Deleting new.java
> Committed revision 154.
> /indreshv/duplicate> cd java2
> /indreshv/duplicate/java2> ls
> a.java b.java c.java d.java new.java
> /indreshv/duplicate/java2> svn delete new.java
> D new.java
> /indreshv/duplicate/java2> svn commit -m "deleting new.java again"
> .
> Deleting new.java
> Committed revision 155.
> /indreshv/duplicate/java2> svn log file:///indreshv/test -v -r154
> -------------------------------------------------------------------
> -----
> r154 | indreshv | 2009-02-16 13:29:18 +0530 (Mon, 16 Feb 2009) | 1
> line
> Changed paths:
> D /trunk/src/java/new.java
> deleting new.java
> -------------------------------------------------------------------
> -----
> /indreshv/duplicate/java2> svn log file:///indreshv/test -v -r155
> -------------------------------------------------------------------
> -----
> r155 | indreshv | 2009-02-16 13:29:58 +0530 (Mon, 16 Feb 2009) | 1
> line
> Changed paths:
> deleting new.java again
> -------------------------------------------------------------------
> -----
>
> On Sat, Feb 14, 2009 at 5:46 AM, Ryan Schmidt
> <[2]subversion-2009a_at_ryandesign.com> wrote:
>
> On Feb 10, 2009, at 12:49, vinay i wrote:
>
> Probably many of you would be aware of this. Assume I have a older
> checked out copy and another developer did a "svn delete" and "svn
> commit" on a particular file in his checked out copy of the same
> repository. Now, if I perform "svn delete" and "svn commit" on the
> same file without doing "svn update" it still allows me to commit.
> This is something which we don't expect to happen. Is there any
> standard procedure to avoid such commits?
>
> I wouldn't have expected that. Do you have a reproduction recipe we
> can try?
>
> References
>
> 1. mailto:vinay.indresh_at_gmail.com
> 2. mailto:subversion-2009a_at_ryandesign.com
Received on 2009-02-17 21:31:06 CET

This is an archived mail posted to the Subversion Users mailing list.