<html><head/><body><html><head></head><body>Hi,<br>
<br>
This is a known issue, and there is already a bugzilla entry about this. I hope to fix it in a few days, by updating GeOS to 3.3.7 and PostGIS to 2.0.2.<br>
<br>
Until then, you can use PostgreSQL RPM repo:<br>
<br>
<a href="http://yum.postgresql.org">http://yum.postgresql.org</a><br>
<br>
Regards, Devrim<br><br><div class="gmail_quote">Max Pyziur <pyz@brama.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px"><br /><br />Greetings,<br /><br />I've done a fresh install of F18 on a Dell Latitude D630 laptop.<br /><br />Until now, most issues have been minor.<br /><br />I'm moving a large amount of Postgresql/PostGIS data from an older Dell <br />Inspiron 600m laptop running F17.<br /><br />I've run:<br />- postgresql-setup initdb<br />- systemctl start postgresql.service<br />- su - postgres<br /><br />and there proceed to run several items bundled into a shell script, which reads <br />as follows (don't know how to control line wrapping here):<br />#!/usr/bin/env bash<br />POSTGIS_SQL_PATH=`pg_config --sharedir`/contrib<br />createdb -E UTF8 template_postgis # Create the template spatial database.<br />createlang -d template_postgis plpgsql # Adding PLPGSQL language support.<br />psql -d postgres -c "UPDATE pg_database SET datistemplate='true' WHERE <br />datname='template_postgis';"<br
/>psql -d template_postgis -f $POSTGIS_SQL_PATH/postgis-64-2.sql # Loading the <br />PostGIS SQL routines<br />psql -d template_postgis -f $POSTGIS_SQL_PATH/spatial_ref_sys.sql<br />psql -d template_postgis -c "GRANT ALL ON geometry_columns TO PUBLIC;" # <br />Enabling users to alter spatial tables.<br />psql -d template_postgis -c "GRANT ALL ON geography_columns TO PUBLIC;"<br />psql -d template_postgis -c "GRANT ALL ON spatial_ref_sys TO PUBLIC;"<br /><br />#########<br /><br />The first problem was running<br />psql -d template_postgis -f $POSTGIS_SQL_PATH/postgis-64-2.sql<br /><br />It gave me:<br />UPDATE 1<br />SET<br />BEGIN<br />psql:/usr/share/pgsql/contrib/postgis-64.sql:59: ERROR: language "C" does not <br />exist<br />psql:/usr/share/pgsql/contrib/postgis-64.sql:65: ERROR: current transaction is <br />aborted, commands ignored until end of transaction block<br /><br />Now things are case-sensitive; globally replacing "LANGUAGE 'C'" with a <br />lower-case 'c' fixes
that.<br /><br />Next problem:<br />UPDATE 1<br />SET<br />BEGIN<br />psql:/usr/share/pgsql/contrib/postgis-64-2.sql:59: ERROR: incompatible library <br />"/usr/lib64/pgsql/<a href="http://postgis-1.5.so">postgis-1.5.so</a>": version mismatch<br />DETAIL: Server is version 9.2, library is version 9.1.<br /><br />Now, I'm stumped. F18 ships w/ postgresql-9.2.2-1.fc18.x86_64 and <br />postgis-1.5.3-4.fc18.x86_64.<br /><br />I'd think that the two would jive, no?<br /><br />Any advice in this regard would be appreciated.<br /><br />Thanks.<br /><br />Max Pyziur<br />pyz@brama.com<br /><br />p.s. If I restore non-spatialized databases, those work correctly.<br /><br /><br /><hr /><br />postgis-users mailing list<br />postgis-users@lists.osgeo.org<br /><a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html></body></html>