I am having trouble updating a SLES 12.5 server. Zypper is not working supposedly due to another zypper process already running:

# zypper lu
System management is locked by the application with pid 25074 (zypper).
Close this application before trying again.

If I try again, the PID changes:

# zypper lu
System management is locked by the application with pid 27117(zypper).
Close this application before trying again.

If I try to kill 27117, it doesn't work as it is not there anymore:

# kill 27117
bash: kill: (27117) - No such process

The PID is stored in

# cat /var/run/zypp.pid
31776

and here too, if I repeat the command, I get a different PID:

# cat /var/run/zypp.pid
525

This is what zypper.log looks like when I issue a zypper lu command:

2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(main):97 ===== Hi, me zypper 1.13.64
2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(main):98 ===== 'zypper' 'lu' =====
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(_autodetectSystemArchitecture):73 Uname architecture is 'x86_64'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(_autodetectTextLocale):209 Default text locale is 'en'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(Impl):343 libzypp: 16.22.8
2023-10-10 22:10:52  myhostname(27119) [zypp] IniParser.cc(parse):84 Start parsing /etc/zypp/zypp.conf[g___]
2023-10-10 22:10:52  myhostname(27119) [zypp] IniParser.cc(parse):138 Done parsing /etc/zypp/zypp.conf[_eF_]
2023-10-10 22:10:52  myhostname(27119) [Progress++] ProgressData.cc(report):88 {#1|/etc/zypp/zypp.conf}END
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(Impl):621 ZConfig singleton created.
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 libzypp: 16.22.8
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 libsolv: 0.6.39
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 zypp.conf: '/etc/zypp/zypp.conf'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 TextLocale: 'en' (en)
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 SystemArchitecture: 'x86_64' (x86_64)
2023-10-10 22:10:52  myhostname(27119) [zypp] PathInfo.cc(assert_dir):354 mkdir /var/tmp/zypp.hVcxMA/zypper 00755
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(Zypper):552 Zypper instance created.
2023-10-10 22:10:52  myhostname(27119) [zypper] media.h(MediaCallbacks):182 Set media callbacks..
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):891 START
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 START MEASURE(ReadConfig)
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):21 Going to read zypper config using Augeas...
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):103 Done reading conf files:
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):108 user conf read: no
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):109 global conf read: yes
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 ELAPSED(ReadConfig) 0 (u 0.01 s 0.00 c 0.00)
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 MEASURE(ReadConfig) 0 (u 0.01 s 0.00 c 0.00) [0 (u 0.00 s 0.00 c 0.00)]
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1019 Verbosity 1
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1020 Output type 1
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1280 repos.d dir = /etc/zypp/repos.d
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1281 cache dir = /var/cache/zypp
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1282 raw cache dir = /var/cache/zypp/raw
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1283 solv cache dir = /var/cache/zypp/solv
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1284 package cache dir = /var/cache/zypp/packages
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):1296 Repositories enabled
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):1414 DONE
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):1606 START
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):3536 Done parsing options.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):3555 Done
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(_openLockFile):168 Open lockfile /var/run/zypp.pid
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(readLockFile):223 read: Lockfile /var/run/zypp.pid has pid 27117 (our pid: 27119)
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(isProcessRunning):195 Checking /proc/27117{d 0555 0/0}
2023-10-10 22:10:52  myhostname(27119) [zypp++] ZYppFactory.cc(isProcessRunning):209 Is running: zypper
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(zyppLocked):270 27117 is running and has a ZYpp lock. Sorry.
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(_closeLockFile):186 Close lockfile /var/run/zypp.pid
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 ZYppFactory.cc(getZYpp):404 THROW:    System management is locked by the application with pid 27117 (zypper).
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Close this application before trying again.
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(assertZYppPtrGod):267 CAUGHT:   System management is locked by the application with pid 27117 (zypper).
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Close this application before trying again.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(assertZYppPtrGod):303 A ZYpp transaction is already in progress.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.h(setExitCode):250 setExitCode 7
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(assertZYppPtrGod):307 THROW:    ZYpp locked
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(safeDoCommand):1582 CAUGHT:   ZYpp locked
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(safeDoCommand):1583 Caught exit request: exitCode 7
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(cleanup):5575 START
2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(~Bye):82 ===== Exiting main() =====
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(~Zypper):559 Zypper instance destroyed. Bye!
2023-10-10 22:10:52  myhostname(27119) [zypp] PathInfo.cc(recursive_rmdir):435 recursive_rmdir /var/tmp/zypp.hVcxMA
2023-10-10 22:10:52  myhostname(27119) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.hVcxMA{d 0700 0/0}

Any idea of what could be going on here? I have solved this in the past by rebooting, but I want to find a better, not so drastic solution. **UPDATE**: I never found the solution, but I found a rude workaround. Since the PID keeps changing that means that after a process closes and before the new one is spawn, there is a time gap where I can run zypper lu. So I just try again and again until I hit that gap and it works just fine.

I thought I'd do some cleaning up, so I ran:

zypper packages --orphaned | awk -F'|' 'NR==0 || NR==1 || NR==2 || NR==3 || NR==4 {next} {print $3}' \
    | grep -v Name | sudo xargs zypper remove --clean-deps

And somehow zypper itself was one of the packages that got removed. So now zypper is missing, how do I go about getting it back?

## Situation Our company has an internal Server * OpenSUSE Leap 15.5 * Python 3.6(.15) * Python 2.7(.18) see details for more information ## Task As Python 3.6 is already EOL we want to **install a newer Python** (3.10 or 3.11).
In order to **not break anything** I would like to 1. install the new python in parallel 1. install it additionally (not replacing or breaking any of the existing installations or aliasses) 1. have it available from anywhere (scripts) As this Server is vital to our development process, I would like to go for the lowest risk possible. ## Questions 1. How risky is installing another python with regards to system stability, the other python installations and the "python" binary/symlink? 1. How should I install python in a lowest-risk-manner? ## Details > ***:~> cat /etc/os-release > NAME="openSUSE Leap" > VERSION="15.5" > ID="opensuse-leap" > ID_LIKE="suse opensuse" > VERSION_ID="15.5" > PRETTY_NAME="openSUSE Leap 15.5" > ANSI_COLOR="0;32" > CPE_NAME="cpe:/o:opensuse:leap:15.5" > BUG_REPORT_URL="https://bugs.opensuse.org " > HOME_URL="https://www.opensuse.org/ " > DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap " > LOGO="distributor-logo-Leap" > > > ***:~> zypper info python > ... > Repository : Update repository with updates from SUSE Linux Enterprise 15 > Name : python > Version : 2.7.18-150000.51.1 > Arch : x86_64 > Vendor : SUSE LLC > Installed Size : 1.4 MiB > Installed : Yes (automatically) > Status : up-to-date > Source package : python-2.7.18-150000.51.1.src > Upstream URL : https://www.python.org/ > Summary : Python Interpreter > ... > > ***:~> zypper info python3 > ... > Repository : Update repository with updates from SUSE Linux Enterprise 15 > Name : python3 > Version : 3.6.15-150300.10.48.1 > Arch : x86_64 > Vendor : SUSE LLC > Installed Size : 141.3 KiB > Installed : Yes (automatically) > Status : up-to-date > Source package : python3-3.6.15-150300.10.48.1.src > Upstream URL : https://www.python.org/ > Summary : Python 3 Interpreter > ....

While installing and running a processd using zypper am getting below error message, the processd is installed, unable to run as expected, Please help, error trying to compare the processd system key: system-key missing on disk Started process Daemon daemon.go:502: gracefully waiting for running hooks daemon.go:504: done waiting for running hooks daemon stop requested to wait for socket activation processd.service: Deactivated successfully.

I have a local repo that has some rpms in it. The repo xmls etc are up to date. When I find an rpm I don't have, I want to be able to download it, not install it obviously, and put that rpm into the repo dir. I see I can use zypper install --download-only but this seems to only work when I haven't got the package installed on my box, else it says 'already' installed. It also doesn't allow me to state the version/edition/rev of the package I want. This is no good to me. How can I get a rpm from my active repositories and store it to a specified location? I don't mind installing a new tool if zypper aint the way to go.

