How to Install and Uninstall duplicity Package on openSUSE Leap
Last updated: November 26,2024
1. Install "duplicity" package
Please follow the steps below to install duplicity on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
duplicity
Copied
2. Uninstall "duplicity" package
Here is a brief guide to show you how to uninstall duplicity on openSUSE Leap:
$
sudo zypper remove
duplicity
Copied
3. Information about the duplicity package on openSUSE Leap
Information for package duplicity:
----------------------------------
Repository : Main Repository
Name : duplicity
Version : 0.8.21-150400.1.7
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 2.3 MiB
Installed : No
Status : not installed
Source package : duplicity-0.8.21-150400.1.7.src
Upstream URL : https://duplicity.gitlab.io/duplicity-web/
Summary : Encrypted bandwidth-efficient backup using the rsync algorithm
Description :
Duplicity incrementally backs up files and directories by encrypting
tar-format volumes with GnuPG and uploading them to a remote (or local)
file server. In theory many remote backends are possible; right now
local, ssh/scp, ftp, rsync, HSI, WebDAV, and Amazon S3 backends are
written.
Because duplicity uses librsync, the incremental archives are space
efficient and only record the parts of files that have changed since
the last backup. Currently duplicity supports deleted files, full unix
permissions, directories, symbolic links, fifos, etc., but not hard
links.
----------------------------------
Repository : Main Repository
Name : duplicity
Version : 0.8.21-150400.1.7
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 2.3 MiB
Installed : No
Status : not installed
Source package : duplicity-0.8.21-150400.1.7.src
Upstream URL : https://duplicity.gitlab.io/duplicity-web/
Summary : Encrypted bandwidth-efficient backup using the rsync algorithm
Description :
Duplicity incrementally backs up files and directories by encrypting
tar-format volumes with GnuPG and uploading them to a remote (or local)
file server. In theory many remote backends are possible; right now
local, ssh/scp, ftp, rsync, HSI, WebDAV, and Amazon S3 backends are
written.
Because duplicity uses librsync, the incremental archives are space
efficient and only record the parts of files that have changed since
the last backup. Currently duplicity supports deleted files, full unix
permissions, directories, symbolic links, fifos, etc., but not hard
links.