Package Details: postgis-old-upgrade 3.6.0-3

Git Clone URL: https://aur.archlinux.org/postgis-old-upgrade.git (read-only, click to copy)
Package Base: postgis-old-upgrade
Description: PostGIS build against postgresql-old-upgrade package for pg_upgrade
Upstream URL: https://postgis.net/
Licenses: GPL
Submitter: amdg
Maintainer: gds506
Last Packager: gds506
Votes: 8
Popularity: 0.002850
First Submitted: 2018-12-17 20:08 (UTC)
Last Updated: 2025-11-06 03:09 (UTC)

Latest Comments

1 2 3 Next › Last »

gds506 commented on 2025-11-06 03:10 (UTC)

Ok. I moved it to the depends on 3.6.0-3. Let me know if it doesn't work.

hashworks commented on 2025-11-06 01:29 (UTC)

Since I got that error on runtime I think it actually needs to go to depends.

$ ldd /opt/pgsql-17/lib/postgis-3.so | grep libc++
        libc++.so.1 => /usr/lib/libc++.so.1 (0x00007fb7be5ae000)
        libc++abi.so.1 => /usr/lib/libc++abi.so.1 (0x00007fb7be56b000)

gds506 commented on 2025-11-05 23:39 (UTC)

Hey @hashworks Thanks for pointing that out. I included libc++ on the makedepends section. I guess that's the right place instead of the depends one. Please let me know if it doesn't work (pushing it as version 3.6.0-2)

hashworks commented on 2025-11-05 19:03 (UTC)

This seems to depend on libc++.

ERROR:  could not load library "/opt/pgsql-17/lib/postgis-3.so": libc++.so.1: cannot open shared object file: No such file or directory

tormod commented on 2025-01-20 23:19 (UTC)

You are right, the makepkg wiki page says "The checksum type and values should always be those provided by upstream, such as in release announcements". BTW, captaincoder's diff already had 3.5.1 nvm :)

gds506 commented on 2025-01-20 13:33 (UTC)

@captaincoder is correct. The PostGIS source download page gives the md5 instead of other hash types and that's why I used it (https://postgis.net/development/source_code/).

Another modification I did to @captaincoder diff is that I used the latest PostGIS 3.5.1... it was on 3.3.2 With these changes I had no issues doing the data migration.

captaincoder commented on 2025-01-20 10:54 (UTC)

@tormod, seems like my diff was applied. I choose md5 since that is what PostGIS supplies with their releases. I could have hashed it with something better but that presumes trust in my correct hashing. By sticking with md5 there are less links in the chain of trust.

Though come to think of it, I don't know how makepkg handles multiple hashes, does it check each if it has multiple hash types for a source file? If so then it should be no problem to keep the md5 and add other types.

tormod commented on 2025-01-19 15:09 (UTC)

@gds506, any reason you're going back to md5 instead of sha512 and b2?

captaincoder commented on 2025-01-15 12:35 (UTC)

@gds506, I (seem to) have successfully upgraded from 16->17 with postgis using the following diff

--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,9 +5,9 @@

 pkgname=postgis-old-upgrade
 _pkgname="${pkgname%-old-upgrade}"
-pkgver=3.3.2
-pkgrel=2
-_pg_majorver=14
+pkgver=3.5.1
+pkgrel=1
+_pg_majorver=16
 pkgdesc='PostGIS build against postgresql-old-upgrade package for pg_upgrade'
 arch=('x86_64')
 url='https://postgis.net/'
@@ -25,8 +25,7 @@ makedepends=('clang' 'llvm')
 optdepends=('perl: for scripts in contrib folder')
 options=('!makeflags')
 source=("https://download.osgeo.org/postgis/source/$_pkgname-$pkgver.tar.gz")
-sha512sums=('4dd129057598b032ba322c42888bb8ce14b9423bd450ef7a42fa22162f6b48e34b226f38480aa67fe2da85be2529b0822655855f9846b657bdd32f50256f4305')
-b2sums=('40dc7636f04e0d5cfd734b175da1ce49c32e4b8f5750059e79e03a7395fb8b9241c1f479815794b46dee81704d7c392fe7693c9f0180323d1ca21812c37d36b5')
+md5sums=('21d2cb87a5255d82fb12ff1b7b4d3795')

gds506 commented on 2025-01-15 00:47 (UTC)

Has anyone been successful upgrading Postgis from Postgres 16 to 17? I tried with a similar approach as @AlfredoRamos latest comment but this time it didn´t work :(

1 2 3 Next › Last »