Search Criteria
Package Details: postgis-old-upgrade 3.5.1-1
Package Actions
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: | 1.00 |
First Submitted: | 2018-12-17 20:08 (UTC) |
Last Updated: | 2025-01-15 14:06 (UTC) |
Dependencies (10)
- gdal (gdal-hdf4AUR, gdal-libkml-filegdbAUR, gdal-libkmlAUR, gdal-ecwAUR)
- json-c (json-c-gitAUR)
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR)
- pcre
- postgresql-old-upgrade
- proj (proj-gitAUR)
- protobuf-c (protobuf-c-gitAUR)
- clang (llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- llvm (llvm-gitAUR, llvm-minimal-gitAUR) (make)
- perl (perl-gitAUR) (optional) – for scripts in contrib folder
Latest Comments
1 2 Next › Last »
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
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 :(
AlfredoRamos commented on 2023-12-08 23:29 (UTC) (edited on 2023-12-08 23:44 (UTC) by AlfredoRamos)
To upgrade from PostgreSQL 15 to 16 it seems that this package also needs Clang and LLVM 15.
Otherwise you get the following errors:
AchmadFathoni commented on 2023-05-13 00:41 (UTC) (edited on 2023-05-13 00:41 (UTC) by AchmadFathoni)
@kaitocross, You can try this
kaitocross commented on 2023-04-07 01:42 (UTC) (edited on 2023-04-07 01:43 (UTC) by kaitocross)
It doesnt compile anymore on a recent Arch Linux system. Error:
1 2 Next › Last »