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

Betr.: Subversion working copy via Samba

From: Jan Keirse <jan.keirse_at_tvh.be>
Date: Fri, 7 Oct 2011 10:08:19 +0200

Dalibor Karloviæ <dado_at_burza.hr> schreef op 07/10/2011 09:52:01:

> Hello,
>
> 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?
 
> Also, I'd like to note that this same mail was sent to Samba's list as I

> can't yet figure out is this a Samba or SVN issue.

It's Subversion.
 
> 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.

> - 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.

 
> Now, I get most of it done:
> - I login via SSH and do a checkout
> - access the share via Samba (Linux, Fedora 14), it works
> - can commit/update/delete on either side, no issues

That's just coincidence, it may fail with the next version of SVN.
 
> 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 ;-)
 
> and from then on, the working copy is so badly damaged (locked, missing
> files/directories), etc. that I haven't found a way to fix it.
>
> Examining the permissions on the file in question, it seems Subversion
sets
> the access mode to r--r--r-- as to avoid tampering (?) and the Windows
> client isn't able to change it. The other reason might be that one user
is
> changing the file another user owns, but they're in the same group.
>
> So, my question is: is there anybody out there who has a similar setup
which
> in fact runs OK? Also, am I missing something obvious here (except for
the
> weird SVN usage pattern)?
 

Working copies are platform dependant. You should only ever access them
with one platform. You can use different clients (ie TortoiseSVN and
svn.exe) but they have to be on the same platform.

Kind Regards,

JAN KEIRSE
ICT-DEPARTMENT
Software quality & Systems: Software Engineer

**** DISCLAIMER ****

http://www.tvh.com/newen2/emaildisclaimer/default.html

"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."
Received on 2011-10-07 10:07:36 CEST

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

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