[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#484717: marked as done (RFP: gibak -- A better backup system based on Git)

Your message dated Sat, 12 Jan 2019 09:19:19 +0000
with message-id <20190112091919.o3znidm4heex3cyg@master.debian.org>
and subject line gibak upstream gone
has caused the Debian Bug report #484717,
regarding RFP: gibak -- A better backup system based on Git
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

484717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484717
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Paul Hedderly <prh@debian.org>

* Package name    : gibak
  Version         : 0.3.0
  Upstream Author : Mauricio Fernandez <mfp@acm.org>
* URL             : http://eigenclass.org/hiki/gibak-backup-system-introduction
* License         : GPL => v2 and LGPL v2.1
  Programming Lang: OCaml and bash
  Description     : A better backup system based on Git

As far as "standard" tools go, however, git provides a very nice infrastructure that can be used to build your own system, to wit:
 * it is more space-efficient than most incremental backup schemes, since it does file compression and both textual *and* binary deltas (in particular, it's better than solutions relying on hardlinks or incremental 
backups à la tar/cpio)
 * its transport mechanism is more efficient than rsync's
 * it is fast: recoving your data is *faster* than cp -a
 * you keep the full revision history
 * powerful toolset with a rich vocabulary

Gibak retains all the advantages from Git, and supplements it in some key areas:

 * metadata support
 * management of submodules (nested Git repositories)
 * automation of common operations; for instance, a commit consists of several steps:
   o determining if some files which were committed earlier are ignored now and removing them from the index
   o adding new and modified files to the index
   o registering new git submodules and copying them to a special area under .git
   o committing changes in the index
   o compaction and optimization of the repository

[ I will push a git repo onto colab-maint so if anyone wants to work as a team on this
  then just shout - especially if you are an OCaml wiz. ]


--- End Message ---
--- Begin Message ---
Upstream urls are gone.

--- End Message ---

Reply to: