Opened 15 years ago
Closed 15 years ago
#520 closed defect (fixed)
postgis install script triggers "obsolete major version 8.3" message
Reported by: | camerons | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | OSGeoLive | Keywords: | 3.0-alpha3 postgis |
Cc: |
Description
In building the 3.0-alpha3 version of the liveDVD, I'm getting the following query come up (which requires acknowledgement). It comes up in the install_postgres.sh script.
How do you suggest this should be handled? Should we be updating the LiveDVD install script for Postgres to a later version? Could I tempt you to update the LiveDVD install script? https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_postgres.sh (current version is r2716)
Issue 1: Should we upgrade to a later version of posgres? Issue 2: Please ensure the user is not prompted for a response during the build process and we wish this to be automated.
Package configuration â"Oâ"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"¤ Configuring pos tgresql-common â"oâ"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â"?â" ? â"' â"' â"' Obsolete major version 8.3 â┼' â"' â-® â"' The PostgreSQL version 8.3 is obsolete, but the server or client â-' â"' packages are still installed. Please install the latest packages â-' â"' (postgresql-8.4 and postgresql-client-8.4) and upgrade the existing â-' â"' clusters with pg_upgradecluster (see manpage). â-' â"' â-' â"' Please be aware that the installation of postgresql-8.4 will â-' â"' automatically create a default cluster 8.4/main. If you want to â-' â"' upgrade the 8.3/main cluster, you need to remove the already existing â-' â"' 8.4 cluster (pg_dropcluster --stop 8.4 main, see manpage for â-' â"' details). â-' â"' â-' â"' The old server and client packages are no longer supported. After the â┼" â"' â"' <Ok>
Attachments (1)
Change History (6)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Script is now updated to 8.4/1.4 There seem to be some data import errors but data is making it in, maybe someone who knows more about postgis can check the attached.
comment:3 by , 15 years ago
On Fri, Jan 29, 2010 at 7:07 AM, Paul Ramsey <pramsey@…> wrote:
Those look like worry about errors. Like a load is going on top of a partial pre-existing one. P
---
Have these issues been fixed in the logs yet?
comment:4 by , 15 years ago
Have these issues been fixed in the logs yet?
not sure. any hints from PostGIS experts?
download the build log and search through to "install_postgis.sh":
http://download.osgeo.org/livedvd/3.0-rc2/arramagong-gisvm-3.0-rc2-log/main_install.log.gz
(zless does the trick)
Hamish
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Yes as far as I know this is now fixed.
It seems perfectly sensible to move to postgresql 8.4. And I would suggest changing the script to postgis 1.4 when possible, but you'll need to check with the various dependencies to make sure it won't break. Don't have an ubuntu environment handy atm to check what packages are readily available I'm afraid.