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

Re: [Subclipse-users] Client too old error on OS X

From: Hugo Visser <joegi_at_scene.nl>
Date: 2006-11-12 14:26:21 CET

Hi Kristian,

I'm on OS X too, and tried this:

Eclipse 3.2 with Subclipse 1.1.7, checked out a project from the
repository.
Did a commit to verify the working copy is ok.

Then upgraded to Subclipse 1.1.8. Restarted Eclipse, working copy is
not updated when Eclipse is just restarted. After an update the
working copy is converted, permissions look ok on the .svn dirs and
the files in there.

Then I deleted the project, reverted to 1.1.7 and checked out the
project again.
Switched back to 1.1.8, did a commit, without updating first, the
working copy is still in 1.3 format (is that correct behaviour?).
Then I updated again, causing the working copy version to be
upgraded. Performed another commit, all seems to be ok.

Only difference is that my repository is not using svn+ssh, but http.
Also the server is subversion 1.2. I don't think that this should
matter, aparently something went wrong either when importing your
existing projects or when upgrading the working copy. I can't really
imagine that JavaSVN would screw up the file permissions, because you
can't control those from Java (yet).

If you have some other things you'd like me to test, let me know. In
general if anything related to subclipse needs to be tested on os x,
I'd be happy to test it.

Hugo

On Nov 12, 2006, at 1:03 PM, Kristian Duske wrote:

> Hi again,
>
> I just checked tried to delete one of my legacy projects, and
> Eclipse threw errors that it could not delete the files and
> directories that contain the SVN meta data. I checked the
> permissions and found that the meta data files are not writable -
> to anyone. They are only readable. So that is probably where all
> these problems come from.
>
> I couldn't even change the permissions on those files as root.
> That's odd. I wonder how this happened. So I guess the problem is
> solved, but the question remains whether Subclipse is responsible
> for fucking up the file permissions like that. Any ideas?
>
> Regards
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Nov 12 14:26:35 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.