Bug 1830257 - Compile failure if version of PostgreSQL client libraries is different from server version
Summary: Compile failure if version of PostgreSQL client libraries is different from s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: postgis
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sandro Mani
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-01 11:17 UTC by Thomas Sailer
Modified: 2020-05-13 07:37 UTC (History)
8 users (show)

Fixed In Version: postgis-3.0.1-6.fc32 postgis-2.5.4-1.fc31
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-13 02:54:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
compile fix patch (453 bytes, patch)
2020-05-01 11:17 UTC, Thomas Sailer
no flags Details | Diff

Description Thomas Sailer 2020-05-01 11:17:11 UTC
Created attachment 1683653 [details]
compile fix patch

When compiling postgis, the server pg config needs to be used, otherwise compilation fails if the client library version differs from the server version.

This can happen eg. if you use the modular PG 11 server on F32, you will still have PG12 client libraries.

NB: upgrading from F31/PG11/PostGIS 2.5.1 to F32/PG12/PostGIS 3.0.1 seems currently pretty impossible with PostGIS enabled databases. I ended up compiling PostGIS 3.0.1 for PG11, upgraded the databases to PostGIS 3.0.1, and then made the move to F32/PG12/PostGIS 3.0.1. This is due to a bug in PostGIS 2.5.1. This bug was apparently fixed in 2.5.4 (maybe 2.5.3 as well), so it might make sense to provide PostGIS 2.5.4 on F31 and in postgis-upgrade on F32.

NB2: that PostGIS isn't part of the PostgreSQL module isn't helping either...

Comment 1 Fedora Update System 2020-05-04 10:38:38 UTC
FEDORA-2020-3c66d648fc has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c66d648fc

Comment 2 Fedora Update System 2020-05-04 10:38:39 UTC
FEDORA-2020-284fcb709e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-284fcb709e

Comment 3 Fedora Update System 2020-05-05 04:40:49 UTC
FEDORA-2020-3c66d648fc has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3c66d648fc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c66d648fc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2020-05-05 05:11:58 UTC
FEDORA-2020-284fcb709e has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-284fcb709e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-284fcb709e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2020-05-13 02:54:56 UTC
FEDORA-2020-284fcb709e has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2020-05-13 07:37:02 UTC
FEDORA-2020-3c66d648fc has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.