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

Re: working copies problem on shared network drive

From: Jon Kloske <jkloske_at_itee.uq.edu.au>
Date: 2006-12-14 11:55:06 CET

Hi Lübbe,

> You could even run the svn up from a post-commit-hook if you are confident
> that all changes are right :)

Nice :) Sadly, the svn repo is located on another server - we access it via
the https method.

> IIRC, you can force group and user plus file/folder
> permissions for a samba share.

Yep, this is the way a lot of people seemed to be solving similarish issues,
though I also saw a lot of thinkers suggesting that it perhaps Wasn't
Right(tm) to be crippling these user based permission limits on filesystems
that support it, and anyway this is all to work around a non-supported
method of using svn working copies... :)

> Are you sure that 'Group' is the same for 'UserA' and 'UserB'? Is it
> possible that you are not in 'Group' when you access the share from
> windows?

Yeah, definitely the same. The group id is locked down in the samba confs,
and anyway, all the dirs are actually +s so they tend to leave the group and
write bits to Group and +w in a sticky fashion, even if you circumvent the
samba share and logon to the unix side of things directly.

> Now thats a real problem. What is their reason for not changing the flag?

I suspect they agree with the thinkers mentioned above, and to be fair to
them I don't feel their decision is wrong (though annoying for the purposes
of my crazy system.)

Thanks anyway for the great suggestions, they are much appreciated and at
least confirm I'm not missing something simple.

Cheers,
Jon.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Dec 14 12:22:04 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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