On Aug 22, 2005, at 1:10 AM, Ryan Schmidt wrote:
>
> On 13.08.2005, at 01:18, Sander Cox wrote:
>
>
>> I just setup an Apache2 server for WebDav with SVN. I can read the
>> contents of the repository just fine but when I try to add some
>> new file I get an error in my apache 2 log an my Mac starts
>> complaining:
>>
>> [Sat Aug 13 01:12:05 2005] [error] [client 10.0.2.216] Failed to
>> create new lock. [500, #1]
>> [Sat Aug 13 01:12:05 2005] [error] [client 10.0.2.216] Can't chmod
>> '/Storage/subversion/db/locks/aeb': Operation not permitted [500,
>> #1]
>> [Sat Aug 13 01:12:06 2005] [error] [client 10.0.2.216] Failed to
>> create new lock. [500, #1]
>> [Sat Aug 13 01:12:06 2005] [error] [client 10.0.2.216] Can't chmod
>> '/Storage/subversion/db/locks/c72': Operation not permitted [500,
>> #1]
>>
>> The /Storage/subversion/db/locks directory has 777 chmod
>> permissions and is owned by the account of the webserver so I
>> don't know why it would want to be running chmod on the file and
>> have absolutely no idea why it is complaining it isn't allowed to
>> change the permissions on the file.
>>
>> I'm using apache2.0.54, subversion 1.2.1 and Mac OS X 10.4.2
>>
>
> What is /Storage? Sounds like it's not a local volume but rather
> something like a Samba share or AppleShare volume, where commands
> like chmod may not work so well. Can that be? People here often
> talk of storing repositories on NFS, which I've heard works fine,
> as long as the repository is FSFS and not BDB, but I've not heard
> of anyone trying Samba or AppleShare, if that's what you're doing.
It's just how I called the directory on the system, it's not a
special mount point for anything.
>> Furthermore I see that Mac OS X is writing the resource
>> forks ._xxx files as well. Would it be possible to prevent this
>> from happening as I don't see need for these files for 90% of the
>> files that are going to be checked into subversion.
>
> I assume we're talking about a working copy here. Mac OS X only
> creates the "AppleDouble" ._ files on file systems that do not
> natively support multiple forks. AFAIK you cannot prevent Mac OS X
> from doing so. But if you use a Mac file system like HFS+ for your
> working copy, then the resource fork will be stored as a fork of
> the file, and no separate ._ file will be created. When you check
> in, only the data fork will be transmitted.
>
> At work, I need to have my working copies on a Samba share, so I
> see ._ files all the time. I mentally ignore them in file listings
> on the command line, and tell Subversion to ignore them too. Works
> fine.
No I'm talking about the direct WebDAV usage of Mac OS X. When you do
a "Apple+K" in the Finder you can enter the https://...../svn-
repository/" and directly browse over the copy of your repository.
Whenever you drag-and-drop a file to this WebDAV mount point, Mac OS
X tries to make two files in the SVN repository and then the above
errors appear and Mac OS X tells me something went wrong.
Best regards,
Sander Cox
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 22 07:57:43 2005