I need to find out what repo 'git-core' comes from. $ zypper search git-core Refreshing service 'nu_novell_com'. Removing repository 'SLE11-WebYaST-SP1-Pool' [done] Removing repository 'SLE11-WebYaST-SP1-Updates' [done] Adding repository 'SLES11-SP2-Updates' [done] Adding repository 'SLE11-WebYaST-SP2-Pool' [done] Adding repository 'SLES11-SP2-Extension-Store' [done] Adding repository 'SLES11-SP2-Core' [done] Adding repository 'SLE11-WebYaST-SP2-Updates' [done] Adding repository 'SLE11-SP2-Debuginfo-Core' [done] Adding repository 'SLE11-SP2-Debuginfo-Updates' [done] Retrieving repository 'SLES11-SP2-Core' metadata [done] Building repository 'SLES11-SP2-Core' cache [done] Retrieving repository 'SLES11-SP2-Extension-Store' metadata [done] Building repository 'SLES11-SP2-Extension-Store' cache [done] Retrieving repository 'SLES11-SP2-Updates' metadata [done] Building repository 'SLES11-SP2-Updates' cache [done] Loading repository data... Reading installed packages... S | Name | Summary | Type --+----------+----------------+-------- i | git-core | Core git tools | package Searching the man pages for zypper, it seems like 'what-provides' would provide this information. It just says "System Packages". $zypper what-provides git-core Refreshing service 'nu_novell_com'. Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+----------+---------+----------------+--------+------------------------------------------------------------------ v | git-core | package | 2.0.0-201.1 | x86_64 | Software configuration management (SLE_11_SP2) v | git-core | package | 1.6.0.2-7.31.2 | x86_64 | SUSE-Linux-Enterprise-Software-Development-Kit-11-SP2 11.2.2-1.66 v | git-core | package | 2.0.0-201.1 | i586 | Software configuration management (SLE_11_SP2) i | git-core | package | 1.8.4-165.1 | x86_64 | (System Packages) These are the repos that exist. ls /etc/zypp/repos.d/ nu_novell_com:SLE11-SP2-Debuginfo-Core.repo nu_novell_com:SLES11-SP1-Pool.repo nu_novell_com:SLE11-SP2-Debuginfo-Updates.repo nu_novell_com:SLES11-SP1-Updates.repo nu_novell_com:SLE11-WebYaST-SP2-Pool.repo nu_novell_com:SLES11-SP2-Core.repo nu_novell_com:SLE11-SP1-Debuginfo-Pool.repo nu_novell_com:SLE11-WebYaST-SP2-Updates.repo nu_novell_com:SLES11-SP2-Extension-Store.repo nu_novell_com:SLE11-SP1-Debuginfo-Updates.repo nu_novell_com:SLES11-Extras.repo nu_novell_com:SLES11-SP2-Updates.repo On CentOS I would run a repoquery or yum info. How can I tell which repo git 1.8.4 comes from on sles? **Update** I fixed this by using a SLES 11 SP2 image instead of SLES 11 SP1. Leaving question open if someone can still answer the question.

I use zypper si command to install source package in SUSE: localhost:/dev/disk/by-id # zypper si zlib Reading installed packages... Loading repository data... Resolving package dependencies... The following source package is going to be installed: zlib 1 source package to install. Overall download size: 587.0 KiB. Already cached: 0 B. After the operation, additional 597.7 KiB will be used. Continue? [y/n/? shows all options] (y): y Checking for file conflicts: ........................................................................................................[done] But when I use the command: zypper se to check package state, it shows "not installed": localhost:/dev/disk/by-id # zypper se zlib Loading repository data... Reading installed packages... S | Name | Summary | Type --+------+--------------------------+----------- | zlib | Data Compression Library | srcpackage Could anyone give some clues?

I would like the help of someone with more experience to understand the differences and how those 5 things are connected: libzypp, YaST, Zypper, PackageKit and Gnome Software Center. Here is my take away from a day of research: - libzypp: the backend package management library that powers applications like YaST, zypper and the openSUSE implementation of PackageKit - YaST: it's a system configuration tool that happens to allow the management of dependencies through libzypp. It provides both a graphical interface (GTK) and an interface through the terminal (not sure what it's used here) - Zypp: the official command-line package manager of Open SUSE - PackageKit: that's where things get a little fuzzy for me. This seems to be a package manager abstraction - its supposed to abstract all the differences between apt, zypper, yum, etc - Gnome Software Center: it's a graphical interface (GTK) to install dependencies through package kit - so it's supposed to work with all distros, regardless of the underline package manager used If I understood this correct: - Why don't I see the apps installed through YaST in the Gnome Software Center and vice-versa? - Why would I want to keep Gnome Software Center installed if the previous point (^) doesn't happen? To me this thing just seems cluttered

I am asking to install a package B that is replacing (**and** conflicting with) another package A. In order to do it without user input, in yum I use --allowerasing. Is there an option like that for zypper? The user is getting this message from zypper:

Resolving package dependencies...

Problem: the to be installed B-some-version.x86_64 conflicts with 'A' provided by the installed A-some-other-version.x86_64
 Solution 1: deinstallation of A-some-other-version.x86_64
 Solution 2: do not install B-some-version.x86_64

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

I tried with --force which made no difference and I want it to go with option 1.

A question exists regarding how to mark an RPM as automatically installed , but that question concerns Fedora. I am using zypper on OpenSUSE as an end-user and would like to know how to mark a package so that it will (or will not) show in the list of unneeded packages, with zypper packages --unneeded. I am looking for something along the lines of zypper mark autoselected [packageName]. A Novell Bugzilla bug mentions a status of byUser, and possibly autoselected, so it sounds like this information exists somewhere. I would like to know how to modify it.

I'm using openSUSE Leap 15.5 and zypper version 1.14.68 Upon startup, the system will attempt to run the updater, which fails. In order to get a more detailed error, I updated manually using: sudo zypper update I receive the following error: > File './x86_64/libsoup-3_0-0-3.0.4-150400.1.6.x86_64.rpm' not found on medium 'https://download.opensuse.org/repositories/openSUSE:/Leap:/15.5/standard/ ' This error then prevents zypper from updating other packages as well (if I proceed with using the 'ignore' command). I'm trying to make sense of this error, but not quite sure where to start. It appears that it has the incorrect repository listed for an important dependency?

As per the zypper manual https://en.opensuse.org/SDB:Zypper_manual_%28plain%29 , the parameter "--force-resolution" is present in the zypper update command but when I am trying to use this parameter in the command, I am getting the following error: Unknown option '--force-resolution' Is this parameter recently removed? I am using SUSE 12 SP5

A major advantage of doing an in-place upgrade compared to doing a clean install, is that all accounts, configurations, and installed programs are kept intact. Using Windows Subsystem for Linux (WSL) , I have installed a fresh instance of openSUSE 42. 1 ### *How can I perform an in-place upgrade of openSUSE 42 to 15.x?* My primary interest is in going from openSUSE 42 to the latest openSUSE version. At the time of writing, Leap 15.4 is the latest active openSUSE release . #### Motivation WSL still offers only version 42.2 of openSUSE when installing from the command line. Considering that the lifetime of openSUSE 42.2 officially ended in January 2018 – almost five years ago – it would make sense to upgrade to a newer version. #### Caution! *Make sure there is enough free disk space before considering an in-place upgrade, in this case, at least about 5 GiB.* ## References * How to install Linux on Windows with WSL * Active openSUSE Leap releases * openSUSE Leap discontinued distributions --- 1 Open [Windows CMD.exe](https://ss64.com/nt/cmd.html) as administrator (WinKey+r, type cmd, hold down Ctrl+Shift, press Enter). Then install openSUSE 42.2 by running : wsl.exe --install --distribution openSUSE-42

I am writing a script that installs some packages and does some configuration work. I want the script to install a specific major version of a package, but I do not care which minor version of the package it is. More to the point, I want it to install the latest 2.y.z release of the package, but not 1.y.z or 3.y.z (or any other major version number). I have tried (without success) - zypper install 'mypackage=2' - `zypper install 'mypackage>11' 'mypackage=2.0.0' 'mypackage 'mypackage>=2.0.0' not found in package names. Trying capabilities. No > provider of 'mypackage >= 2.0.0' found. However, after that message, it still proceeds with installing mypackage-1.5.0, because that satisfies the second package-edition specified.

I have a problem with SUSE 12 zypper. I need to install an unsigned package with zypper in non-interactive mode from script. Unfortunately, zypper version is 1.13 and there is no option for flag --allow-unsigned-rpm. So I've been trying to "pipe" output of the printf command into zypper, but having no luck so far. Here is an example of what I am doing: printf "y\ni\n" | sudo zypper install UNSIGNED_RPM_PATH_HERE What am I doing wrong? This pipe works for every other script I tried to write myself.

On SUSE Tumbleweed, just updated (2023-08-20) and I have seen in the log a package that for sure I've never manually installed ... (343/370) Installing: trainwreck-5.109.0-1.1.x86_64 .......... [done] ... When I used Debian, I was able to satisfy my curiosity using $ apt rdepends trainwreck trainwreck Reverse Depends: Depends: model-train $ Having googled a little bit, no a substantial bit, the most relevant find shows that it can be done, at least for direct dependencies, but is no help in making one, a clueless one like me, understand how the figures were obtained. How can I obtain at least a list of the reverse dependencies of package trainwreck on Suse Tumbleweed?

I upgraded a laptop from openSUSE 15.3 to 15.4 today. During the process, there were many prompts related to requirements that could not be provided. After running the upgrade process, fixing a number of repo URLs and rebooting, both sudo zypper verify and sudo zypper ref && sudo zypper up give the following error message:

zypper: symbol lookup error: /usr/lib64/libzypp.so.1722: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11

I have also noticed that in Yast, I can't get beyond the first screen: when I click "Software Management" or any of the other items in the control centre, the throbber spins for a few seconds but nothing else happens. Output of rpm -q libzypp:

libzypp-17.31.2-150200.45.1.x86_64

Output of rpm -q zypper:

zypper-1.14.57-150200.39.1.x86_64

Output of rpm -q -i libzypp zypper:

Name        : libzypp
Version     : 17.31.2
Release     : 150200.45.1
Architecture: x86_64
Install Date: Fri 14 Oct 2022 19:24:59 CEST
Group       : System/Packages
Size        : 10145384
License     : GPL-2.0-or-later
Signature   : RSA/SHA256, Thu 06 Oct 2022 16:21:42 CEST, Key ID 70af9e8139db7c82
Source RPM  : libzypp-17.31.2-150200.45.1.src.rpm
Build Date  : Thu 06 Oct 2022 16:15:12 CEST
Build Host  : sheep16
Relocations : (not relocatable)
Packager    : https://www.suse.com/ 
Vendor      : SUSE LLC 
URL         : https://github.com/openSUSE/libzypp 
Summary     : Library for package, patch, pattern and product management
Description :
libzypp is the package management library that powers applications
like YaST, zypper and the openSUSE/SLE implementation of PackageKit.

libzypp provides functionality for a package manager:

  * An API for package repository management, supporting most common
    repository metadata formats and signed repositories.
  * An API for solving packages, products, patterns and patches
    (installation, removal, update and distribution upgrade
    operations) dependencies, with additional features like locking.
  * An API for commiting the transaction to the system over a rpm
    target. Supporting deltarpm calculation, media changing and
    installation order calculation.
  * An API for browsing available and installed software, with some
    facilities for programs with an user interface.
Distribution: SUSE Linux Enterprise 15
Name        : zypper
Version     : 1.14.57
Release     : 150200.39.1
Architecture: x86_64
Install Date: Fri 14 Oct 2022 19:25:00 CEST
Group       : System/Packages
Size        : 8306495
License     : GPL-2.0-or-later
Signature   : RSA/SHA256, Thu 06 Oct 2022 16:31:56 CEST, Key ID 70af9e8139db7c82
Source RPM  : zypper-1.14.57-150200.39.1.src.rpm
Build Date  : Thu 06 Oct 2022 16:30:31 CEST
Build Host  : sheep28
Relocations : (not relocatable)
Packager    : https://www.suse.com/ 
Vendor      : SUSE LLC 
URL         : https://github.com/openSUSE/zypper 
Summary     : Command line software manager using libzypp
Description :
Zypper is a command line tool for managing software. It can be used to add
package repositories, search for packages, install, remove, or update packages,
install patches, hardware drivers, verify dependencies, and more.

Zypper can be used interactively or non-interactively by user, from scripts,
or front-ends.

Authors:
--------
    Jan Kupec 
    Michael Andres 
    Duncan Mac-Vicar 
    Martin Vidner 
    Josef Reidinger 
Distribution: SUSE Linux Enterprise 15

I have also noticed that [this libzypp page](https://software.opensuse.org/package/libzypp) says, > There is no official package available for openSUSE Leap 15.4 Is there any way I can solve this issue and make zypper (and Yast) work again?