Skip to content

Added postgresql 10 + postgis 2.4.0#63

Closed
tdamsma wants to merge 7 commits intopostgis:masterfrom
tdamsma:master
Closed

Added postgresql 10 + postgis 2.4.0#63
tdamsma wants to merge 7 commits intopostgis:masterfrom
tdamsma:master

Conversation

@tdamsma
Copy link

@tdamsma tdamsma commented Oct 12, 2017

Added postgresql 10 + postgis 2.4.0, and postgresql 9.6 + postgis 2.4.0.

To get the postgis 2.3 builds passing, I had to remove line 11 postgis=$POSTGIS_VERSION \ from the template, as postgis 2.3 has been purged from the apt repo. I don't understand why postgis needs to be installed after postgresql-x-postgis-x is installed before, everything seem to just work without it. But as I don't understand why it was there, I can't really judge if it is a bad idea to remove it.

As postgresl-10 is FROM debian:stretch, I modified the update script to take that into account

@tdamsma tdamsma mentioned this pull request Oct 12, 2017
Thijs Damsma added 3 commits October 13, 2017 09:58
…able and it doesn't seem to break anything. Postgis is still installed with postgresql-9.6-postgis-2.3
@tdamsma tdamsma changed the title Added postgresql 10.0 + postgis 2.4.0 Added postgresql 10 + postgis 2.4.0 Oct 13, 2017
&& apt-get install -y --no-install-recommends \
postgresql-$PG_MAJOR-postgis-$POSTGIS_MAJOR=$POSTGIS_VERSION \
postgresql-$PG_MAJOR-postgis-$POSTGIS_MAJOR-scripts=$POSTGIS_VERSION \
postgis=$POSTGIS_VERSION \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we discuss this removal? I know they don't version this package name, so is the issue that only the 2.4 version is now available? If so, then I'd like to remove 2.3 entirely.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just saw that you commented on this already.

The postgis package provides a number of PostGIS binaries if I recall. There is some discussion in #8 and #26

@md5
Copy link
Contributor

md5 commented Oct 13, 2017

Can you squash your commits? I think it would make sense to see a single commit for the 2.3 package upgrades (assuming we don't remove 2.3), another commit for adding the 2.4 images, and another commit for the updates to update.sh.

@tdamsma
Copy link
Author

tdamsma commented Oct 14, 2017

That would indeed make perfect sense, but my git-fu is lacking a bit. You could also just squash-merge the whole bunch, as the updates are a bit related: I didn't want to update the 2.3 images, but I had to cause they used outdated packages. Anyways, I'll give it a shot

@tdamsma
Copy link
Author

tdamsma commented Oct 14, 2017

Resubmitted as #64

@tdamsma tdamsma closed this Oct 14, 2017
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

Successfully merging this pull request may close these issues.

2 participants