
... is once more 'normal' ...

there are three modules right now setup:

earthdistance
libpqxx
pgsql-server

pgsql combines all three of the above to transparently give the equivalent
of the whole distribution from its component parts ...




Thu, 1 Aug 2002 10:24:09 -0300 (ADT)
"Marc G. Fournier" <scrappy@hub.org>
cvs checkout pgsql 
Marc G. Fournier wrote:
> 
> ... is once more 'normal' ...
> 
> there are three modules right now setup:
> 
> earthdistance
> libpqxx
> pgsql-server
> 
> pgsql combines all three of the above to transparently give the equivalent
> of the whole distribution from its component parts ...

Marc, I have to ask, why did you split them up that way.  I thought
/contrib, /interfaces, /doc would be the way to go.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Thu, 1 Aug 2002 13:45:20 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: cvs checkout pgsql
"Marc G. Fournier" <scrappy@hub.org> writes:
> ... is once more 'normal' ...

Uh, it's completely broken as far as I can tell.

$ pwd
/home/postgres/pgsql/src/bin/pg_dump
$ cvs status
cvs server: Examining .
cvs server: failed to create lock directory for `/cvsroot/pgsql/src/bin/pg_dump'
 (/cvsroot/pgsql/src/bin/pg_dump/#cvs.lock): No such file or directory
cvs server: failed to obtain dir lock in repository `/cvsroot/pgsql/src/bin/pg_dump'
cvs [server aborted]: read lock failed - giving up
$

Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.

