path: root/tickets/f0cbd17bf39c46b6b6ceb942e051f2c6/Maildir/new/1502657887.M310991P29646Q1.koom

Return-Path: <obnam-support-bounces@obnam.org>
X-Original-To: distix@pieni.net
Delivered-To: distix@pieni.net
Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221])
	by pieni.net (Postfix) with ESMTPS id 6E9FA4477D
	for <distix@pieni.net>; Sun, 13 Aug 2017 20:44:51 +0000 (UTC)
Received: from platypus.pepperfish.net (unknown [10.112.101.20])
	by yaffle.pepperfish.net (Postfix) with ESMTP id 233C541941;
	Sun, 13 Aug 2017 21:44:51 +0100 (BST)
Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
	by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
	id 1dgzkh-00005l-3s; Sun, 13 Aug 2017 21:44:51 +0100
Received: from [10.112.101.103] (helo=mx3.pepperfish.net)
 by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
 id 1dgzkg-00005U-AG
 for <obnam-support@obnam.org>; Sun, 13 Aug 2017 21:44:50 +0100
Received: from mail-qk0-f181.google.com ([209.85.220.181])
 by mx3.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
 (Exim 4.84_2) (envelope-from <sanskritfritz@gmail.com>)
 id 1dgzkc-0004oJ-HZ
 for obnam-support@obnam.org; Sun, 13 Aug 2017 21:44:49 +0100
Received: by mail-qk0-f181.google.com with SMTP id a77so42155783qkb.0
 for <obnam-support@obnam.org>; Sun, 13 Aug 2017 13:44:40 -0700 (PDT)
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;
 bh=KBuNeQODScuzYKIgrX4ZgU6RjZkurzXXqzh4p6fJsWY=;
 b=erkGds6b+KEwuin5qjTrs70ken6upQT3kVEthoyrBvsq9Q7AATdaRDzfAHavbkUfzT
 q7WqTA7BlN+Y+tr4TJJUSsbt5n6cl4ACE7Y8GLfydtQ+Bt3PlcR0bQRQH1NEZ8xk6EbM
 kf4cPwx+pa96T1Tjq86g2rm+8f+UYDeC58si2SASM6sJJTfqsye6RyqXyCDOXoVwXy4n
 LZWFUmt+1ZKuOJDJMi5MysfnZCEFZ93pbxxa/ABE7XBJvJlM5CLcyg7noDmZRJFx9LQ9
 s4oo3gqWwdmuC7FXcCYAx7MHWpFkqgkAps7T18a9WJVHustUBsAzV2yQqIlwT3nNUwOd
 Fqtw==
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;
 bh=KBuNeQODScuzYKIgrX4ZgU6RjZkurzXXqzh4p6fJsWY=;
 b=O/BTfcpFZxupKpo0DNEZ7tmEj1KyBd3FeNjcVUnqtaEBQp+lYErdve4M39MFzpceKq
 0hizXY0YbGh3OndSvAuTcNib1CfSJBJ8B2MeHoUH08ObtBx//ZgBtBCIPeHa6pU41wcq
 T+FkHzd5OSe8LUlPINes/J6Vt6VRTYI9/VoWW/0vBMD6/EBRwRPvHsYJrbB5eRsnbjYO
 Nd8CcwnKvDcXkC90W95SxoSCesrL37irQlfuMEElCff/71aieGjSdX7gEOz4pNKB1jF+
 ljUCxalZn5OSdmsCGOnom9vgiTsz3eWvY71gm7MMkz/yH+jIpcBegshfsSA0M27KfoWB
 kNiw==
X-Gm-Message-State: AHYfb5iJLbSimkvKLZ+aiKxxbglyh2fgZ6tAPpMBdXBlv0QLf834bCax
 0IKlTPEs+M7V1dxJ+ZQ/0ldGb379bA==
X-Received: by 10.55.43.160 with SMTP id r32mr27222682qkr.47.1502657073944;
 Sun, 13 Aug 2017 13:44:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.38.35 with HTTP; Sun, 13 Aug 2017 13:43:53 -0700 (PDT)
In-Reply-To: <20170813184758.hbel3jxgultskktu@liw.fi>
References: <20170813184758.hbel3jxgultskktu@liw.fi>
From: SanskritFritz <sanskritfritz@gmail.com>
Date: Sun, 13 Aug 2017 22:43:53 +0200
Message-ID: <CAExbbMyVUCe_UkeMKaf1KkCgLnWwYnF=dHswV5Er2YvAjYUwCw@mail.gmail.com>
To: Obnam support <obnam-support@obnam.org>
X-Pepperfish-Transaction: 11ba-5dda-84c2-53ff
X-Spam-Score: 4.0
X-Spam-Score-int: 40
X-Spam-Bar: ++++
X-Scanned-By: pepperfish.net, Sun, 13 Aug 2017 21:44:49 +0100
X-Spam-Report: Content analysis details: (4.0 points)
 pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -0.0 RCVD_IN_MSPIKE_H3      RBL: Good reputation (+3)
 [209.85.220.181 listed in wl.mailspike.net]
 1.0 PPF_FROM_CONTAINS_MAIL The From header contains 'mail'
 0.5 PPF_RECEIVED_HTTP      Received header mentions http
 0.2 PPF_ALTERNATIVES       Body in multipart/alternative
 -0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
 trust [209.85.220.181 listed in list.dnswl.org]
 1.5 RCVD_IN_SORBS_SPAM     RBL: SORBS: sender is a spam source
 [209.85.220.181 listed in dnsbl.sorbs.net]
 -0.0 SPF_PASS               SPF: sender matches SPF record
 1.2 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
 (sanskritfritz[at]gmail.com)
 0.3 HTML_MESSAGE           BODY: HTML included in message
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
 [score: 0.0000]
 1.0 PPF_BLANK              RAW: Body contains _blank
 0.2 PPF_NUMERIC_ENTITY     RAW: Body contains numeric HTML entities
 0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid
 -0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
X-ACL-Warn: message may be spam
X-Scan-Signature: f576f89d0cea0834df63e092bec7ab85
Subject: Re: [obnam-announce] Retiring Obnam
X-BeenThere: obnam-support@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Obnam backup software discussion <obnam-support-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
 <mailto:obnam-support-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org>
List-Post: <mailto:obnam-support@obnam.org>
List-Help: <mailto:obnam-support-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
 <mailto:obnam-support-request@obnam.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5859063545528327932=="
Mime-version: 1.0
Sender: obnam-support-bounces@obnam.org
Errors-To: obnam-support-bounces@obnam.org

--===============5859063545528327932==
Content-Type: multipart/alternative; boundary="001a11495ff61c9c1b0556a89d67"

--001a11495ff61c9c1b0556a89d67
Content-Type: text/plain; charset="UTF-8"

Hi.
This is very sad news for me. I rely on Obnam for my backup. Although I
already know which alternative I'll use (zbackup), I actually think Obnam
could live on in a form of a fork. I wonder if anyone is willing to
maintain a fork. I don't dare to stup up in such role, my coding knowledge
is not enough to do that. Will you pull the code from your site as well?
Because if you will, we would like to transfer the code base to github or
the like.
Having all said that, I also want to express my gratitude and THANK YOU for
Obnam!




On Sun, Aug 13, 2017 at 8:47 PM, Lars Wirzenius <liw@liw.fi> wrote:

