Opened 10 months ago
Closed 9 months ago
#5664 closed defect (invalid)
Yum Update nothing provides libarmadillo.so.12()(64bit) needed by gdal36-libs-3.6.4-6PGDG.rhel9.x86_64 from pgdg-common
Reported by: | marc3932 | Owned by: | pramsey |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.4.3 |
Component: | postgis | Version: | 3.4.x |
Keywords: | Cc: | marc3932 |
Description (last modified by )
*PROBLEM*
*yum update nothing provides libarmadillo.so.12()(64bit) needed by gdal36-libs-3.6.4-6PGDG.rhel9.x86_64 from pgdg-common *
[root@rhel9-pg14 ~]# yum update —exclude=postgis33_14 —exclude=postgresql14*
Updating Subscription Management repositories. EPEL_9 24 kB/s | 2.3 kB 00:00 Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs) 39 kB/s | 4.5 kB 00:00 Red Hat CodeReady Linux Builder for RHEL 9 x86_64 (RPMs) 38 kB/s | 4.5 kB 00:00 Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs) 37 kB/s | 4.1 kB 00:00 Error:
Problem: cannot install the best update candidate for package gdal36-libs-3.6.4-5PGDG.rhel9.x86_64
- nothing provides libarmadillo.so.12()(64bit) needed by gdal36-libs-3.6.4-6PGDG.rhel9.x86_64 from pgdg-common
(try to add '—skip-broken' to skip uninstallable packages or '—nobest' to use not only best candidate packages) [root@rhel9-pg14 ~]#
*NOTE:* —skip-broken still returns the same error message, and —nobest just skips the gdal36-libs update
*RHEL 9.3 DETAILS*
[root(at)rhel9-pg14 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 9.3 (Plow) [root(at)rhel9-pg14 ~]#
[root(at)rhel9-pg14 ~]# rpm -qa | grep postgres | sort
postgresql14-14.10-1PGDG.rhel9.x86_64 postgresql14-contrib-14.10-1PGDG.rhel9.x86_64 postgresql14-libs-14.10-1PGDG.rhel9.x86_64 postgresql14-server-14.10-1PGDG.rhel9.x86_64
[root(at)rhel9-pg14 ~]# rpm -qa | grep postgis | sort
postgis34_14-3.4.0-1PGDG.rhel9.x86_64
[root@rhel9-pg14 ~]# rpm -qa | grep armadillo | sort
armadillo-10.8.2-4.el9.x86_64
[root@rhel9-pg14 ~]# rpm -qa | grep gdal | sort
gdal35-libs-3.5.3-7PGDG.rhel9.x86_64 gdal36-libs-3.6.4-5PGDG.rhel9.x86_64
[root(at)rhel9-pg14 ~]# subscription-manager repos —list-enabled
Available Repositories in /etc/yum.repos.d/redhat.repo
Repo ID: rhel-9-for-x86_64-appstream-rpms Repo Name: Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs) Repo URL: https://red-inf-cap-p01.esri.com/pulp/content/ESRI/LEP_Patch/cv_patch/content/dist/rhel9/$releasever/x86_64/appstream/os Enabled: 1
Repo ID: ESRI_EPEL_9_EPEL_9 Repo Name: EPEL_9 Repo URL: https://red-inf-cap-p01.esri.com/pulp/content/ESRI/LEP_Patch/cv_patch/custom/EPEL_9/EPEL_9 Enabled: 1
Repo ID: rhel-9-for-x86_64-baseos-rpms Repo Name: Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs) Repo URL: https://red-inf-cap-p01.esri.com/pulp/content/ESRI/LEP_Patch/cv_patch/content/dist/rhel9/$releasever/x86_64/baseos/os Enabled: 1
Repo ID: codeready-builder-for-rhel-9-x86_64-rpms Repo Name: Red Hat CodeReady Linux Builder for RHEL 9 x86_64 (RPMs) Repo URL: https://red-inf-cap-p01.esri.com/pulp/content/ESRI/LEP_Patch/cv_patch/content/dist/rhel9/$releasever/x86_64/codeready-builder/os Enabled: 1
[root(at)rhel9-pg14 ~]# ls -la /etc/yum.repos.d/
total 52 drwxr-xr-x. 2 root root 85 Jan 31 16:13 . drwxr-xr-x. 136 root root 8192 Feb 2 10:33 .. -rw-r—r—. 1 root root 13067 Dec 25 15:11 pgdg-redhat-all.repo -rw-r—r—. 1 root root 14013 Oct 17 04:10 pgdg-redhat-all.repo.old -rw-r—r—. 1 root root 4657 Jan 31 16:09 redhat.repo [root(at)rhel9-pg14 ~]#
Change History (4)
comment:1 by , 10 months ago
Description: | modified (diff) |
---|
comment:2 by , 10 months ago
comment:3 by , 9 months ago
Milestone: | PostGIS 3.4.2 → PostGIS 3.4.3 |
---|
comment:4 by , 9 months ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Please report build issues to the builder, as they won't get fixed here.
Armadillo 12 packages *are* in the EPEL repo: https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/Packages/a/
We have an internal Satellite that we pull from the EPEL repo. The Satellite Repos are refreshed daily by the IT department. It seems then that the EPEL repo has not been refreshed. I will check with my IT department.