On 10/24/07, Jay Levitt <lists-subclipse@shopwatch.org> wrote:
> This is not a bug report, because it's way too vague to be a bug report.
> It's a pre-bug report.
>
> I was creating a Rails plugin yesterday, and I had to move a bunch of
> files and folders around a few times, all within Eclipse. At some
> point, the WC became corrupted beyond cleanup's ability to fix things
> (either Subclipse or command line); there were locked .svn/entries files
> with a setguid bit set. I eventually had to manually copy all the
> source files to a newly created directory, and sudo rm -rf the old stuff.
>
> This is with Subclipse 1.2.4 against a 1.4.4 server.
>
> I seem to remember that (a) this is known, and caused by moves not being
> atomic, and that (b) 1.5 improves things somewhat.
>
> If that's *not* the case, let me know and I'll find a failure recipe...
Yes, that is the case. It is not because of the atomic moves though
(that feature still has not been implemented). This bug was just an
artificial limitation that Subversion carried around in its client
API's. It did not allow something to be moved twice without a commit.
This also manifests as not allowing a folder to be renamed, and then
files in the folder also renamed. We try to work around the
limitations in Subclipse but it is not hard to get to a point where it
can't handle it anymore.
1.5 fixes all of this.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Oct 24 16:01:16 2007