> This is a difficult announcement to write. The summary is that you
> should switch to another backup program in the coming months.
>
> The first commit to Obnam's current code base is this:
>
>     commit 7eaf5a44534ffa7f9c0b9a4e9ee98d312f2fcb14
>     Author: Lars Wirzenius <liw@iki.fi>
>     Date:   Wed Sep 6 18:35:52 2006 +0300
>
>         Initial commit.
>
> It's followed by over 5200 more commits until the latest one, which is
> from yesterday. The NEWS file contains 58 releases. There are 20761
> lines of Python, 15384 words in the English language manual, with
> translations in German and French. The yarn test suite, which is a
> kind of a manual, is another 13382 words in English and
> pseudo-English. That's a fair bit of code and prose. Not all of it
> mine, I've had help from some wonderful people. But most of it mine.
>
> I wrote all of that because backups were fun. It was pleasing to use
> my own program to guarantee the safety of my own data. The technical
> challenges of implmenting the kind of backup program I wanted were
> interesting, and solving interesting problems is a big part of why
> I am a programmer.
>
> Obnam has a kind user base. It's not a large user base: the Debian
> "popularity contest" service estimates it at around 500. But it's a
> user base that is kind and has treated me well. I have tried to
> reciprocate.
>
> Unfortunately, I have not had fun while developing Obnam for some time
> now. This has changed. A few years ago, I lived in Manchester, UK, and
> commuted by train to work. It was a short train ride, about 15
> minutes. At times I would sit on the floor with my laptop on my knees,
> writing code or the manual. Back then Obnam was a lot of fun. I was
> excited, and enthusiastic.
>
> In the past two years or so, I've not been able to feel that
> excitement again. My native language, Finnish, has an expression
> describing unpleasant tasks: something is as much fun as drinking tar.
> That describes Obnam in recent years for me.
>
> Obnam has not turned out well, from a maintainability point of view.
> It seems that every time I try to fix something, I break something
> else. Usuaully what breaks is speed or memory use: Obnam gets slower
> or starts using even more memory.
>
> For several years now I've been working on a new repository format for
> Obnam, code names GREEN ALBATROSS. It was meant to solve Obnam's
> problems as far as extensibility, performance, and resource use were
> concerned. It seems to have failed.
>
> I'm afraid I've had enough. I'm going to retire Obnam as a project and
> as a program, and move on to doing something else, so I can feel
> excitement and pleasure again.
>
> After some careful thought, I fear that the maintainability problems
> of Obnam can realistically only be solved by a complete rewrite from
> scratch, and I'm not up to doing that.
>
> If you use Obnam, you should migrate to some other backup solution.
> Don't worry, you have until the end of the year. I will be around and
> I intend to fix any serious bugs in Obnam; in particular, security
> flaws. But you should start looking for a replacement sooner rather
> than later.
>
> I will be asking Obnam to be removed from the Debian unstable and
> testing branches. The next Debian release (buster, Debian 10) won't
> include Obnam.
>
> The Obnam mailing lists are kindly hosted by Daniel Silverstone, and
> they will remain, but later this year I will change them to be
> moderated. The Obnam git repository will remain. The web site will
> remain, but I will add a note that Obnam is no longer maintained.
> Other Obnam online resources may disappear.
>
> If you would like to take over the Obnam project, and try to resolve
> the various issues, please contact me to discuss that.
>
> Thank you, and may you never need to restore.
>
> _______________________________________________
> obnam-announce mailing list
> obnam-announce@obnam.org
> http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/
> obnam-announce-obnam.org
>
>

