[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    =?UTF-8?B?W0lzc3VlIDE4MDZdIE5ldyAtICdzdm4gdXAnIHN0b3BzIHdoZW4gaQ==?=
From:       sussman () tigris ! org
Date:       2004-03-24 20:07:15
Message-ID: 20040324200715.23028.qmail () tigris ! org
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=1806
                  Issue #:|1806
                  Summary:|'svn up' stops when it doesn't have to.
                Component:|subversion
                  Version:|current
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|libsvn_wc
              Assigned to:|issues@subversion
              Reported by:|sussman






------- Additional comments from sussman@tigris.org Wed Mar 24 12:07:15 -0800 2004 -------
If 'svn up' tries to delete a versioned directory, and the directory contains
unversioned and/or locally-changed files, then an error is thrown back to the
client:

svn: Won't delete locally modified directory 'b'
svn: Left locally modified or unversioned files

Then 'svn up' just stops.  But it doesn't have to... the directory *is*
successfully removed from version control:  it's no longer in any entries file,
and all that's left behind is an unversioned dir containing some scattered paths
to unversioned files.  If the user runs 'svn up' again, the update process
continues and finishes happily.  

So:  why are we stopping at all?

At least one user has reported this annoyance:  their working copies are full of
unversioned objects (.o files, for example), and every time somebody moves a
directory in the tree, people have to run 'svn up' at least twice to complete
the update.  Pretty dumb.

What we really want is svn to print some sort of warning about leaving
unversioned files behind, not throw a full-out error.  There is no error, just
some information to report.   It's just a matter of trapping a very specific
error-code at a precise spot in our code.  Should be quite easy to fix.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
For additional commands, e-mail: issues-help@subversion.tigris.org

[prev in list] [next in list] [prev in thread] [next in thread]