Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Hey OP, did the accepted answer work for you? Same situation here, but the accepted answer didn't help me jump the gap.
    – elrobis
    Commented Feb 6, 2018 at 17:32
  • I ignore the offending gdal library. I hope that in a near future it will be solved. Postgis and Postgres work ok as before. Commented Feb 8, 2018 at 7:17
  • Same issue here. In my case adding "--exclude=gdal" uncovered another incompatibility between the existing gdal-libs and libarmadillo: "gdal-libs-1.11.4-10 requires libarmadillo.so.4". I had to use "--exclude=gdal-libs,armadillo" and that got me through the update. I do not have a clear picture yet if postgis is functioning as expected.
    – Sam Alpher
    Commented Feb 21, 2018 at 12:57