On 5/9/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
>
> On 5/5/06, Ian Sullivan <isullivan@gmail.com> wrote:
> > I deleted a file from my WC, then copied the WC to a tag and the tag
> > contained the deleted file...
> >
> > Is this correct behavior...
> >
> > I can see from the logs that when I did the copy svn checked the
> > revision number of my WC and used that revision for the copy.
> >
> > I know that if I modify files in my WC or add files, those files will
> > wind up in the tag, even if the WC isn't updated to the revision that
> > contains the changes.
> >
> > K:\svn_test\sub1>svn info
> > Path: .
> > URL: https://localhost:5150/svn/test/testing/trunk/sub1
> > Repository UUID: a0ed805a-73d8-0310-b6aa-88c1c10397f8
> > Revision: 559
> > Node Kind: directory
> > Schedule: normal
> > Last Changed Author: ian
> > Last Changed Rev: 548
> > Last Changed Date: 2005-07-28 12:22:06 -0700 (Thu, 28 Jul 2005)
> >
> > K:\svn_test\sub1>dir
> > 03/06/2006 04:05 PM 6 five.txt
> > 06/10/2005 01:22 PM 6 four.txt
> > 05/05/2006 04:29 PM 12 one.txt
> > 06/10/2005 01:19 PM 6 three.txt
> > 06/07/2005 04:19 PM 12 two.txt
> > K:\svn_test\sub1>svn del one.txt
> > D one.txt
> >
> > K:\svn_test\sub1>svn ci -m"testing"
> > Deleting sub1\one.txt
> >
> > Committed revision 563.
> >
> > K:\svn_test\sub1>svn info
> > Path: .
> > URL: https://localhost:5150/svn/test/testing/trunk/sub1
> > Repository UUID: a0ed805a-73d8-0310-b6aa-88c1c10397f8
> > Revision: 559
> > Node Kind: directory
> > Schedule: normal
> > Last Changed Author: ian
> > Last Changed Rev: 548
> > Last Changed Date: 2005-07-28 12:22:06 -0700 (Thu, 28 Jul 2005)
> >
> > K:\svn_test\sub1>svn copy -m"testing" .
> > https://localhost:5150/svn/test/tags/del_test2
> > Committed revision 564.
> >
> > K:\svn_test\sub1>svn list
> https://localhost:5150/svn/test/tags/del_test2
> > five.txt
> > four.txt
> > one.txt
> > three.txt
> > two.txt
> >
> > Client: 1.1.3(r12730)
> > Server: 1.1.4(r13838)
>
> Could you try with a more recent version of Subversion? I just tested
> this with a 1.4.x build and it works fine here. It's quite likely
> that this bug has been fixed in either 1.2 or 1.3.
>
> -garrett
>
Thanx garrett, I will see if upgrading the client and/or the server solves
the problem.
-Ian
Received on Thu May 11 01:22:50 2006