Thread

  1. Re: [HACKERS] Problem with CVS access to current sources

    Tom Lane <tgl@sss.pgh.pa.us> — 1998-07-29T15:58:02Z

    ernst.molitor@uni-bonn.de writes:
    > The command
    >   cvs -z3 -d :pserver:anoncvs@postgresql.org:/usr/local/cvsroot co -P pgsql
    > returns 
    >   Fatal error, aborting.
    >   : no such user
    
    Yeah, the cvs server at postgresql.org has been broken for a couple days
    now.  I'm seeing the same and some other people have complained as well.
    
    Marc, are you awake?
    
    			regards, tom lane
    
    
  2. Re: [HACKERS] Problem with CVS access to current sources

    Marc G. Fournier <scrappy@hub.org> — 1998-08-01T15:28:58Z

    On Wed, 29 Jul 1998, Tom Lane wrote:
    
    > ernst.molitor@uni-bonn.de writes:
    > > The command
    > >   cvs -z3 -d :pserver:anoncvs@postgresql.org:/usr/local/cvsroot co -P pgsql
    > > returns 
    > >   Fatal error, aborting.
    > >   : no such user
    > 
    > Yeah, the cvs server at postgresql.org has been broken for a couple days
    > now.  I'm seeing the same and some other people have complained as well.
    > 
    > Marc, are you awake?
    
    Try it now...I just tried it using anon-cvs from home, and it appears to
    work...
    
    Marc G. Fournier                                
    Systems Administrator @ hub.org 
    primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
    
    
    
  3. Re: [HACKERS] Problem with CVS access to current sources

    Peter Mount <peter@retep.org.uk> — 1998-08-01T22:41:01Z

    On Sat, 1 Aug 1998, The Hermit Hacker wrote:
    
    > On Wed, 29 Jul 1998, Tom Lane wrote:
    > 
    > > ernst.molitor@uni-bonn.de writes:
    > > > The command
    > > >   cvs -z3 -d :pserver:anoncvs@postgresql.org:/usr/local/cvsroot co -P pgsql
    > > > returns 
    > > >   Fatal error, aborting.
    > > >   : no such user
    > > 
    > > Yeah, the cvs server at postgresql.org has been broken for a couple days
    > > now.  I'm seeing the same and some other people have complained as well.
    > > 
    > > Marc, are you awake?
    > 
    > Try it now...I just tried it using anon-cvs from home, and it appears to
    > work...
    
    Well, CVS is now working here now, but I'm still getting:
    
    ERROR:  pg_atoi: error in "f": can't parse "f"
    ERROR:  pg_atoi: error in "f": can't parse "f"
    
    when running initdb. Heres some more details (from --debug):
    
    > creating bootstrap relation
    bootstrap relation created ok
    > Commit End
    tuple 1242<Inserting value: 'boolin'
    Typ == NULL, typeindex = 3 idx = 0
    boolin End InsertValue
    Inserting value: '11'
    Typ == NULL, typeindex = 10 idx = 1
    11 End InsertValue
    Inserting value: 'f'
    Typ == NULL, typeindex = 10 idx = 2
    ERROR:  pg_atoi: error in "f": can't parse "f"
    ERROR:  pg_atoi: error in "f": can't parse "f"
    initdb: could not create template database
    initdb: cleaning up by wiping out /usr/local/dbase/data/base/template1
    
    -- 
    Peter T Mount peter@retep.org.uk or petermount@earthling.net
    Main Homepage: http://www.retep.org.uk
    PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
    
    
    
  4. Re: [HACKERS] Problem with CVS access to current sources

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-08-01T22:56:14Z

    > On Sat, 1 Aug 1998, The Hermit Hacker wrote:
    > 
    > > On Wed, 29 Jul 1998, Tom Lane wrote:
    > > 
    > > > ernst.molitor@uni-bonn.de writes:
    > > > > The command
    > > > >   cvs -z3 -d :pserver:anoncvs@postgresql.org:/usr/local/cvsroot co -P pgsql
    > > > > returns 
    > > > >   Fatal error, aborting.
    > > > >   : no such user
    > > > 
    > > > Yeah, the cvs server at postgresql.org has been broken for a couple days
    > > > now.  I'm seeing the same and some other people have complained as well.
    > > > 
    > > > Marc, are you awake?
    > > 
    > > Try it now...I just tried it using anon-cvs from home, and it appears to
    > > work...
    > 
    > Well, CVS is now working here now, but I'm still getting:
    > 
    > ERROR:  pg_atoi: error in "f": can't parse "f"
    > ERROR:  pg_atoi: error in "f": can't parse "f"
    > 
    > when running initdb. Heres some more details (from --debug):
    > 
    
    It is because there are two copies of initdb in initdb.sh.  Someone
    reported the problem, but no one fixed it.
    
    -- 
    Bruce Momjian                          |  830 Blythe Avenue
    maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
      +  If your life is a hard drive,     |  (610) 353-9879(w)
      +  Christ can be your backup.        |  (610) 853-3000(h)
    
    
  5. Re: [HACKERS] Problem with CVS access to current sources

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-08-01T23:11:54Z

    > 
    > It is because there are two copies of initdb in initdb.sh.  Someone
    > reported the problem, but no one fixed it.
    > 
    
    I have fixed this in the current CVS tree.
    
    -- 
    Bruce Momjian                          |  830 Blythe Avenue
    maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
      +  If your life is a hard drive,     |  (610) 353-9879(w)
      +  Christ can be your backup.        |  (610) 853-3000(h)
    
    
  6. Re: [HACKERS] Problem with CVS access to current sources

    Marc G. Fournier <scrappy@hub.org> — 1998-08-02T00:15:57Z

    On Sat, 1 Aug 1998, Bruce Momjian wrote:
    
    > It is because there are two copies of initdb in initdb.sh.  Someone
    > reported the problem, but no one fixed it.
    
    	Fixed...:(
    
    Marc G. Fournier                                
    Systems Administrator @ hub.org 
    primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
    
    
    
  7. Re: [HACKERS] Problem with CVS access to current sources

    Marc G. Fournier <scrappy@hub.org> — 1998-08-02T00:16:15Z

    On Sat, 1 Aug 1998, Bruce Momjian wrote:
    
    > > 
    > > It is because there are two copies of initdb in initdb.sh.  Someone
    > > reported the problem, but no one fixed it.
    > > 
    > 
    > I have fixed this in the current CVS tree.
    
    	Oops...
    
    Marc G. Fournier                                
    Systems Administrator @ hub.org 
    primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
    
    
    
  8. Re: [HACKERS] Problem with CVS access to current sources

    Peter Mount <peter@retep.org.uk> — 1998-08-02T09:26:11Z

    On Sat, 1 Aug 1998, Bruce Momjian wrote:
    
    > > 
    > > It is because there are two copies of initdb in initdb.sh.  Someone
    > > reported the problem, but no one fixed it.
    > > 
    > 
    > I have fixed this in the current CVS tree.
    
    Thanks.
    
    -- 
    Peter T Mount peter@retep.org.uk or petermount@earthling.net
    Main Homepage: http://www.retep.org.uk
    PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
    
    
    
  9. Re: [HACKERS] Problem with CVS access to current sources

    ernst.molitor@uni-bonn.de — 1998-08-02T09:58:24Z

    Hi Marc, 
    
    thank you very much, CVS works like a charm again...
    
    Best regards,
    
    Ernst