Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue discovered while using a CentOS 6.4 x86_64 VirtualBox image #34

Open
jrgriffiniii opened this issue Jan 3, 2015 · 0 comments
Open

Comments

@jrgriffiniii
Copy link
Contributor

Hello Everyone,

I believe that I may have identified a potential issue. I was installing PostGIS within a CentOS 6.4 environment (using the VirtualBox image at the URL http://developer.nrel.gov/downloads/vagrant-boxes/CentOS-6.4-x86_64-v20131103.box), and I found that there appeared to be a conflict involving this Module and puppet-postgresql:

class { 'postgresql::globals':
    manage_package_repo => true,
}
[...]
include ::postgis

This fails with the error that $libdir cannot be resolved from within the appropriate SQL file for PostGIS (in this case, /usr/pgsql-8.4/share/contrib/postgis-1.5/postgis.sql). From what I could best determine, this can be traced to an error which arises when the postgresql-server package is installed using the yum.

I've attempted to resolve this by setting manage_package_repo to false, only to find a plethora of issues plaguing the installation process arising from deprecated releases of the GDAL releases (when attempting to install PostGIS from another third-party yum repository).

I've handled this locally by simply invoking sed to replace $libdir within the needed SQL files during the creation of PostGIS databases. I certainly understand if this is far too low a priority an issue to address (CentOS 6.4 and PostGIS 1.5 are quite old).

Please note that, should this more properly be resolved by the maintainers of puppetlabs/puppetlabs-postgresql, I've created the JIRA issue MODULES-1635.

Thank you greatly for your time and contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant