Re: postgresql-7.0.3.tar.gz != postgresql-7.0.3-2.src.rpm

From: darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain)
To: Kevin Cole <kjcole(at)gri(dot)gallaudet(dot)edu>
Cc: db-sig(at)python(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Re: postgresql-7.0.3.tar.gz != postgresql-7.0.3-2.src.rpm
Date: 2001-04-13 00:41:15
Message-ID: 20010413004115.659C31A7F@druid.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thus spake Kevin Cole
> I'm cc'ing the pgsql-bugs address, since I'm starting to think it's
> their problem.
>
> It appears that the folks at www.postgresql.org don't know about pgdb.py
> either. Or, rather, not consistently. Apparently, the 7.0.3-2 source
> tarball doesn't equal the 7.0.3-2 source RPM.
>
> I just downloaded the latest PostgreSQL source RPM (7.0.3-2) from
> www.postgresql.org and rebuilt everything. (From that source, it built
> 10 binary RPM's: the client, server, development stuff, perl, python,
> tcl and tk, test, odbc, and jdbc packages.) When finished, I ended up
> with exactly what I had before: pgsqldb.py et al. No pgdb.py.

I'm not sure what's in the RPM (I run NetBSD) but the PostgreSQL sources
for PyGreSQL are the horse's mouth. The official development tree moved
into PygreSQL about a month ago.

--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Philip Warner 2001-04-13 10:59:39 Re: table data not being restored after pg_dump
Previous Message Lamar Owen 2001-04-12 20:32:35 Re: postgresql-7.0.3.tar.gz != postgresql-7.0.3-2.src.rpm