From: Pavel Machek <pavel@denx.de>
To: Kento Yoshida <kento.yoshida.wz@renesas.com>
Cc: "cip-security@lists.cip-project.org"
<cip-security@lists.cip-project.org>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] Python 3.x vs 2.7
Date: Fri, 3 Apr 2020 23:47:08 +0200 [thread overview]
Message-ID: <20200403214708.GA32080@duo.ucw.cz> (raw)
In-Reply-To: <TYAPR01MB2399241EB327E673BD6F48EFDFC60@TYAPR01MB2399.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]
Hi!
>
> FYI, unfortunately we couldn't find the alternative package for system backup. The duplicity is the best package for us from the license and num of dependencies point of view.
> See the following.
>
> <duplicity>
> Encryption: Yes
> Schedule backup: No
> Incremental backup: Yes
> License: GPL v2
> Dependencies count (aprox): 80
> Reference: http://duplicity.nongnu.org/features.ht
I'm not sure what your exact requirements are, but have you considered
"tar"? It should be possible to pipe its output to aespipe (and
possibly other tools) to get encryption, and it should be able to do
incremental backups...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-04-03 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 9:58 [cip-dev] Python 3.x vs 2.7 Kento Yoshida
2020-04-02 23:19 ` nobuhiro1.iwamatsu
2020-04-03 1:50 ` Kento Yoshida
2020-04-06 7:35 ` Punit Agrawal
2020-04-03 21:47 ` Pavel Machek [this message]
2020-04-06 10:15 ` Jan Kiszka
2020-04-06 21:52 ` Pavel Machek
2020-04-07 6:48 ` Kento Yoshida
2020-04-08 9:24 ` [cip-security] " masashi.kudo
2020-04-16 10:14 ` Kento Yoshida
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200403214708.GA32080@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=cip-security@lists.cip-project.org \
--cc=kento.yoshida.wz@renesas.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox