[BUGS] BUG #8463: Packaging problem with postgis rpms
The following bug has been logged on the website: Bug reference: 8463 Logged by: Kriton Kyrimis Email address: kyri...@alumni.princeton.edu PostgreSQL version: 9.2.4 Operating system: Scientific Linux 6.4 Description: (I am submitting this report here, as I assume that the rpms downloaded from yum.postgresql.org are built by postgresql and not by postgis.) The latest release of the postgis2_92* rpms (version 2.0.4) introduced a new package, postgis2_92-client, containing, among other things, the postgis shared library. This creates the problem that, after updating an existing system, the shared libraries disappear, and postgis stops working, producing the error "postgis2_92-client-2.0.4-1" whenever a query involving postgis is executed. At the very least, the postgis2_92 package should depend on the postgis2_92-client package, so that updating the former will also install the latter, thus avoiding breaking existing systems. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #8500: Upgrade to postgis 2.1 breaks existing databases
The following bug has been logged on the website: Bug reference: 8500 Logged by: Kriton Kyrimis Email address: kyri...@alumni.princeton.edu PostgreSQL version: 9.2.4 Operating system: Scientific Linux 6.4 Description: The version of postgis, available in the postgresql yum repository for postgis 9.2, was recently upgraded to version 2.1. This breaks existing databases built with postgis 2.0, as queries involving postgis fail with the error message "ERROR: could not access file "$libdir/postgis-2.0": No such file or directory" This includes backing up the databases, so upgrading them to use postgis 2.1 may not even be an option, if a hard upgrade is required. I have downgraded all postgis2_92 packages to version 2.0.4 and excluded them from future upgrades, but I'd recommend reverting to that version in the repositories, as well. At the very least, please ensure that version 2.0.x of the packages remains available in the future. Better still, provide alternative postgis21_92-* packages, for those wishing to use the latest version, without affecting those that use the previous version. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
