Re: Betr.: Subversion working copy via Samba

Jan Keirse wrote:

>> I don't know is this a Samba or Subversion (or my faulty config) related
>
>> issue so I'll start here. I'd like to clarify that the need to have just
> one
>> working copy (and not one per user on his/her local disk) is vital here.
>
> Can we know why?

Sure, I'll lay it out:
- we're a small web development studio
- we have a development server which exposed one share to the team via Samba
- if we're developing a new site called foo.com, we create a working copy on
the server and make it available as foo.com.web in our local domain which
makes it accessible from each workstation right away
- this gives us a point to which anybody working on the site can hook up to
and we all can see exactly what's going on at any point in time
- also, the less tech-savy guys/gals (designers, copywriters, PMs) don't
need to setup their own entire work environment (server, database, virtual
hosts, etc), they just open the share and a browser and start working.
- we cannot automate the procedure because there's alot of different systems
on staff (WinXP, Win7, MacOSX, Fedora, Ubuntu, etc).

The one "working copy per user" has too high of a (time) cost here.

>> Target:
>> - check out a working copy to this directory
>> - allow only members of @Production to access it
>> - allow various Subversion clients to be used via Samba on the working
> copy
>
> Then do the checkout from the client.

Same thing, sadly. Subversion is changing my preset permissions and ruining
my working copies. :(

>> - allow for using SVN directly on the server (not via Samba, MUCH faster
> for
>> large operations like checkout) without the need to fix permissions
>> afterward (seamlessly)
>
> No, impossible. Working copies are platform dependant. Either always
> access them from windows or always access them from linux.
> If it occasionally work it's coincidence, it may fail tomorrow.

Actually, we've been working like that for years and it worked great as long
as the minor version of all the clients accessing it is the same, as soon as
the WC is upgraded, we all need to upgrade.

How we had it setup was up to now was:
- set perms for files to one user:group combo (say, developer:production)
- force user developer, force group production in Samba

and that worked, except you couldn't just go the the WC on the server itself
and run SVN commands w/o breaking permissions / working copy. Now I have the
exact opposite, it works on the server, not via Samba.

>> But, as soon as my co-worker on Win7/TortoiseSVN deleted a file (via
> Samba),
>> he gets (Q:\ points to this share):
>>
>> Commit succeeded, but other errors follow:
>> Error bumping revisions post-commit (details follow):
>> In directory 'Q:\webs\<censored>\trunk\images'
>> Error processing command 'committed' in
> 'Q:\webs\<censored>\trunk\images'
>> Can't set file
>>
> 'Q:\webs\<censored>\trunk\images\.svn\prop-base\avatar_small.png.svn-base'
>
>> read-write: Access is denied.
>
> See it can't work ;-)

Yeah :) that's why I'm here, I'm thinking there must be a way to do this.

Thanks for your reply.

-- 
Dado