<metapackage xmlns:os="http://opensuse.org/Standards/One_Click_Install" xmlns="http://opensuse.org/Standards/One_Click_Install">
  <group>
    <repositories>
      <repository recommended="true">
        <name>Archiving:Backup</name>
        <summary>Nobody wants backup, they only want restore.</summary>
        <description>This project contains various backup/restore tools. While building is enabled for other distributions then Tumbleweed/Factory, primary purpose of this project is development, not backporting for older releases. Do not add this project repositories to your systems unless you know what you are doing and are willing to fix issues you encounter.</description>
        <url>https://download.opensuse.org/repositories/Archiving:/Backup/16.0/</url>
      </repository>
      <repository recommended="true">
        <name>openSUSE:Leap:16.0</name>
        <summary>openSUSE Leap 16.0 based on SLFO</summary>
        <description>Leap 16.0 based on SLES 16.0 (specifically SLFO:1.2)</description>
        <url>https://download.opensuse.org/distribution/leap/16.0/repo/oss/</url>
      </repository>
      <repository recommended="true">
        <name>openSUSE:Backports:SLE-16.0</name>
        <summary>Community packages for SLE-16.0</summary>
        <description>Community packages for SLE-16.0</description>
        <url>https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-16.0/standard/</url>
      </repository>
      <repository recommended="false">
        <name>SUSE:SLFO:1.2</name>
        <summary>SLFO 1.2 (the base for openSUSE 16.0 and SLES 16.0)</summary>
        <description></description>
        <url>https://download.opensuse.org/repositories/SUSE:/SLFO:/1.2/standard/</url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>duplicity</name>
        <summary>Encrypted bandwidth-efficient backup using the rsync algorithm</summary>
        <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.</description>
      </item>
    </software>
  </group>
</metapackage>
