{"action":"closed","issue":{"url":"https://api.github.com/repos/boundlessgeo/django-osgeo-importer/issues/30","repository_url":"https://api.github.com/repos/boundlessgeo/django-osgeo-importer","labels_url":"https://api.github.com/repos/boundlessgeo/django-osgeo-importer/issues/30/labels{/name}","comments_url":"https://api.github.com/repos/boundlessgeo/django-osgeo-importer/issues/30/comments","events_url":"https://api.github.com/repos/boundlessgeo/django-osgeo-importer/issues/30/events","html_url":"https://github.com/boundlessgeo/django-osgeo-importer/issues/30","id":180930752,"number":30,"title":"Travis CI build is failing due to PostGIS versioning issue","user":{"login":"harts-boundless","id":20508891,"avatar_url":"https://avatars.githubusercontent.com/u/20508891?v=3","gravatar_id":"","url":"https://api.github.com/users/harts-boundless","html_url":"https://github.com/harts-boundless","followers_url":"https://api.github.com/users/harts-boundless/followers","following_url":"https://api.github.com/users/harts-boundless/following{/other_user}","gists_url":"https://api.github.com/users/harts-boundless/gists{/gist_id}","starred_url":"https://api.github.com/users/harts-boundless/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/harts-boundless/subscriptions","organizations_url":"https://api.github.com/users/harts-boundless/orgs","repos_url":"https://api.github.com/users/harts-boundless/repos","events_url":"https://api.github.com/users/harts-boundless/events{/privacy}","received_events_url":"https://api.github.com/users/harts-boundless/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-04T15:44:42Z","updated_at":"2016-10-13T16:53:06Z","closed_at":"2016-10-13T16:53:06Z","body":"> To summarize things we are finding: this seems to relate to the CREATE EXTENSION being used to enable PostGIS; the error message clearly suggesting that it is now looking for PostGIS 2.3 instead of 2.2 or 2.1. The very recent release of PostGIS 2.3 (Sept 26) and the use of an unpinned apt-get install of package \"postgis\" suggests a cause. Maybe postgis was updated in pgdg or something, and importer's install.sh scaffolding to avoid using it is now broken.\r\n\r\n> Our idea about why it is still working locally in Vagrant is that we provisioned before the postgis upgrade.\r\n"}}
{"actor":{"display_login":"harts-boundless"}}