On Fri, Nov 21, 2008 at 6:25 AM, Allan McRae <[EMAIL PROTECTED]> wrote:
> Firmicus wrote:
>>
>> Simo Leone a écrit :
>>>
>>> Hey guys,
>>>
>>> During the server changes today, the path to the community CVS tree
>>> changed. In order to make your existing checkouts work again, please
>>> run the following at the root of your CVS checkout:
>>>
>>> find . -path '*CVS/Root' -exec sed -i
>>> 's#/home/cvs-community#/srv/cvs/cvs-community#g' {} ';'
>>>
>>> CVS will ask you to re-login if you had your credentials saved, due to
>>> the change in path. In addition, CVS may not be available until tomorrow
>>> morning due to permissions issues with the CVS lock directory, as soon
>>> as someone with sudo wakes up, this should be fixed.
>>>
>>> -S
>>>
>>> PS: There is a whole slew of documentation about the AUR that now needs
>>> updating for the new path, anyone that wants to tackle this gets a
>>> hundred gold stars and a bunch of thank-you's.
>>>
>>
>> Thanks for that Simo.
>>
>> But I still can't do a checkout:
>> $cvs -q co -P community
>> cvs checkout: failed to create lock directory for
>> `/srv/cvs/cvs-community/CVSROOT' (/var/lock/cvs/CVSROOT/#cvs.history.lock):
>> Permission denied
>> cvs checkout: failed to obtain history lock in repository
>> `/srv/cvs/cvs-community'
>> cvs checkout: failed to create lock directory for
>> `/srv/cvs/cvs-community/community' (/var/lock/cvs/community/#cvs.lock):
>> Permission denied
>> cvs checkout: failed to obtain dir lock in repository
>> `/srv/cvs/cvs-community/community'
>> cvs [checkout aborted]: read lock failed - giving up
>>
>> Did I miss something?
>>
>
> I don't think so... Looking on the server, the lock directories need
> permissions changed.
I think /var/lock is fine. I set /var/lock/cvs to g+w (done recursively too)
Can someone check again?
