CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Pavel Machek <pavel@denx.de>,
	Kento Yoshida <kento.yoshida.wz@renesas.com>,
	"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: Mon, 6 Apr 2020 23:52:05 +0200	[thread overview]
Message-ID: <20200406215205.GA14162@amd.ucw.cz> (raw)
In-Reply-To: <8d490687-c9fb-239e-5d01-55fec493168f@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

On Mon 2020-04-06 12:15:16, Jan Kiszka wrote:
> On 03.04.20 23:47, Pavel Machek wrote:
> > 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...
> 
> I suppose there is that concern about GPLv3 again (as with broadly used
> rsync) - which is generally overrated. There exists legal views that already
> GPLv2 requires to keep such licensed components replaceable on the target.
> What then effectively remains with v3 is its, well, wording complexity.

Does "tar" match the requirements?

And I agree that best option would be to accept GPLv3.

If that's out of question, I'm pretty sure we can get GPLv2 tar
implementation somewhere. busybox has implementation, and I'm pretty
sure there's GPLv2 fork of busybox. Old version of tar should be
GPLv2. Still better than porting duplicity to different python
version...

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4555): https://lists.cip-project.org/g/cip-dev/message/4555
Mute This Topic: https://lists.cip-project.org/mt/72826088/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-04-06 22:02 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
2020-04-06 10:15   ` Jan Kiszka
2020-04-06 21:52     ` Pavel Machek [this message]
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=20200406215205.GA14162@amd.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=cip-security@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --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