Bug 21468

Summary: postgis-2.2.2-3.mga6 is built for PostgreSQL 9.5, but only have v9.4 or v9.6 available as packages
Product: Mageia Reporter: Andy Jefferson <andy_jefferson>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: antonin.roussel, cjw, doktor5000, eatdirt, joequant, marja11, ouaurelien
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: postgis-2.2.2-3.mga6 CVE:
Status comment:

Description Andy Jefferson 2017-08-07 20:22:05 CEST
Description of problem:
The package postgis-2.2.2-3.mga6 seems to be built for PostgreSQL 9.5.
Sadly MGA 6 only makes PostgreSQL 9.4 and 9.6 available as packages.



Version-Release number of selected component (if applicable):
postgis-2.2.2-3.mga6

How reproducible:

Steps to Reproduce:
1. Clean install of MGA6

2. Install PostgreSQL 9.6 
postgresql9.6-server-9.6.3-1.mga6
postgresql9.6-devel-9.6.3-1.mga6
postgresql9.6-plpgsql-9.6.3-1.mga6
postgresql-jdbc-9.4.1210-1.mga6
postgresql9.6-9.6.3-1.mga6

3. Install PostGIS 2.2
lib64postgis5-2.2.2-3.mga6
lib64postgis-devel-2.2.2-3.mga6
postgis-2.2.2-3.mga6

4. Start up PostgreSQL, and then su to the postgres user, and try to invoke
psql {mydatabase} --file=/usr/share/postgresql/contrib/postgis-2.2/postgis.sql

and it comes back with 

SET
BEGIN
DO
CREATE FUNCTION
psql:/usr/share/postgresql/contrib/postgis-2.2/postgis.sql:96: ERROR: incompatible library "/usr/lib64/postgresql/postgis-2.2.so": version mismatch
DETAIL: Server is version 9.6, library is version 9.5.


The library version (for postGIS) needs to match what the server (9.6) is running.
Florian Hubold 2017-08-07 20:44:38 CEST

CC: (none) => doktor5000

Comment 1 Florian Hubold 2017-08-08 21:32:10 CEST
@Joseph/Christian: Mind to take a look please? I'm not that good with postgres, but this looks like to me that postgis was rebuilt the last time when postgresql9.5 was still available (and possibly 9.4 was not installable for any reason) and it might only need a rebuild, no? 
Also the requires should probably be stricter as it should require the same postgres version at runtime which it was built with, no?
The macro %requires_eq might be usable to automate this ...

CC: (none) => cjw, joequant

Comment 2 Marja Van Waes 2017-08-08 23:11:05 CEST
(In reply to Florian Hubold from comment #1)
> @Joseph/Christian: Mind to take a look please? I'm not that good with
> postgres, but this looks like to me that postgis was rebuilt the last time
> when postgresql9.5 was still available (and possibly 9.4 was not installable
> for any reason) and it might only need a rebuild, no? 
> Also the requires should probably be stricter as it should require the same
> postgres version at runtime which it was built with, no?
> The macro %requires_eq might be usable to automate this ...

Thanks, Florian :-)

(Assigning to all packagers collectively for now, because postgis has no registered maintainer, Joseph or Christian or anyone else who wants to fix this bug can reassign to himself)

Whiteboard: (none) => MGA6TOO
Version: 6 => Cauldron
CC: (none) => eatdirt, marja11
Source RPM: (none) => postgis-2.2.2-3.mga6
Assignee: bugsquad => pkg-bugs

Comment 3 Andy Jefferson 2018-02-16 16:31:22 CET
FWIW, taking current prod release of PostGIS (2.4.3) and doing a plain build and then install (using PostGIS release instructions) against the MGA-provided PostgreSQL 9.6, this runs fine. Perhaps it simply needs someone to rebuild the RPM against PostgreSQL 9.6 (instead of 9.5)?
Antonin Roussel 2019-02-28 13:56:40 CET

CC: (none) => antonin.roussel

Comment 4 Andy Jefferson 2019-05-26 11:15:06 CEST
Perhaps we can have this fixed for Mageia v7? 

If it is indeed just a case of actually building consistent things together (like I demonstrated) before release then that should not be a problem, no?
Comment 5 Andy Jefferson 2019-07-31 20:20:12 CEST
Can someone just close this?

In MGA7 if the user installs postgresql11-11.4-1.mga7 and postgis-2.5.2-1.mga7 then the above process works. 

i.e The PostGIS v2.5 extension has been built against PostgreSQL v11
David Walser 2019-08-11 17:19:05 CEST

Whiteboard: MGA6TOO => (none)
Version: Cauldron => 6

Comment 6 Aurelien Oudelet 2020-08-23 15:29:47 CEST
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:OLD

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: NEW => RESOLVED

Comment 7 Andy Jefferson 2020-08-23 15:32:06 CEST
Think you'll find that I already said it works in MGA 7 and asked someone to close it a year ago
Comment 8 Aurelien Oudelet 2020-08-23 15:35:05 CEST
@ Andy
Sometime, Bugsquad is a short team and time flies ;)