Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s25w7-00HOr7-Ve for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 01 May 2024 09:07:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s25w5-00ByH6-5d for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 01 May 2024 09:07:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s25w4-00ByGz-Vt for pgsql-pkg-yum@lists.postgresql.org; Wed, 01 May 2024 09:07:33 +0000 Received: from ns7.gunduz.org ([165.232.104.158]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s25w2-000uEd-PH for pgsql-pkg-yum@postgresql.org; Wed, 01 May 2024 09:07:32 +0000 Received: from dell-laptop07.gunduz.org (unknown [152.37.89.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ns7.gunduz.org (Postfix) with ESMTPSA id 02DDF30001D4; Wed, 1 May 2024 09:07:27 +0000 (UTC) Message-ID: <78fd412966536e4441e9bb3730d6441486d06c2e.camel@gunduz.org> Subject: Re: AW: postgis/gdal - undefined symbol: proj_crs_has_point_motion_operation From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= To: "Lorenz, Christopher" , "pgsql-pkg-yum@postgresql.org" Date: Wed, 01 May 2024 10:07:27 +0100 In-Reply-To: <7a701d8cf9124ea5b2f1968f734b56e9@ZIT-BB.Brandenburg.de> References: <102a9afd1469446380ca72ded8de4df9@ZIT-BB.Brandenburg.de> <7a701d8cf9124ea5b2f1968f734b56e9@ZIT-BB.Brandenburg.de> Autocrypt: addr=devrim@gunduz.org; prefer-encrypt=mutual; keydata=mQINBFN+TjkBEAC6pudhV1V54kHPe91nr6Erz6VuG93VKfcHOHN86yET35s8ytey7f//m 93mW0X6LJUMbY+Z0BztU4EauGAhYRSFzpBWUVBCxaaSyB+l0FR6WtH/Lv6Sxql0GLs6Uhxsk2v3jJ tMtk+hFAW2TJInW0ab1xxwTiiHFmSnJOBEK7IMlOOu5kfOAILgGOgiyMUPsDf5iTIJ35iX9hqFvmz MueFVwAExTeTkKCRXvuGXrO28Bbesy6h4GbJe1bUaTwTMEBn90oQD20UUKI9Lvo46c1SkqF1nOSoQ A3A2eBjWACq68DQ9Q8TbtkBlL8QKftrFz3SL0jth9ZpxyYfm+jiZ5LEAd717YM7qjvH5Yq0juZO3U jz2L9RVgyIF1lTQ33fQEuGn797n7LxdaQSdOYK88yrpABic6fJs6rxGy86HcNVHJQCfxgu+uU4eG9 /wzBKllXreabD2JJXIRjqvhJTXd7JWaF6TZUEUM0SH2GlA6I2G2vGSyRoe0/jaqUIDGm5drzFGkrK 7CwhWzLqxSBlVkCelhOVfDuyit3ypwPhsztTOgZ9w3iwnAPZWuqXbys2Z26H9hQb5eG7xlkCZwlSr mD8mUdHlU5DP84VPIXX6mGCh0I4EJ4ur61CNESpv86BKfGUpbl/3x9XSmcWfvdxB4JnrjHBm9aDIQ ZzukEJGdiGBpQARAQABtCNEZXZyaW0gR8O8bmTDvHogPGRldnJpbUBndW5kdXoub3JnPokCOQQTAQ IAIwUCU35OOQIbAwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJENjDPf6Sz261pAgP/j4OJd8 EfBLcdkeYyWKNVV3xN6KGF5tTo5iLjjIBmxmj7403DoigD4qfXY8UQ1hG1e0vTe+zaBuL+fMmn3Rg SAcUcjNUjVwcOeGFIMO0uMDX4xnMeAahjuc+2EKBFBW0UY21aH6BdmM98GkU/gyBpaMt/MC+5Xgsj 1koqlA9vCj1bnDXVNP7w/MPhVsEGbhkBZFB/vwVDVJ0J1U4vA1pr2ggUGOOv0kXu7r7B7nGQgcxN8 qh8QBgfP4ePzbubdA3oGY3PTmRjWWDAzA7HpnKD9pPiAFxvhmnUVcOCdTCo9mNaJc+kRXP7yGbsQa rOWvLMtCvKa0DjFJ6SDY45h3g1XF+Xp/ZMZLbJ7xNc3zEVnBZc0AIvGL+IlQbo9trPdJvjdrFATio UV/cLxug1p4kl8JB6YMvToiKFmMlpQv2wcKK63bm01lDjU93sAy8oZpeKYlOYlN9D0WmyhJbFTlTl IJhMX0aY/xfxUaMYJC5DxV+9s18uviqGWDb2zQR3i3qUbfzV27yHnKo194rUblZ128CzAjs32NerE CLJjKEpc2Ci14fJZz6c6P0J5JTONBKhAzygQi/l97RGBqsLiniJIsTUjGH+hEr7hTnhEg/ZOQSs32 h9vVjhQB7WJ9Xg9A3Frw5mD+W3YkMMM4bFryLTM5p7E1iwGlx+XeM8UMzhtYt Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.1 (3.52.1-1.fc40) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Tue, 2024-04-30 at 13:16 +0000, Lorenz, Christopher wrote: > The result was: > $ rpm -qa | grep proj > proj94-9.4.0-1PGDG.rhel8.x86_64 > proj82-8.2.1-3.rhel8.x86_64 > proj92-9.2.1-1PGDG.rhel8.x86_64 >=20 > The solution for me was to remove the old proj82 and proj92 rpms, gdal > has used the proj92 library before.=20 >=20 > Now it works (PostGIS_full_version()): Great! > The automatic update on my server doesn't removes the old proj92 > package. Is it possible and practical to define conflicts with > different proj versions in specs to avoid problems like these?=20 I am not sure this is 100% safe. What happens when there is a PostGIS version that cannot be compiled against newer Proj and someone wants to install multiple PostGIS versions? I'm not saying that the current situation is ok, just saying that I'm not satisfies with the solutions that I thought so far. Regards, --=20 Devrim G=C3=BCnd=C3=BCz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR