Shane, are you using the Lazarus login to CVS? That might be why you can get it and he can't. Maybe the cvs login doesn't have access to it? I bet it is a priviliges problem again for the cvs login. Can one of the FPC team check the priviliges of the mwedit directories and subdirectories please?

I tried it and it worked, so 1) try it again 2) if it doesn't work let us know. Then we'll know it's a permissions error and one of our folks can fix it. Shane >>> Chris Storah 10/27/99 08:11AM >>> Sorry, I mean to post this to the list rather than direct - wondered why I never got my own message back! The error message is : cvs -z3 checkout lazarus (in directory C:\TEST) cvs server: Updating lazarus cvs server: Updating lazarus/examples cvs server: Updating lazarus/lcl cvs server: Updating lazarus/lcl/components cvs server: Updating lazarus/lcl/components/mwedit cvs server: failed to create lock directory in repository `/FPC/CVS/fpc/lazarus/lcl/components/mwedit': Unknown error 18446744073709485823 cvs server: failed to obtain dir lock in repository `/FPC/CVS/fpc/lazarus/lcl/components/mwedit' cvs [server aborted]: read lock failed - giving up *****CVS exited normally with code 1***** Chris -----Original Message----- From: Shane Miller Sent: 27 October 1999 14:01 To: Subject: RE: [lazarus] CVS : problem getting components level of lazerus What message are you getting? It seemed to pull correctly for me this morning. I can't compile due to other issues, but it pulled correctly from CVS. You get any error message you could pass along? Shane >>> Chris Storah 10/27/99 07:29AM >>> I now have access to the components level, but it is failing on the wmedit level under components. Is this the same permission problem, or is it a setting in CVS that I need to set? Chris. -----Original Message----- From: Michael Van Canneyt Sent: 27 October 1999 08:51 To: Subject: Re: [lazarus] CVS : problem getting components level of lazerus On Tue, 26 Oct 1999, Curtis White wrote: > 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? No it doesn't. At the moment, the only way to solve this is to telnet to the machine, and fix the permissions manually. I'll see if I can have this automated. Michael. > > > 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. > > > > _________________________________________________________________ > To unsubscribe: mail with > "unsubscribe" as the Subject > archives at http://www.miraclec.com/list_archives/lazarus > _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus