'Resolving package dependencies conflicts in SLES

I am facing issues while downloading certain packages having dependencies, i tried installing glib2-devel but getting this

abc@abc:~> sudo zypper in glib2-devel

Refreshing service ‘Basesystem_Module_15_SP3_x86_64’. Refreshing service ‘SUSE_Linux_Enterprise_Server_15_SP3_x86_64’. Refreshing service ‘Server_Applications_Module_15_SP3_x86_64’. Loading repository data… Reading installed packages… Resolving package dependencies…

Problem: the to be installed glib2-devel-2.62.6-150200.3.9.1.x86_64 requires ‘pkgconfig(libselinux)’, but this requirement cannot be provided not installable providers: libselinux-devel-3.0-1.31.x86_64[Basesystem_Module_15_SP3_x86_64:SLE-Module-Basesystem15-SP3-Pool]

Solution 1: Following actions will be done: downgrade of libselinux1-3.1-1.68.x86_64 to libselinux1-3.0-1.31.x86_64 downgrade of libsemanage1-3.1-3.2.x86_64 to libsemanage1-3.0-1.27.x86_64 downgrade of policycoreutils-3.1-2.2.x86_64 to policycoreutils-3.0-1.20.x86_64 deinstallation of policycoreutils-devel-3.1-2.2.x86_64 downgrade of python3-selinux-3.1-1.2.x86_64 to python3-selinux-3.0-1.20.x86_64 downgrade of python3-setools-4.3.0-1.2.x86_64 to python3-setools-4.2.2-1.19.x86_64 downgrade of selinux-tools-3.1-1.68.x86_64 to selinux-tools-3.0-1.31.x86_64 downgrade of libsepol1-3.1-1.112.x86_64 to libsepol1-3.0-1.31.x86_64 downgrade of python3-policycoreutils-3.1-2.2.noarch to python3-policycoreutils-3.0-1.20.x86_64 downgrade of python3-semanage-3.1-1.2.x86_64 to python3-semanage-3.0-1.19.x86_64 deinstallation of policycoreutils-python-utils-3.1-2.2.noarch

Solution 2: do not install glib2-devel-2.62.6-150200.3.9.1.x86_64

Solution 3: break glib2-devel-2.62.6-150200.3.9.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):

How to solve these dependencies , since i will be installing glib2-devel through ansible.

I tried zypper install --oldpackage libselinux1-3.0-1.31.x86_64 but its again showing the similar package conflict. Any help would be appreciated.



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source