Re: CVS server problem!

From: Greg Copeland <greg(at)CopelandConsulting(dot)Net>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CVS server problem!
Date: 2002-08-01 22:26:58
Message-ID: 1028240819.3112.79.camel@mouse.copelandconsulting.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Seems the CVS server is not working correctly. I just deleted my CVS
tree and did a fresh checkout of the pgsql module. Everything seemingly
went well. After the check out completed, I did:

[gcope(at)mouse pgsql]$ ./configure --with-tcl --with-java --with-python
--with-perl
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking which template to use... linux
checking whether to build with 64-bit integer date/time support... no
checking whether to build with recode support... no
checking whether NLS is wanted... no
checking for default port number... 5432
checking for default soft limit on number of connections... 32
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
./configure: ./src/template/linux: No such file or directory

So, I did, "./configure" which yields the same result. So, thinking
maybe I just had a poorly timed checkout, I did an update. Doing so,
looks like this:
[gcope(at)mouse pgsql]$ cvs -z3 update -dP
? config.log
cvs server: Updating .
cvs server: Updating ChangeLogs
cvs server: Updating MIGRATION
cvs server: Updating config
.
.
.
src/backend/utils/mb/conversion_procs/utf8_and_iso8859_1
cvs server: Updating
src/backend/utils/mb/conversion_procs/utf8_and_johab
cvs server: Updating src/backend/utils/mb/conversion_procs/utf8_and_sjis
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_sjis: No such file or directory
cvs server: skipping directory
src/backend/utils/mb/conversion_procs/utf8_and_sjis
cvs server: Updating src/backend/utils/mb/conversion_procs/utf8_and_tcvn
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_tcvn: No such file or directory
cvs server: skipping directory
src/backend/utils/mb/conversion_procs/utf8_and_tcvn
cvs server: Updating src/backend/utils/mb/conversion_procs/utf8_and_uhc
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_uhc: No such file or directory
cvs server: skipping directory
src/backend/utils/mb/conversion_procs/utf8_and_uhc
cvs server: Updating src/backend/utils/misc
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/misc: No such file or
directory
cvs server: skipping directory src/backend/utils/misc
cvs server: Updating src/backend/utils/mmgr
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mmgr: No such file or
directory
cvs server: skipping directory src/backend/utils/mmgr
cvs server: Updating src/backend/utils/sort
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/sort: No such file or
directory
cvs server: skipping directory src/backend/utils/sort
cvs server: Updating src/backend/utils/time
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/time: No such file or
directory
cvs server: skipping directory src/backend/utils/time
cvs server: Updating src/bin
cvs server: cannot open directory /projects/cvsroot/pgsql/src/bin: No
such file or directory
cvs server: skipping directory src/bin

So, I'm fairly sure something is awry.

Greg

On Mon, 2002-07-29 at 20:51, Tatsuo Ishii wrote:
> Can anyone fix this?
>
> $ cvs up
> can't create temporary directory /tmp/cvs-serv40296
> No space left on device
> --
> Tatsuo Ishii
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2002-08-01 22:27:13 Re: Trimming the Fat, Part Deux ...
Previous Message Bruce Momjian 2002-08-01 22:25:52 Re: FUNC_MAX_ARGS benchmarks