Re: Full CVS checkout?

ack too early in the morning....

less haste more heed,

might need to create a separate cvs lock directory, although toplevel
CVS seems t work without it...

try it now (it is chgrp -R proj_gpe)

On Wed, 2002-03-27 at 07:06, Robert Mibus wrote:
> Can anyone tell me why this[0] doesn't work? I can check individual
> modules but not the whole lot. ("-d .../cvs/gpe co html" works but not
> "-d .../cvs co gpe")
>
> It *did* work... before anything was in CVS except a README :)
>
> I'm guessing that /cvs/gpe is now an entire repository in itself, not a
> directory of /cvs? So should I then just c/o base/, html/, etc.?
yes

>
> Hmm, 'co base' doesn't work; same error as below. (failed to create lock
> dir...)

> It *may* be because /cvs/gpe/usqld is actually owned by occ.users, not
> occ.proj_gpe as (I assume) it should be.
>
> FWIW:
> [mibus_at_handhelds gpe]$ groups
> mibus cvswrite proj_gpe
>
>
> TIA,
> mibus
>
> ##[0]##
> mibus: ~/ipaq/cvs> cvs -d mibus_at_handhelds.org:/cvs co gpe
> cvs server: Updating .
> cvs server: Updating CVSROOT
> U CVSROOT/checkoutlist
> U CVSROOT/commitinfo
> U CVSROOT/config
> U CVSROOT/cvswrappers
> U CVSROOT/editinfo
> U CVSROOT/loginfo
> U CVSROOT/modules
> U CVSROOT/notify
> U CVSROOT/rcsinfo
> U CVSROOT/taginfo
> U CVSROOT/verifymsg
> cvs server: Updating base
> cvs server: failed to create lock directory for `/cvs/gpe/base'
> (/cvs/gpe/base/#cvs.lock): Permission denied
> cvs server: failed to obtain dir lock in repository `/cvs/gpe/base'
> cvs [server aborted]: read lock failed - giving up
> ####
>
> --
> Robert Mibus <mibus_at_bigpond.com>
> "...[Linux's] capacity to talk via any medium except smoke signals."
> (By Dr. Greg Wettstein, Roger Maris Cancer Center)
>
> _______________________________________________
> GPE mailing list
> GPE_at_handhelds.org
> http://handhelds.org/mailman/listinfo/gpe
>
>
Received on Wed Mar 27 2002 - 07:37:49 EST