cvs problem - Mailing list pgsql-hackers

From Patrick Welche
Subject cvs problem
Date
Msg-id 20030723121156.E20649@quartz.newn.cam.ac.uk
Whole thread Raw
Responses Re: cvs problem
List pgsql-hackers
cvs server: Updating src/bin/scripts/po
cvs server: failed to create lock directory for `/projects/cvsroot/pgsql-server/src/bin/scripts/po'
(/projects/cvsroot/pgsql-server/src/bin/scripts/po/#cvs.lock):Permission denied
 
cvs server: failed to obtain dir lock in repository `/projects/cvsroot/pgsql-server/src/bin/scripts/po'
cvs [server aborted]: read lock failed - giving up


On a different note, I also wonder about:

M src/backend/parser/gram.c

It seems that you checkout the source with no gram.c. Build it, thus creating
gram.c. Next time you cvs update, you get Attic/gram.c merged in :/ - or is
my use of cvs incorrect? (cvs -z3 update -P -d)

Cheers,

Patrick


pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: Re: [PATCHES] Czech NLS
Next
From: "Paulo Scardine"
Date:
Subject: Re: SELECT FOR UPDATE NOWAIT