How to Install and Uninstall update-test-affects-package-manager Package on openSuSE Tumbleweed
Last updated: November 26,2024
1. Install "update-test-affects-package-manager" package
This guide let you learn how to install update-test-affects-package-manager on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
update-test-affects-package-manager
Copied
2. Uninstall "update-test-affects-package-manager" package
Please follow the guidelines below to uninstall update-test-affects-package-manager on openSuSE Tumbleweed:
$
sudo zypper remove
update-test-affects-package-manager
Copied
3. Information about the update-test-affects-package-manager package on openSuSE Tumbleweed
Information for package update-test-affects-package-manager:
------------------------------------------------------------
Repository : openSUSE-Tumbleweed-Update
Name : update-test-affects-package-manager
Version : 5.1-2.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 484 B
Installed : No
Status : not installed
Source package : update-test-trivial-5.1-2.2.src
Summary : Test update that requires a software stack restart
Description :
Package for testing the update stack during product development.
An update for this package should be installed first by the
update stack and then ask the user to run the update process
again to apply other updates that might be available. This is
used, for example, to update packages from the software update
stack (zypper, libzypp, packagekit, etc).
------------------------------------------------------------
Repository : openSUSE-Tumbleweed-Update
Name : update-test-affects-package-manager
Version : 5.1-2.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 484 B
Installed : No
Status : not installed
Source package : update-test-trivial-5.1-2.2.src
Summary : Test update that requires a software stack restart
Description :
Package for testing the update stack during product development.
An update for this package should be installed first by the
update stack and then ask the user to run the update process
again to apply other updates that might be available. This is
used, for example, to update packages from the software update
stack (zypper, libzypp, packagekit, etc).