How to Install and Uninstall python2-testrepository Package on openSUSE Leap
Last updated: March 04,2025
Deprecated! Installation of this package may no longer be supported.
1. Install "python2-testrepository" package
This tutorial shows how to install python2-testrepository on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python2-testrepository
Copied
2. Uninstall "python2-testrepository" package
This guide covers the steps necessary to uninstall python2-testrepository on openSUSE Leap:
$
sudo zypper remove
python2-testrepository
Copied
3. Information about the python2-testrepository package on openSUSE Leap
Information for package python2-testrepository:
-----------------------------------------------
Repository : Main Repository
Name : python2-testrepository
Version : 0.0.20-bp153.1.17
Arch : noarch
Vendor : openSUSE
Installed Size : 1,0 MiB
Installed : No
Status : not installed
Source package : python-testrepository-0.0.20-bp153.1.17.src
Summary : A repository of test results
Description :
This project provides a database of test results which can be used as part of
developer workflow to ensure/check things like:
* No commits without having had a test failure, test fixed cycle.
* No commits without new tests being added.
* What tests have failed since the last commit (to run just a subset).
* What tests are currently failing and need work.
Test results are inserted using subunit (and thus anything that can output
subunit or be converted into a subunit stream can be accepted).
-----------------------------------------------
Repository : Main Repository
Name : python2-testrepository
Version : 0.0.20-bp153.1.17
Arch : noarch
Vendor : openSUSE
Installed Size : 1,0 MiB
Installed : No
Status : not installed
Source package : python-testrepository-0.0.20-bp153.1.17.src
Summary : A repository of test results
Description :
This project provides a database of test results which can be used as part of
developer workflow to ensure/check things like:
* No commits without having had a test failure, test fixed cycle.
* No commits without new tests being added.
* What tests have failed since the last commit (to run just a subset).
* What tests are currently failing and need work.
Test results are inserted using subunit (and thus anything that can output
subunit or be converted into a subunit stream can be accepted).