borgbackup 0.30.0-1 source package in Ubuntu

Changelog

borgbackup (0.30.0-1) unstable; urgency=medium

  * New upstream release.
    - Drop spelling errors patch: upstream
    - rebase patches.
  [ Danny Edel ]
  * fix build by following upstream manpage name change.

 -- Gianfranco Costamagna <email address hidden>  Sun, 24 Jan 2016 09:14:42 +0100

Upload details

Uploaded by:
Danny Edel
Uploaded to:
Sid
Original maintainer:
Danny Edel
Architectures:
any all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
borgbackup_0.30.0-1.dsc 2.1 KiB 63f980f4f08e631454e67309fc70a563f36eb37262b3d823885553974cc596d1
borgbackup_0.30.0.orig.tar.gz 428.7 KiB a467310d2846cd90ddfc371f2d981994ccd8dedf8c2b99a25fd8b5295062e858
borgbackup_0.30.0-1.debian.tar.xz 14.9 KiB 4f5f89b3735301874119388e06c8d9f442556a605c5e0058cb950b3564d5fc5a

Available diffs

No changes file available.

Binary packages built by this source

borgbackup: deduplicating and compressing backup program

 Borg is a deduplicating and compressing backup program. Optionally, it
 also supports authenticated encryption. It was forked from the attic
 backup program.
 .
 The main goal of Borg is to provide an efficient and secure way to
 backup data. The data deduplication technique used makes Borg suitable
 for daily backups since only the changes are stored. The authenticated
 encryption makes it suitable for backups to not fully trusted targets.
 .
 It can push backups to remote repositories accessed via ssh. A client
 pushing a backup invokes "borg serve" on the repository host. It is
 possible to restrict the ssh key to "borg serve" using the
 authorized_keys command= clause.
 .
 Please note that the server and the client should be on the same
 version of borgbackup. Using different versions of borgbackup on
 client and server might result in 'incompatible API version' error
 messages and a non-working backup.
 .
 While there is no direct operations mode for pull-type backups, you
 can configure the backup target in append-only mode, preventing the
 backup source from deleting or altering previous backups.

borgbackup-dbgsym: debug symbols for package borgbackup

 Borg is a deduplicating and compressing backup program. Optionally, it
 also supports authenticated encryption. It was forked from the attic
 backup program.
 .
 The main goal of Borg is to provide an efficient and secure way to
 backup data. The data deduplication technique used makes Borg suitable
 for daily backups since only the changes are stored. The authenticated
 encryption makes it suitable for backups to not fully trusted targets.
 .
 It can push backups to remote repositories accessed via ssh. A client
 pushing a backup invokes "borg serve" on the repository host. It is
 possible to restrict the ssh key to "borg serve" using the
 authorized_keys command= clause.
 .
 Please note that the server and the client should be on the same
 version of borgbackup. Using different versions of borgbackup on
 client and server might result in 'incompatible API version' error
 messages and a non-working backup.
 .
 While there is no direct operations mode for pull-type backups, you
 can configure the backup target in append-only mode, preventing the
 backup source from deleting or altering previous backups.

borgbackup-doc: deduplicating and compressing backup program (documentation)

 Borg is a deduplicating and compressing backup program. Optionally, it
 also supports authenticated encryption. It was forked from the attic
 backup program.
 .
 The main goal of Borg is to provide an efficient and secure way to
 backup data. The data deduplication technique used makes Borg suitable
 for daily backups since only the changes are stored. The authenticated
 encryption makes it suitable for backups to not fully trusted targets.
 .
 It can push backups to remote repositories accessed via ssh. A client
 pushing a backup invokes "borg serve" on the repository host. It is
 possible to restrict the ssh key to "borg serve" using the
 authorized_keys command= clause.
 .
 This is the documentation package