From: Oleg Pykhalov <go.wigust@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Eric Bavier <bavier@member.fsf.org>, 30448@debbugs.gnu.org
Subject: [bug#30448] Breaking rdiff-backup and btar (was Re: [bug#30448] Update librsync to 2.0.1)
Date: Sat, 28 Apr 2018 19:48:25 +0300 [thread overview]
Message-ID: <87muxn6zvq.fsf@gmail.com> (raw)
In-Reply-To: <20180425172333.GA25054@jasmine.lan> (Leo Famulari's message of "Wed, 25 Apr 2018 13:23:33 -0400")
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
Hello,
Leo Famulari <leo@famulari.name> writes:
[…]
> Yeah, it makes me wonder if duplicity is still maintained or not...
The upstream does maintain duplicity. Also I did a version update
0.7.12 -> 0.7.17 in our package recipe. I hope to send it to Guix
patches mailing list after testing it myself for some time.
[…]
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-04-28 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 19:01 [bug#30448] Update librsync to 2.0.1 Leo Famulari
2018-02-15 14:27 ` Ludovic Courtès
2018-04-23 12:58 ` Ludovic Courtès
2018-04-24 17:57 ` [bug#30448] Breaking rdiff-backup and btar (was Re: [bug#30448] Update librsync to 2.0.1) Leo Famulari
2018-04-24 20:30 ` Ludovic Courtès
2018-04-25 17:23 ` Leo Famulari
2018-04-28 16:48 ` Oleg Pykhalov [this message]
2019-02-13 0:00 ` bug#30448: " Leo Famulari
2019-02-13 21:30 ` [bug#30448] Update librsync to 2.0.1 Leo Famulari
2019-02-25 23:24 ` bug#30448: " Leo Famulari
2019-02-13 21:26 ` [bug#30448] [PATCH] gnu: librsync: Update to 2.0.2 Leo Famulari
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=87muxn6zvq.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=30448@debbugs.gnu.org \
--cc=bavier@member.fsf.org \
--cc=leo@famulari.name \
/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).