unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: [PATCH 0/6] Add borg
Date: Thu, 24 Mar 2016 17:55:55 -0400	[thread overview]
Message-ID: <20160324215555.GA2153@jasmine> (raw)
In-Reply-To: <cover.1457998381.git.leo@famulari.name>

On Mon, Mar 14, 2016 at 07:34:20PM -0400, Leo Famulari wrote:
> These patches add the borg backup program [0], which is a more actively
> developed fork of attic [1].

Applied, with changes, as 229b36617a

> 
> Borg is compatible with the current version of python-llfuse (1.0), but
> this required changes in borg [2]. Since attic has not had any updates
> since borg was forked, I think it's reasonable to guess that attic still
> requires python-llfuse@0.41. So, this patch set updates llfuse while
> keeping the old version around.
> 
> These patches also update python-msgpack and clean up its python-2
> variant.
> 
> [0]
> http://borgbackup.readthedocs.org/en/latest/
> 
> [1]
> https://attic-backup.org/
> 
> [2]
> https://github.com/borgbackup/borg/commit/dbec05ab73b30f655021118e62bc94c547870472
> 
> Leo Famulari (6):
>   gnu: python-msgpack: Update to 0.4.7.
>   gnu: python-msgpack: Use 'python2-variant'.
>   gnu: attic: Specify dependency on python-llfuse@0.41.
>   gnu: python-llfuse: Update to 1.0, keep 0.41 variant.
>   gnu: Add borg.
>   gnu: python-llfuse@0.41: Update to 0.41.1.
> 
>  gnu/packages/backup.scm | 65 ++++++++++++++++++++++++++++++++++++++++++++++---
>  gnu/packages/python.scm | 48 +++++++++++++++++++++++++-----------
>  2 files changed, 96 insertions(+), 17 deletions(-)
> 
> -- 
> 2.6.3
> 
> 

      parent reply	other threads:[~2016-03-24 21:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 23:34 [PATCH 0/6] Add borg Leo Famulari
2016-03-14 23:34 ` [PATCH 1/6] gnu: python-msgpack: Update to 0.4.7 Leo Famulari
2016-03-14 23:34 ` [PATCH 2/6] gnu: python-msgpack: Use 'python2-variant' Leo Famulari
2016-03-14 23:34 ` [PATCH 3/6] gnu: attic: Specify dependency on python-llfuse@0.41 Leo Famulari
2016-03-15  8:58   ` Alex Kost
2016-03-15  9:13     ` Leo Famulari
2016-03-14 23:34 ` [PATCH 4/6] gnu: python-llfuse: Update to 1.0, keep 0.41 variant Leo Famulari
2016-03-15  8:53   ` Alex Kost
2016-03-15  9:13     ` Leo Famulari
2016-03-15 10:12       ` Mathieu Lirzin
2016-03-15 16:25         ` Ludovic Courtès
2016-03-21  2:49           ` Leo Famulari
2016-03-21  8:52             ` Alex Kost
2016-03-14 23:34 ` [PATCH 5/6] gnu: Add borg Leo Famulari
2016-03-15  9:11   ` Alex Kost
2016-03-15  9:18     ` Leo Famulari
2016-03-21 21:31       ` Leo Famulari
2016-03-21 22:35         ` Leo Famulari
2016-03-21 22:52           ` Leo Famulari
2016-03-22 20:20             ` Alex Kost
2016-03-22 21:25               ` Leo Famulari
2016-03-23  8:14                 ` Alex Kost
2016-03-23 20:49                   ` Efraim Flashner
2016-03-14 23:34 ` [PATCH 6/6] gnu: python-llfuse@0.41: Update to 0.41.1 Leo Famulari
2016-03-24 21:55 ` Leo Famulari [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160324215555.GA2153@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).