--001a11495ff61c9c1b0556a89d67
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi.<br></div>This is very sad news for me. =
I rely on Obnam for my backup. Although I already know which alternative I&=
#39;ll use (zbackup), I actually think Obnam could live on in a form of a f=
ork. I wonder if anyone is willing to maintain a fork. I don&#39;t dare to =
stup up in such role, my coding knowledge is not enough to do that. Will yo=
u pull the code from your site as well? Because if you will, we would like =
to transfer the code base to github or the like.<br></div></div>Having all =
said that, I also want to express my gratitude and THANK YOU for Obnam!<br>=
<div><br><div><br><div><br></div></div></div></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Sun, Aug 13, 2017 at 8:47 PM, Lars Wir=
zenius <span dir=3D"ltr">&lt;<a href=3D"mailto:liw@liw.fi" target=3D"_blank=
">liw@liw.fi</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This i=
s a difficult announcement to write. The summary is that you<br>
should switch to another backup program in the coming months.<br>
<br>
The first commit to Obnam&#39;s current code base is this:<br>
<br>
=C2=A0 =C2=A0 commit 7eaf5a44534ffa7f9c0b9a4e9ee98d<wbr>312f2fcb14<br>
=C2=A0 =C2=A0 Author: Lars Wirzenius &lt;<a href=3D"mailto:liw@iki.fi">liw@=
iki.fi</a>&gt;<br>
=C2=A0 =C2=A0 Date:=C2=A0 =C2=A0Wed Sep 6 18:35:52 2006 +0300<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Initial commit.<br>
<br>
It&#39;s followed by over 5200 more commits until the latest one, which is<=
br>
from yesterday. The NEWS file contains 58 releases. There are 20761<br>
lines of Python, 15384 words in the English language manual, with<br>
translations in German and French. The yarn test suite, which is a<br>
kind of a manual, is another 13382 words in English and<br>
pseudo-English. That&#39;s a fair bit of code and prose. Not all of it<br>
mine, I&#39;ve had help from some wonderful people. But most of it mine.<br=
>
<br>
I wrote all of that because backups were fun. It was pleasing to use<br>
my own program to guarantee the safety of my own data. The technical<br>
challenges of implmenting the kind of backup program I wanted were<br>
interesting, and solving interesting problems is a big part of why<br>
I am a programmer.<br>
<br>
Obnam has a kind user base. It&#39;s not a large user base: the Debian<br>
&quot;popularity contest&quot; service estimates it at around 500. But it&#=
39;s a<br>
user base that is kind and has treated me well. I have tried to<br>
reciprocate.<br>
<br>
Unfortunately, I have not had fun while developing Obnam for some time<br>
now. This has changed. A few years ago, I lived in Manchester, UK, and<br>
commuted by train to work. It was a short train ride, about 15<br>
minutes. At times I would sit on the floor with my laptop on my knees,<br>
writing code or the manual. Back then Obnam was a lot of fun. I was<br>
excited, and enthusiastic.<br>
<br>
In the past two years or so, I&#39;ve not been able to feel that<br>
excitement again. My native language, Finnish, has an expression<br>
describing unpleasant tasks: something is as much fun as drinking tar.<br>
That describes Obnam in recent years for me.<br>
<br>
Obnam has not turned out well, from a maintainability point of view.<br>
It seems that every time I try to fix something, I break something<br>
else. Usuaully what breaks is speed or memory use: Obnam gets slower<br>
or starts using even more memory.<br>
<br>
For several years now I&#39;ve been working on a new repository format for<=
br>
Obnam, code names GREEN ALBATROSS. It was meant to solve Obnam&#39;s<br>
problems as far as extensibility, performance, and resource use were<br>
concerned. It seems to have failed.<br>
<br>
I&#39;m afraid I&#39;ve had enough. I&#39;m going to retire Obnam as a proj=
ect and<br>
as a program, and move on to doing something else, so I can feel<br>
excitement and pleasure again.<br>
<br>
After some careful thought, I fear that the maintainability problems<br>
of Obnam can realistically only be solved by a complete rewrite from<br>
scratch, and I&#39;m not up to doing that.<br>
<br>
If you use Obnam, you should migrate to some other backup solution.<br>
Don&#39;t worry, you have until the end of the year. I will be around and<b=
r>
I intend to fix any serious bugs in Obnam; in particular, security<br>
flaws. But you should start looking for a replacement sooner rather<br>
than later.<br>
<br>
I will be asking Obnam to be removed from the Debian unstable and<br>
testing branches. The next Debian release (buster, Debian 10) won&#39;t<br>
include Obnam.<br>
<br>
The Obnam mailing lists are kindly hosted by Daniel Silverstone, and<br>
they will remain, but later this year I will change them to be<br>
moderated. The Obnam git repository will remain. The web site will<br>
remain, but I will add a note that Obnam is no longer maintained.<br>
Other Obnam online resources may disappear.<br>
<br>
If you would like to take over the Obnam project, and try to resolve<br>
the various issues, please contact me to discuss that.<br>
<br>
Thank you, and may you never need to restore.<br>
<br>______________________________<wbr>_________________<br>
obnam-announce mailing list<br>
<a href=3D"mailto:obnam-announce@obnam.org">obnam-announce@obnam.org</a><br=
>
<a href=3D"http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-=
announce-obnam.org" rel=3D"noreferrer" target=3D"_blank">http://listmaster.=
pepperfish.<wbr>net/cgi-bin/mailman/listinfo/<wbr>obnam-announce-obnam.org<=
/a><br>
<br></blockquote></div><br></div>

--001a11495ff61c9c1b0556a89d67--


--===============5859063545528327932==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
obnam-support mailing list
obnam-support@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org

--===============5859063545528327932==--