Re: cvs problem

try it now ... I think its a pathing problem with a cron entry ... just
fixed that, so should be okay now ...

On Wed, 23 Jul 2003, Patrick Welche wrote:

> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org