How to Install and Uninstall python311-patatt Package on openSuSE Tumbleweed
Last updated: November 12,2024
1. Install "python311-patatt" package
Please follow the step by step instructions below to install python311-patatt on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python311-patatt
Copied
2. Uninstall "python311-patatt" package
Please follow the step by step instructions below to uninstall python311-patatt on openSuSE Tumbleweed:
$
sudo zypper remove
python311-patatt
Copied
3. Information about the python311-patatt package on openSuSE Tumbleweed
Information for package python311-patatt:
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python311-patatt
Version : 0.6.3-2.4
Arch : noarch
Vendor : openSUSE
Installed Size : 254.9 KiB
Installed : No
Status : not installed
Source package : python-patatt-0.6.3-2.4.src
Upstream URL : https://git.kernel.org/pub/scm/utils/patatt/patatt.git/
Summary : Cryptographic patch attestation for the masses
Description :
This utility allows an easy way to add end-to-end cryptographic attestation to
patches sent via mail. It does so by adapting the DKIM email signature standard
to include cryptographic signatures via the X-Developer-Signature email header.
If your project workflow doesn't use patches sent via email, then you don't
need this and should simply start signing your tags and commits.
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python311-patatt
Version : 0.6.3-2.4
Arch : noarch
Vendor : openSUSE
Installed Size : 254.9 KiB
Installed : No
Status : not installed
Source package : python-patatt-0.6.3-2.4.src
Upstream URL : https://git.kernel.org/pub/scm/utils/patatt/patatt.git/
Summary : Cryptographic patch attestation for the masses
Description :
This utility allows an easy way to add end-to-end cryptographic attestation to
patches sent via mail. It does so by adapting the DKIM email signature standard
to include cryptographic signatures via the X-Developer-Signature email header.
If your project workflow doesn't use patches sent via email, then you don't
need this and should simply start signing your tags and commits.