diff options
author | Distix listener <distix@pieni.net> | 2017-02-08 14:05:10 +0100 |
---|---|---|
committer | Distix listener <distix@pieni.net> | 2017-02-08 14:05:10 +0100 |
commit | 10731cac1bc6f0ab668f1a1022e115f6614f5774 (patch) | |
tree | 1d38ddd89bbdad576fa615062f480f48a8655c22 /tickets | |
parent | 2fa3dd1076dd0f384639fb9d28d53cb5fbb27e96 (diff) | |
download | obnam-dev-distix-10731cac1bc6f0ab668f1a1022e115f6614f5774.tar.gz |
imported mails
Diffstat (limited to 'tickets')
-rw-r--r-- | tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486559109.M39108P25780Q1.hrun | 187 |
1 files changed, 187 insertions, 0 deletions
diff --git a/tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486559109.M39108P25780Q1.hrun b/tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486559109.M39108P25780Q1.hrun new file mode 100644 index 0000000..b9c41f1 --- /dev/null +++ b/tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486559109.M39108P25780Q1.hrun @@ -0,0 +1,187 @@ +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 275E52730D + for <distix@pieni.net>; Wed, 8 Feb 2017 14:03:27 +0100 (CET) +Received: from platypus.pepperfish.net (unknown [10.112.100.20]) + by bagpuss.pepperfish.net (Postfix) with ESMTP id 65C7ACE3; + Wed, 8 Feb 2017 13:03:26 +0000 (GMT) +Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net) + by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) + id 1cbRuA-00020c-8M; Wed, 08 Feb 2017 13:03:26 +0000 +Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net) + by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) + id 1cbRu8-00020P-Bs + for <obnam-dev@obnam.org>; Wed, 08 Feb 2017 13:03:24 +0000 +Received: from mail-qt0-f177.google.com ([209.85.216.177]) + by mx0.pepperfish.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) + (Exim 4.80) (envelope-from <sanskritfritz@gmail.com>) + id 1cbRu6-0001br-Ht + for obnam-dev@obnam.org; Wed, 08 Feb 2017 13:03:24 +0000 +Received: by mail-qt0-f177.google.com with SMTP id v23so164321204qtb.0 + for <obnam-dev@obnam.org>; Wed, 08 Feb 2017 05:03:17 -0800 (PST) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; + h=mime-version:in-reply-to:references:from:date:message-id:subject:to + :cc; bh=jBdcbNOUvLr9lWt1ySmatCT++WZPVxaCIy82x4L7Ifg=; + b=eJt+SW/CbmJrVLUV3k/n1tZ9vHEpQBIGTGh5FdCeEiI8OA1dvpeIfuSQ9lFuLJT0cb + RbZNH7alGKsqbz1TW9BHp1vTKerZZNcu+lFEeyxmE6S1KjCS51E8G60DIOzqlsWc9UKF + lVmFRv+C2zlzsNjDhz8cr6XGBww/lOxQRaJ0LyaN/bRegr8kNyV8SRGR4pU3Q1hNYerN + iVaZ2CHSxRMLjLa9aCBxeSJphCs7cGhBfs8fgb0W+TAMCx2fVbzIkZCWAngO9bhA97WZ + kmTFn94G9KwzT5sjVLhbfMK57wQ6GwWWaSpxETFCoWpJsiBeLWWByl07vcDZeiBWVjoS + IG8Q== +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20161025; + h=x-gm-message-state:mime-version:in-reply-to:references:from:date + :message-id:subject:to:cc; + bh=jBdcbNOUvLr9lWt1ySmatCT++WZPVxaCIy82x4L7Ifg=; + b=NPQ0wGOoLO5g7uXOhMpJfRTiGGQopqDnvTIJ7/tBJQbP2t2T0galeJsvJp3b0gva2G + bo9sABtkDpZdnJtB1YrF+N6s51XXialPnqHKzz06zR58EoN92/Pr086Ud6IHN5qFSctU + lHbV5qEf3I/huD6dXJIyBU0K0MTTXzjvunAG3ym5cj6JPWmoguk5AQDe9dkfsF4OJtXZ + pdQPtiGmCphudFL8Eze2mPxUVQziRZiSfbb3UePJtShoOnYLidAatEaIKI+OcLCZRmuL + pvO60Uc2gFL5oRhPLHx9JNsmXwbAe+ue15v+hOQh/A9q1MV8PMegxZAasEXwHC93LlbQ + uI+g== +X-Gm-Message-State: AMke39loPhN6+rEdH5QPZDL8dfgdtsIFUgnChEHc0tZilN3zbfdBk8n8VFDzr2emtjO5UZ+7z43/8V/VaGbH6A== +X-Received: by 10.237.37.90 with SMTP id w26mr19350172qtc.112.1486558990814; + Wed, 08 Feb 2017 05:03:10 -0800 (PST) +MIME-Version: 1.0 +Received: by 10.237.58.231 with HTTP; Wed, 8 Feb 2017 05:02:30 -0800 (PST) +In-Reply-To: <20170208125824.z6h4k3kybfm3npfd@exolobe3> +References: <20170121144532.lxn3alp4he4nvrwy@exolobe3> + <87shnoapcg.fsf@euler.schwinge.homeip.net> + <20170208125824.z6h4k3kybfm3npfd@exolobe3> +From: SanskritFritz <sanskritfritz@gmail.com> +Date: Wed, 8 Feb 2017 14:02:30 +0100 +Message-ID: <CAExbbMzf0ZeaQEUdC-aZD2NFUNv0utrOd2RmBkJL_TXTzTrtSw@mail.gmail.com> +To: Lars Wirzenius <liw@liw.fi> +X-Pepperfish-Transaction: 9c40-415f-e57b-4d78 +X-Spam-Score: 4.3 +X-Spam-Score-int: 43 +X-Spam-Bar: ++++ +X-Scanned-By: pepperfish.net, Wed, 08 Feb 2017 13:03:24 +0000 +X-Spam-Report: Content analysis details: (4.3 points) + pts rule name description + ---- ---------------------- -------------------------------------------------- + -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no + trust [209.85.216.177 listed in list.dnswl.org] + 0.2 PPF_ALTERNATIVES Body in multipart/alternative + 0.5 PPF_RECEIVED_HTTP Received header mentions http + 0.2 PPF_INREPLYTO_NODOTS In-Reply-To contains no dots after the @ + 0.2 PPF_REFERENCES_NODOTS References contains no dots after the @ + 1.0 PPF_FROM_CONTAINS_MAIL The From header contains 'mail' + 1.2 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (sanskritfritz[at]gmail.com) + 1.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source + [209.85.216.177 listed in dnsbl.sorbs.net] + -0.0 SPF_PASS SPF: sender matches SPF record + -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% + [score: 0.0000] + 0.3 HTML_MESSAGE BODY: HTML included in message + 0.2 PPF_NUMERIC_ENTITY RAW: Body contains numeric HTML entities + 1.0 PPF_BLANK RAW: Body contains _blank + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's + domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature +X-ACL-Warn: message may be spam +X-Scan-Signature: 9ec9504f9e4e0e45d288644cbc35aab1 +Cc: Obnam development <obnam-dev@obnam.org> +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> +Content-Type: multipart/mixed; boundary="===============0154928674000949269==" +Mime-version: 1.0 +Sender: obnam-dev-bounces@obnam.org +Errors-To: obnam-dev-bounces@obnam.org + +--===============0154928674000949269== +Content-Type: multipart/alternative; boundary=001a113f2fc895e2520548047c55 + +--001a113f2fc895e2520548047c55 +Content-Type: text/plain; charset=UTF-8 + +On Wed, Feb 8, 2017 at 1:58 PM, Lars Wirzenius <liw@liw.fi> wrote: + +> On Wed, Feb 08, 2017 at 12:34:07PM +0100, Thomas Schwinge wrote: +> > 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. +> +> I fear it'd make things so slow nobody would actually use this, even +> for testing. It'd mean obnam was making two backups at the same time. +> + +You could start two obnam instances parallelly :D + +--001a113f2fc895e2520548047c55 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">= +On Wed, Feb 8, 2017 at 1:58 PM, Lars Wirzenius <span dir=3D"ltr"><<a hre= +f=3D"mailto:liw@liw.fi" target=3D"_blank">liw@liw.fi</a>></span> wrote:<= +br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left= +:1px #ccc solid;padding-left:1ex"><span class=3D"">On Wed, Feb 08, 2017 at = +12:34:07PM +0100, Thomas Schwinge wrote:<br> +> One idea I just had -- but I don't know if that is feasible to imp= +lement:<br> +> you could (internally!) have obnam "write" both the "cu= +rrent" and the<br> +> "Green Albatross" formats, and then every "read" o= +peration would read<br> +> both of them, and compare that they return the same data.=C2=A0 Then h= +ave<br> +> obnam complain if that doesn't match (with the "current"= + format's data<br> +> then taking precedence, I think).=C2=A0 Obviously, that will add a lot= + of<br> +> overhead for every repository access, but any users willing to take th= +at<br> +> can then easily help testing the "Green Albatross" format.= +=C2=A0 But I don't<br> +> know if the repository abstraction in obnam is sufficiently generic fo= +r<br> +> being able to deal with two underlying repository formats, etc.<br> +<br> +</span>I fear it'd make things so slow nobody would actually use this, = +even<br> +for testing. It'd mean obnam was making two backups at the same time.<b= +r></blockquote></div><br></div><div class=3D"gmail_extra">You could start t= +wo obnam instances parallelly :D<br><br></div><div class=3D"gmail_extra"><b= +r></div></div> + +--001a113f2fc895e2520548047c55-- + + +--===============0154928674000949269== +Content-Type: text/plain; charset="us-ascii" +MIME-Version: 1.0 +Content-Transfer-Encoding: 7bit +Content-Disposition: inline + +_______________________________________________ +obnam-dev mailing list +obnam-dev@obnam.org +http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org + +--===============0154928674000949269==-- + |