<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.16.1">
</HEAD>
<BODY>
you must do chmod g+s sites/elk to preserver the group ownership. However, the openssh daemon will not respect this so the sftp:// protocol will not work, the bzr+ssh protocol handles this correctly.<BR>
<BR>
//Mattias<BR>
<BR>
<BR>
lör 2008-03-08 klockan 22:16 +0000 skrev Thomas Nichols:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Hi,</FONT>
<FONT COLOR="#000000">I'm moving a bunch of projects from svn to bzr, and really like it -- </FONT>
<FONT COLOR="#000000">but have a permissions problem.</FONT>
<FONT COLOR="#000000">I set the repo to be g+w on everything -- and I have a cron script that </FONT>
<FONT COLOR="#000000">commits to this repo as user carriebot group carriebot, these being the </FONT>
<FONT COLOR="#000000">user and group who own all files in the repo. All works sweetly, until I </FONT>
<FONT COLOR="#000000">make a change to the repo from my dev machine, committing to the server as</FONT>
<FONT COLOR="#000000">thomasn:users</FONT>
<FONT COLOR="#000000">User thomasn on the server is in the carriebot group, so can write to </FONT>
<FONT COLOR="#000000">the repo -- but the _default_ group for thomasn is 'users', and when I </FONT>
<FONT COLOR="#000000">commit from my dev machine over ssh to the server I get the following in </FONT>
<FONT COLOR="#000000">the server repo:</FONT>
<FONT COLOR="#000000"># ls -la sites/elk/.bzr/branch</FONT>
<FONT COLOR="#000000">total 24</FONT>
<FONT COLOR="#000000">drwxrwx--- 3 carriebot carriebot 4096 Mar 8 21:50 .</FONT>
<FONT COLOR="#000000">drwxrwx--- 6 carriebot carriebot 4096 Feb 2 21:32 ..</FONT>
<FONT COLOR="#000000">-rwxrwx--- 1 carriebot carriebot 65 Feb 3 00:32 branch.conf</FONT>
<FONT COLOR="#000000">-rwxrwx--- 1 carriebot carriebot 34 Feb 2 21:32 format</FONT>
<FONT COLOR="#000000">-rw-rw---- 1 thomasn users 54 Mar 8 21:50 last-revision</FONT>
<FONT COLOR="#000000">drwxrwx--- 2 carriebot carriebot 4096 Mar 8 21:50 lock</FONT>
<FONT COLOR="#000000">-rwxrwx--- 1 carriebot carriebot 0 Feb 2 21:32 tags</FONT>
<FONT COLOR="#000000">... so .bzr/branch/last-revision is now owned by thomasn:users, and </FONT>
<FONT COLOR="#000000">(unsurprisingly) the cron scripts can no longer use the repo.</FONT>
<FONT COLOR="#000000">I've tried using both sftp:// and bzr+ssh:// protocols, same issue.</FONT>
<FONT COLOR="#000000">How are other people tackling this? Is there a daemon bzr-server I could </FONT>
<FONT COLOR="#000000">leave running, so that thomasn:users could issue client requests to this </FONT>
<FONT COLOR="#000000">server (and the server process would be the only one making filesystem </FONT>
<FONT COLOR="#000000">changes to the repo)? Is the only solution to commit from my dev box as </FONT>
<FONT COLOR="#000000">user carriebot? Or is this workflow better supported by a different </FONT>
<FONT COLOR="#000000">approach?</FONT>
<FONT COLOR="#000000">Any suggestions would be most welcome.</FONT>
<FONT COLOR="#000000">Regards,</FONT>
<FONT COLOR="#000000">Thomas.</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>