http://bugzilla.opensuse.org/show_bug.cgi?id=969715 Roman Evstifeev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@dstoecker.de, | |tzotsos@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c1 --- Comment #1 from Angelos Tzotsos --- We need to add this requirement to PostGIS 2.2 package. Actually there is no older package in the Application:Geo anymore... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c3 --- Comment #3 from Angelos Tzotsos --- The older source tarballs are there on purpose: for migration from previous database versions. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c5 --- Comment #5 from Roman Evstifeev --- I glanced at gdal changelog an did not see any suspicious new requirements. I created bugreport at postgis trac: http://trac.osgeo.org/postgis/ticket/3492#ticket It is about configure script, which still requires geos 3.3 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c7 --- Comment #7 from Bruno Friedmann --- For example on a 13.1 Evergreen when I try to install postgresql92-postgis when the machine is clear of all geo apps. and have packman and application:geo repository the dependances are correctly handle by the postgis package Selecting 'postgresql92-postgis-2.2.1-7.2.x86_64' from repository 'geo' for installation. Resolving package dependencies... Force resolution: No The following 17 NEW packages are going to be installed: libboost_serialization1_53_0 1.53.0-4.1.2 libCGAL11 4.7-35.3 libfreexl1 1.0.2-11.2 libgdal20 2.0.2-32.2 libgeos-3_5_0 3.5.0-14.3 libgeos_c1 3.5.0-14.3 libgeotiff2 1.4.1-6.4 libhdf4 4.2.11-32.1 libhdf5-11 1.8.16-22.3 libhdf5_hl11 1.8.16-22.3 liblwgeom-2_2-5 2.2.1-7.2 libnetcdf7 4.3.3.1-17.6 libopenjp2-7 2.1.0-31.2 libproj9 4.9.2-22.2 libSFCGAL1 1.2.2-3.2 libspatialite7 4.3.0a-8.6 postgresql92-postgis 2.2.1-7.2 I've made a request to packman mailing list, that they remove their outdated geos at least for Leap and Tumbleweed (they distribute a 3.4.2 version) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c9 --- Comment #9 from Bruno Friedmann --- Roman actual package postgis require the right version of geos see my previous example. postgis2 was still available in app:geo during some times, but get deprecated months ago (if not a year). When we introduce postgis with postgresqlXX- variant. As your postgis2 was in another Vendor repo, I would assume that installing postgresql93-postgis wouldn't allow the vendor change. Mixing repository is not supported for obvious reasons :-) I'm interested in fixing packaging issues if there's some : For that could you provide a testcase with a clean 13.2 repo : oss, update, application-geo enable and then try the zypper -v in postgresql93-postgis and show what packages is proposed at install time. Also an overview of zypper lr -d would explain certainly the what and why it as failed in your case. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c13 --- Comment #13 from Roman Evstifeev --- Why not just add %requires_ge to the spec and let resolver to pick right version? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c15 --- Comment #15 from Roman Evstifeev --- "%requires_ge libgeos0" will create a versioned dependency on libgeos of the seame version that was used for build. I the case you described, when user tries to install postgis, resolver will force upgrade to geos 3.5. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c18 --- Comment #18 from Bruno Friedmann --- I've made a test by adding the suggested %requires_ge libgeos1 for lib part %package -n %{libname} Summary: LWGEOM geometry shared library Group: System/Libraries %requires_ge libgeos1 but still rpm header contain no hard require for geos ? Thus I don't understand what can be done expect hard requiring 3.5.0 /sbin/ldconfig libSFCGAL.so.1()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.4)(64bit) libgeos_c.so.1()(64bit) libjson-c.so.2()(64bit) libproj.so.9()(64bit) rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsLzma) <= 4.4.6-1 If you want to help could you branch the package (Application:Geo:Staging/postgis) then edit postgis.spec then build it bash pre_checkin.sh && osc build --clean postgresql-postgis93.spec and report your result here ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c20 --- Comment #20 from Bruno Friedmann --- I would say as Application:Geo is a final and devel repository, we will not be able to produce a silver bullet for everycase. Roman, Angelos do you have any package on Leap that force geos 3.4.2 ? If none, then I would recommend an update in the .changes + description that people trying to use postgis from Application:Geo should after adding the repository do a zypper -v dup --from Application:Geo to upgrade any component to the one present in A:G ... Which is the normal recommended way for any additionnal repository. This will help people like Roman having a component (perhaps older) to be upgraded to the last one we have in A:G. Otherwise, we will have to open a Maintenance Ticket against Leap + SLE12 to have geos upgraded there (and explaining why :-)) Your thoughs -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c22 Martin Pluskal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com --- Comment #22 from Martin Pluskal --- (In reply to Bruno Friedmann from comment #20)

I would say as Application:Geo is a final and devel repository, we will not be able to produce a silver bullet for everycase.

Roman, Angelos do you have any package on Leap that force geos 3.4.2 ? If none, then I would recommend an update in the .changes + description that people trying to use postgis from Application:Geo should after adding the repository do a zypper -v dup --from Application:Geo to upgrade any component to the one present in A:G ... Which is the normal recommended way for any additionnal repository.

This will help people like Roman having a component (perhaps older) to be upgraded to the last one we have in A:G.

Otherwise, we will have to open a Maintenance Ticket against Leap + SLE12 to have geos upgraded there (and explaining why :-)) hmpf this would be tricky as geos on Leap does not have split package for shared library, such change would introduce new package and likely require rebuild of geos dependencies (gdal).

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c24 --- Comment #24 from Roman Evstifeev --- (In reply to Martin Pluskal from comment #23)

I assume that you mean postgis to use statically linked geos? Technically it would be possible, but such solution would be just wrong - there are reasons why static linking is not used and actively discouraged/forbidden in most distributions.

Static linking have some drawbacks, but maybe for this particular case it can be used as a solution? Is it forbidden in openSUSE official repos? If it is forbidden in the official repo - maybe some conditional blocks in the spec will allow to link statically only in the devel repo, while official repo will have dynamically linked one? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c26 --- Comment #26 from Bruno Friedmann --- To add informations : without geos-3.5 postgis will loose some functionnality - GEOS geometry library, version 3.3 or greater, but GEOS 3.5+ is recommended to take full advantage of all the new functions and features. Without GEOS 3.5, you will be missing some major enhancements such as ST_ClipByBox2D and ST_Subdivide. GEOS is available for download from http://trac.osgeo.org/geos/ and 3.4+ is backward-compatible with older versions so fairly safe to upgrade. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=969715 http://bugzilla.opensuse.org/show_bug.cgi?id=969715#c28 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #28 from Bruno Friedmann --- I'm closing this, seems to work as expected in my last test with 42.1 and 42.2 and TW. If not reopen, or create a new one. -- You are receiving this mail because: You are on the CC list for the bug.