> Have you read the last section in chapter 6, and gone down the
> svn+ssh:// checklist?
I skipped that section, because it is entitled "supporting multiple
access methods" and I only have one access method. Since you are the
author, I hope it would not be out of place to suggest renaming the
section :)
http://svnbook.red-bean.com/svnbook/ch06s03.html#svn-ch-6-sect-3.3
I have followed the first step of the checklist, but I thought the
other parts were disconcerting. Since I am using a FreeBSD install, if
I were to move the binary file for svnserve, it would disable me from
portupgrading it. As far as I know, on most UNIXes, moving the binary
will upset the upgrading process, or at least end up getting your
script replaced with the upgrade.
If you look at my previous email again, you will see that SVN creates
broken permissions on its own, out of the box. I didn't go in there and
tell berkeley DB to 'chmod g-w log.*' :-D
The current permissions and access system is very confusing to those
who are developers, not unix sysadmin gurus. As it is, svn+ssh does not
work correctly out of the box. Why does it work the way it currently
does (that is, designed to ignore that it needs some type of umask
intervention), and is there change in the wind? Do I have to do the
somewhat dodgy umask shuffle, or is there another way?
- paul
On May 26, 2004, at 11:53 AM, Ben Collins-Sussman wrote:
> On Wed, 2004-05-26 at 10:17, Paul Oppenheim wrote:
>> Hello SVN'ers,
>>
>> I'm having a problem with an SVN 1.0.2 repository that is living on a
>> FreeBSD 5.2 server. My team's repository is administered by a user
>> named 'svn' and has a group of 'Proto2004'. Two users that are also in
>> group 'Proto2004' are 'poppenhe' and 'woodardj'. When user 'poppenhe'
>> makes a commmit, user 'woodardj' cannot then use the repository.
>>
>> I've examined the repository, and the problem seems to be a
>> permissions
>> problem. The only time the permissions were manually modified was when
>> the repository was created. After creation, I did a 'chown -RP
>> svn:Proto2004 haquery/' to make the repository accessible to the users
>> of the group. Is that incorrect? The access method is restricted to
>> svn+ssh.
>
> Have you read the last section in chapter 6, and gone down the
> svn+ssh:// checklist?
>
> http://svnbook.red-bean.com/svnbook/ch06s05.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 26 21:49:16 2004