[lazarus] CVS : problem getting components level of lazerus

[Curtis White]

Is there something that I should have done different when I created the
directories and files that would prevent these problems? Do I need to set their
permissions before I add them to CVS? Or would that make any difference?


Thanks...Curtis

On 25-Oct-99 Michael Van Canneyt wrote:
> 
> 
> On Sun, 24 Oct 1999, Florian Klaempfl wrote:
> 
>> > Chris Storah wrote:
>> > 
>> > I have managed to get CVS working to a certain point (it fetches most of
>> > the code)...
>> > apart from the components level of lazerus. Does anyone have any ideas why
>> > it should
>> > fail at this point? - the following is the last few lines of the CVS
>> > result pane
>> > (running under Win98).
>> > 
>> > U lazarus/lcl/win32object.inc
>> > U lazarus/lcl/wincontrol.inc
>> > U lazarus/lcl/windows.pp
>> > cvs server: Updating lazarus/lcl/components
>> > cvs server: failed to create lock directory in repository
>> > `/FPC/CVS/fpc/lazarus/lcl/components': Unknown error 18446744073709485823
>> > cvs server: failed to obtain dir lock in repository
>> > `/FPC/CVS/fpc/lazarus/lcl/components'
>> > cvs [server aborted]: read lock failed - giving up
>> > 
>> > Cheers, Chris.
>> > 
>> > 
>> 
>> Someone didn't fix the CVS directory permissions.
>> 
>> BTW Michael, why is fixperms permission on idefix 444 (instead of at least
>> 554)?
> 
> ?? it is 777 for directories and 444 for files. CVS can handle this.
> 554 is of course wrong: that would be r-xr-xr-- instead of 664 rw-rw-r-- :-)
> 
> CVS uses the directory permissions to decide access.
> 
> Michael. 
>