On Oct 7, 2004, at 3:57 PM, Nathan Kidd wrote:
> Scott Palmer wrote:
> <SNIP>
>> I had a case today where I went to commit my changes to Subversion,
>> and I got a message that my working copy was not up to date. So I
>> issued a 'svn up' command with the intention of trying my commit
>> again. At this point things went horribly wrong because the update
>> was unable to deal with the read-ony files that it was trying to
>> replace. The update aborted part-way through. As part of the update
>> one of my files needed to merge, since I was making changes to it it
>> was not read-only.
> <SNIP>
>> The svn cleanup command would not complete. The working copy was
>> stuck in a locked state. I could not properly update or commit....
>> So then I decided to be brave and poke around in the ".svn" folder to
>> see if I could make it go. Sort of like wacking a piece of high-tech
>> equipment on the side when it acts up - sometimes it works, sometimes
>> you just break it more :)
>> I broke it more.
>
> I also had this experience a few weeks ago, when copying files from a
> VSS working copy to my svn working copy and trying to commit. It
> failed in the same way. I went down the same path as you (remove
> read-only, try svn cleanup, poke around in .svn).
>
...
> The svn code should check if a file is read-only before attempting
> whatever it has to do for the commit, rather than plowing ahead,
> failing, and essentially breaking your WC.
On Oct 7, 2004, at 3:25 PM, Greg Goodrich wrote:
> I second this post. I too have done this. ... svn cleanup was of no
> use).
Well I was hoping one of the Subversion developers might have a
comment, but nothing so far. Should a bug report be filed on this?
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 9 00:29:56 2004