This makes it a little difficult to get any work done :-(

			regards, tom lane

Thu, 01 Aug 2002 14:41:10 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: cvs checkout pgsql 
Tom Lane wrote:
> "Marc G. Fournier" <scrappy@hub.org> writes:
> > ... is once more 'normal' ...
> 
> Uh, it's completely broken as far as I can tell.
> 
> $ pwd
> /home/postgres/pgsql/src/bin/pg_dump
> $ cvs status
> cvs server: Examining .
> cvs server: failed to create lock directory for `/cvsroot/pgsql/src/bin/pg_dump'
>  (/cvsroot/pgsql/src/bin/pg_dump/#cvs.lock): No such file or directory
> cvs server: failed to obtain dir lock in repository `/cvsroot/pgsql/src/bin/pg_dump'
> cvs [server aborted]: read lock failed - giving up
> $
> 
> Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.
> 
> This makes it a little difficult to get any work done :-(

Yes, I just deleted my CVS tree and re-checked out.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Thu, 1 Aug 2002 14:41:54 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: cvs checkout pgsql
On Thu, 1 Aug 2002, Tom Lane wrote:

> "Marc G. Fournier" <scrappy@hub.org> writes:
> > ... is once more 'normal' ...
>
> Uh, it's completely broken as far as I can tell.
>
> $ pwd
> /home/postgres/pgsql/src/bin/pg_dump
> $ cvs status
> cvs server: Examining .
> cvs server: failed to create lock directory for `/cvsroot/pgsql/src/bin/pg_dump'
>  (/cvsroot/pgsql/src/bin/pg_dump/#cvs.lock): No such file or directory
> cvs server: failed to obtain dir lock in repository `/cvsroot/pgsql/src/bin/pg_dump'
> cvs [server aborted]: read lock failed - giving up
> $
>
> Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.
>
> This makes it a little difficult to get any work done :-(

I made a large change this morning based on a comment by Thomas ... the
way I *had* it was to get the whole thing, you had to checkout pgsql-all
... Thomas suggested leaving it as pgsql, with pgsql-server being 'the
base', but in order to do that, I had to move the pgsql repository to
pgsql-server, since otherwise modules makes it recursive on my ... its a
'one time only change', but it requires a fresh checkout to get the
patches in properly ... same thing that I explained yesterday about how
you'll get a 'No such file or directory' is you tried to update, say,
libpqxx, since its path is no longer
/cvsroot/pgsql/src/interfaces/libpqxx, but is /cvsroot/interfaces/libpqxx
... the fact that its different modules is transparent to the programmer
*unless*, of course, its already checked out at the tiem :(

 Script started on Thu Aug  1 15:15:48 2002
> setenv CVSROOT /cvsroot
> cvs -q checkout -P pgsql
U pgsql/COPYRIGHT
U pgsql/GNUmakefile.in
U pgsql/HISTORY
U pgsql/INSTALL
<alot of lines deleted>
U pgsql/src/interfaces/libpqxx/test/test5.cxx
U pgsql/src/interfaces/libpqxx/test/test6.cxx
U pgsql/src/interfaces/libpqxx/test/test7.cxx
U pgsql/src/interfaces/libpqxx/test/test8.cxx
U pgsql/src/interfaces/libpqxx/test/test9.cxx
> cd pgsql/src/bin/pg_dump
cvs s> cvs status
cvs status: Examining .
===================================================================
File: Makefile          Status: Up-to-date

   Working revision:    1.36    Sat Jul 27 20:10:05 2002
   Repository revision: 1.36    /cvsroot/pgsql-server/src/bin/pg_dump/Makefile,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

===================================================================
File: README            Status: Up-to-date

   Working revision:    1.5     Fri Jul 21 11:40:08 2000
   Repository revision: 1.5     /cvsroot/pgsql-server/src/bin/pg_dump/README,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

<alot more lines deleted>

===================================================================
File: zh_CN.po          Status: Up-to-date

   Working revision:    1.5     Mon Dec 10 18:45:57 2001
   Repository revision: 1.5     /cvsroot/pgsql-server/src/bin/pg_dump/zh_CN.po,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

===================================================================
File: zh_TW.po          Status: Up-to-date

   Working revision:    1.3     Thu Nov 29 18:59:28 2001
   Repository revision: 1.3     /cvsroot/pgsql-server/src/bin/pg_dump/zh_TW.po,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

> exit
exit

Script done on Thu Aug  1 15:16:51 2002



Thu, 1 Aug 2002 16:22:31 -0300 (ADT)
"Marc G. Fournier" <scrappy@hub.org>
Re: cvs checkout pgsql 
On Thu, 1 Aug 2002, Tom Lane wrote:

> "Marc G. Fournier" <scrappy@hub.org> writes:
> > ... is once more 'normal' ...
>
> Uh, it's completely broken as far as I can tell.
>
> $ pwd
> /home/postgres/pgsql/src/bin/pg_dump
> $ cvs status
> cvs server: Examining .
> cvs server: failed to create lock directory for `/cvsroot/pgsql/src/bin/pg_dump'
>  (/cvsroot/pgsql/src/bin/pg_dump/#cvs.lock): No such file or directory
> cvs server: failed to obtain dir lock in repository `/cvsroot/pgsql/src/bin/pg_dump'
> cvs [server aborted]: read lock failed - giving up
> $
>
> Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.
>
> This makes it a little difficult to get any work done :-(

What'r you typin about?  It works fine.   Ok, ok.. It does *NOW*. :)
There's probably still stuff that's broke that I haven't discovered
yet.

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev@michvhf.com    http://www.pop4.net
         56K Nationwide Dialup from $16.00/mo at Pop4 Networking
        Online Campground Directory    http://www.camping-usa.com
       Online Giftshop Superstore    http://www.cloudninegifts.com
==========================================================================




Thu, 1 Aug 2002 15:33:23 -0400 (EDT)
Vince Vielhaber <vev@michvhf.com>
Re: cvs checkout pgsql 
On Thu, 2002-08-01 at 15:33, Vince Vielhaber wrote:
> On Thu, 1 Aug 2002, Tom Lane wrote:
> 
> > "Marc G. Fournier" <scrappy@hub.org> writes:
> > > ... is once more 'normal' ...
> >
> > Uh, it's completely broken as far as I can tell.
> >
> > $ pwd
> > /home/postgres/pgsql/src/bin/pg_dump
> > $ cvs status
> > cvs server: Examining .
> > cvs server: failed to create lock directory for `/cvsroot/pgsql/src/bin/pg_dump'
> >  (/cvsroot/pgsql/src/bin/pg_dump/#cvs.lock): No such file or directory
> > cvs server: failed to obtain dir lock in repository `/cvsroot/pgsql/src/bin/pg_dump'
> > cvs [server aborted]: read lock failed - giving up
> > $
> >
> > Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.
> >
> > This makes it a little difficult to get any work done :-(
> 
> What'r you typin about?  It works fine.   Ok, ok.. It does *NOW*. :)
> There's probably still stuff that's broke that I haven't discovered
> yet.

Well, of course that specific URL doesn't work  because it's actually
pgsql-server.


01 Aug 2002 15:48:22 -0400
Rod Taylor <rbt@zort.ca>
Re: cvs checkout pgsql
Rod Taylor <rbt@zort.ca> writes:
> Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.
>> 
>> What'r you typin about?  It works fine.   Ok, ok.. It does *NOW*. :)

> Well, of course that specific URL doesn't work  because it's actually
> pgsql-server.

Well, it did work before, and I'd really like it to work again.  I do
not want to think about how Marc's broken apart the distribution when
I'm looking at my local tree, and I don't want to think about it when
I'm looking at cvsweb either.

			regards, tom lane

Thu, 01 Aug 2002 15:53:44 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: cvs checkout pgsql 
On 1 Aug 2002, Rod Taylor wrote:

> On Thu, 2002-08-01 at 15:33, Vince Vielhaber wrote:
> > On Thu, 1 Aug 2002, Tom Lane wrote:
> >
> > > "Marc G. Fournier" <scrappy@hub.org> writes:
> > > > ... is once more 'normal' ...
> > >
> > > Uh, it's completely broken as far as I can tell.
> > >
> > > $ pwd
> > > /home/postgres/pgsql/src/bin/pg_dump
> > > $ cvs status
> > > cvs server: Examining .
> > > cvs server: failed to create lock directory for `/cvsroot/pgsql/src/bin/pg_dump'
> > >  (/cvsroot/pgsql/src/bin/pg_dump/#cvs.lock): No such file or directory
> > > cvs server: failed to obtain dir lock in repository `/cvsroot/pgsql/src/bin/pg_dump'
> > > cvs [server aborted]: read lock failed - giving up
> > > $
> > >
> > > Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.
> > >
> > > This makes it a little difficult to get any work done :-(
> >
> > What'r you typin about?  It works fine.   Ok, ok.. It does *NOW*. :)
> > There's probably still stuff that's broke that I haven't discovered
> > yet.
>
> Well, of course that specific URL doesn't work  because it's actually
> pgsql-server.

But the developer's web page is updated with the new info.

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev@michvhf.com    http://www.pop4.net
         56K Nationwide Dialup from $16.00/mo at Pop4 Networking
        Online Campground Directory    http://www.camping-usa.com
       Online Giftshop Superstore    http://www.cloudninegifts.com
==========================================================================




Thu, 1 Aug 2002 16:00:12 -0400 (EDT)
Vince Vielhaber <vev@michvhf.com>
Re: cvs checkout pgsql
On Thu, 1 Aug 2002, Tom Lane wrote:

> Rod Taylor <rbt@zort.ca> writes:
> > Also, http://developer.postgresql.org/cvsweb.cgi/pgsql/ isn't working.
> >>
> >> What'r you typin about?  It works fine.   Ok, ok.. It does *NOW*. :)
>
> > Well, of course that specific URL doesn't work  because it's actually
> > pgsql-server.
>
> Well, it did work before, and I'd really like it to work again.  I do
> not want to think about how Marc's broken apart the distribution when
> I'm looking at my local tree, and I don't want to think about it when
> I'm looking at cvsweb either.

You don't have to think about anything ... god, does *nobody* read what
they are replying to??

if you do a cvs checkout of pgsql, you will get exactly what you are used
to ... you can update, commit, look at status, look at logs, etc ... cvs
itself is setup to handle pulling in and placing the required modules when
you do the checkout of pgsql ...

I could move docs into $CVSROOT/this/is/a/stupid/directory/structure/docs
and except for the fact that you already have a copy checked out pointing
to the old path, a fresh checkout would still place that in pgsql/docs,
where you've grown used to it being ...




Thu, 1 Aug 2002 18:12:16 -0300 (ADT)
"Marc G. Fournier" <scrappy@hub.org>
Re: cvs checkout pgsql 
Looks like I replied to the wrong thread...here's a repeat...

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@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@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

Unrelated quote:
> I could move docs into $CVSROOT/this/is/a/stupid/directory/structure/docs
> and except for the fact that you already have a copy checked out pointing
> to the old path, a fresh checkout would still place that in pgsql/docs,
> where you've grown used to it being ...
> 

You do realize that by moving modules outside of the base project,
you're forcing more work for the masses.  That is, if you plan to have
/doc, /pgsql-server, /contrib, etc, people will now have to create a new
.../pgsql directory locally which means, locally, people will have
.../pgsql/pgsql-server, .../pgsql/contrib, etc...why force onto the
developer what CVS should already be doing it.  I don't know about you
guys, but when I check out pgsql, I certainly expect everything to be
there.  If that's not what I want, then I should be more explicate in
what I pick for checkout.

Just some food for thought...this is a common peeve of mine when people
decide they need to restructure their repository...seems like this is
always done and almost always a poor choice that isn't realized until
it's all done and over with.

Greg
01 Aug 2002 17:45:39 -0500
Greg Copeland <greg@CopelandConsulting.Net>
Re: cvs checkout pgsql
"Marc G. Fournier" <scrappy@hub.org> writes:
>> Well, it did work before, and I'd really like it to work again.  I do
>> not want to think about how Marc's broken apart the distribution when
>> I'm looking at my local tree, and I don't want to think about it when
>> I'm looking at cvsweb either.

> You don't have to think about anything ... god, does *nobody* read what
> they are replying to??

> if you do a cvs checkout of pgsql, you will get exactly what you are used
> to ...

Yes, I did a re-checkout, remerge of the rather large patch I'm working
on, rebuild, etc.  I've more or less recovered here, after wasting an
hour or two that I had other uses for.  But cvsweb is still broken:
there is AFAICT no page that presents a unified view of the CVS tree
anymore.  If it's merely moved, how about telling me where?

I quite concur with Peter's remarks: some discussion of this sort of
change would have been appropriate in advance, rather than after.

			regards, tom lane

Fri, 02 Aug 2002 00:07:41 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: cvs checkout pgsql 