Chuck Milam wrote:
>
> On Tue, 20 Jul 1999, Bruce Momjian wrote:
>
> > > What's the time frame for the 6.5.1 release? I may just wait for it.
> > Should have been today. Cc'ing marc.
>
> I see the 6.5.1 tarball is now on the FTP site, but no updated RPMS yet.
Preliminary RPMS are available on my private Public Server (:-0) at
http://206.74.232.196/SRPMS.beta and RPMS.beta If Marc wishes to
mirror, he may.
THESE ARE VERY PRELIMINARY. They have been tested and are working on my
testbed site (and the source rpm successfully --rebuild'ed on my RedHat
6.0+rpm 3.0.2 box at home without any editing or kludges -- thanks for
fixing the dangling symlinks Tom) -- but, you need to do your own
testing. Rebuilding this rpm set requires a complete development
environment -- specifically, python-devel needs to be installed. Also, I
have not fully tested the odbc, jdbc, perl, or python packages -- the
tcl package with pgaccess runs well (gotta love that pgaccess tcl
script!). I'll just put it this way -- I will be blowing these i386
rpms into my production box within a couple of days if they hold up
under testing -- and I have every reason to believe that they will.
The binary i386 RPMS were built on an i486DX4/100 running Linux-Mandrake
5.3 (AKA RedHat 5.2+KDE done right). They will run on a RedHat 6 machine
if the compat-libs are installed.
Support for good upgrading is not currently included -- which is why I
consider these to be PRELIMINARY. HOWEVER, if you have already
installed or upgraded to the 6.5 RPMS, you may do an rpm -U to upgrade
since the database format has not changed between 6.5.0 and 6.5.1 (which
I just did on my home machine, with no data loss).
For all others wishing to test these RPMS, read my notes on upgrading
postgresql rpms at http://206.74.232.196/postgres/rpm_upgrade.html ALSO
you may download the spec file used to generate these rpms -- just
browse the postgres directory. I have included the spec file from
Thomas' 6.5-1 release, as well as the one from this 6.5.1-1 release. I
welcome feedback both on the spec file and the upgrade procedure --
while it has worked for me through several upgrades
(6.1.1->6.2.0->6.2.1-6.3.0->6.3.2->6.5.0) on my production database
server, YMMV.
My site policy forbids anonymous ftp from behind my firewall or other
distribution off of my main server (wgcr.org) (and I set the policy) --
use wget to good effect. (wget -r http://206.74.232.196/postgres). I'll
get a domain name for this personal server later this week, hopefully.
I was going to wait for an upgrading script of some kind (and Thomas'
blessing) before announcing these beta-test RPMS, but, I guess I won't
wait (Thomas may have to slap me around a bit ;-)). I AM looking for
feedback on the best ways to upgrade, however. Should rpm -U be
accomodated, or not even allowed? And many other questions that I will
post when I am a little more coherent....
So: Caveat downloador...
Lamar Owen
WGCR Internet Radio
