1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
|
Return-Path: <obnam-dev-bounces@obnam.org>
X-Original-To: distix@pieni.net
Delivered-To: distix@pieni.net
Received: from bagpuss.pepperfish.net (bagpuss.pepperfish.net [148.251.8.16])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pieni.net (Postfix) with ESMTPS id A622227343
for <distix@pieni.net>; Wed, 8 Feb 2017 13:02:33 +0100 (CET)
Received: from platypus.pepperfish.net (unknown [10.112.100.20])
by bagpuss.pepperfish.net (Postfix) with ESMTP id 50EF8ECB;
Wed, 8 Feb 2017 12:02:32 +0000 (GMT)
Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1cbQxE-0007pe-6g; Wed, 08 Feb 2017 12:02:32 +0000
Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1cbQxC-0007pE-LR
for <obnam-dev@obnam.org>; Wed, 08 Feb 2017 12:02:30 +0000
Received: from smtprelay03.ispgateway.de ([80.67.29.28])
by mx0.pepperfish.net with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
(Exim 4.80) (envelope-from <thomas@schwinge.name>)
id 1cbQxA-00083w-8M
for obnam-dev@obnam.org; Wed, 08 Feb 2017 12:02:30 +0000
Received: from [217.247.204.188] (helo=euler.schwinge.homeip.net)
by smtprelay03.ispgateway.de with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256)
(Exim 4.84) (envelope-from <thomas@schwinge.name>)
id 1cbQwu-00034v-Ni
for obnam-dev@obnam.org; Wed, 08 Feb 2017 13:02:12 +0100
Received: (nullmailer pid 26439 invoked by uid 1000);
Wed, 08 Feb 2017 12:02:20 -0000
From: Thomas Schwinge <thomas@codesourcery.com>
To: Lars Wirzenius <liw@liw.fi>, Obnam development <obnam-dev@obnam.org>
In-Reply-To: <20170121144532.lxn3alp4he4nvrwy@exolobe3>
References: <20170121144532.lxn3alp4he4nvrwy@exolobe3>
User-Agent: Notmuch/0.9-125-g4686d11 (http://notmuchmail.org) Emacs/24.5.1
(x86_64-pc-linux-gnu)
Date: Wed, 08 Feb 2017 12:34:07 +0100
Message-ID: <87shnoapcg.fsf@euler.schwinge.homeip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Df-Sender: b3V0Z29pbmdAc2Nod2luZ2UubmFtZQ==
X-Pepperfish-Transaction: 46f5-362a-3973-6c02
X-Spam-Score: -2.7
X-Spam-Score-int: -26
X-Spam-Bar: --
X-Scanned-By: pepperfish.net, Wed, 08 Feb 2017 12:02:30 +0000
X-Spam-Report: Content analysis details: (-2.7 points)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.5 PPF_USER_AGENT User-Agent: exists
0.2 PPF_INREPLYTO_NODOTS In-Reply-To contains no dots after the @
0.2 PPF_REFERENCES_NODOTS References contains no dots after the @
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust [80.67.29.28 listed in list.dnswl.org]
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
X-ACL-Warn: message may be spam
X-Scan-Signature: dec02e0749d215982dbb7ebe51425d50
Subject: Re: Obnam FORMAT GREEN ALBATROSS status and roadmap
X-BeenThere: obnam-dev@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Obnam development discussions <obnam-dev-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-dev-obnam.org>
List-Post: <mailto:obnam-dev@obnam.org>
List-Help: <mailto:obnam-dev-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=subscribe>
Sender: obnam-dev-bounces@obnam.org
Errors-To: obnam-dev-bounces@obnam.org
Hi Lars!
On Sat, 21 Jan 2017 16:45:32 +0200, Lars Wirzenius <liw@liw.fi> wrote:
> I intend to get the new Obnam repository format, GREEN ALBATORSS,
> finished this year.
:-)
One idea I just had -- but I don't know if that is feasible to implement:
you could (internally!) have obnam "write" both the "current" and the
"Green Albatross" formats, and then every "read" operation would read
both of them, and compare that they return the same data. Then have
obnam complain if that doesn't match (with the "current" format's data
then taking precedence, I think). Obviously, that will add a lot of
overhead for every repository access, but any users willing to take that
can then easily help testing the "Green Albatross" format. But I don't
know if the repository abstraction in obnam is sufficiently generic for
being able to deal with two underlying repository formats, etc.
Gr=C3=BC=C3=9Fe
Thomas
_______________________________________________
obnam-dev mailing list
obnam-dev@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org
|
