1 Return-Path: <david@tethera.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 23551431FAF
\r
6 for <notmuch@notmuchmail.org>; Thu, 17 Apr 2014 15:52:16 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id lhugZWUjWG5R for <notmuch@notmuchmail.org>;
\r
16 Thu, 17 Apr 2014 15:52:08 -0700 (PDT)
\r
17 Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net
\r
18 [87.98.215.224]) (using TLSv1 with cipher AES256-SHA (256/256 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id CF688431FAE
\r
21 for <notmuch@notmuchmail.org>; Thu, 17 Apr 2014 15:52:07 -0700 (PDT)
\r
22 Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim
\r
23 4.72) (envelope-from <david@tethera.net>)
\r
24 id 1Wav8b-0002qy-Oe; Thu, 17 Apr 2014 22:50:33 +0000
\r
25 Received: (nullmailer pid 1818 invoked by uid 1000); Thu, 17 Apr 2014
\r
27 From: David Bremner <david@tethera.net>
\r
28 To: Allan Streib <astreib@indiana.edu>
\r
29 Subject: Re: notmuch, OpenBSD issues
\r
30 In-Reply-To: <871twvokwm.fsf@viking.indiana.edu>
\r
31 References: <871twvokwm.fsf@viking.indiana.edu>
\r
32 User-Agent: Notmuch/0.17+174~g4efbc9f (http://notmuchmail.org) Emacs/24.3.1
\r
33 (x86_64-pc-linux-gnu)
\r
34 Date: Fri, 18 Apr 2014 07:50:15 +0900
\r
35 Message-ID: <877g6ny3iw.fsf@maritornes.cs.unb.ca>
\r
37 Content-Type: text/plain
\r
38 Cc: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
\r
39 X-BeenThere: notmuch@notmuchmail.org
\r
40 X-Mailman-Version: 2.1.13
\r
42 List-Id: "Use and development of the notmuch mail system."
\r
43 <notmuch.notmuchmail.org>
\r
44 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
45 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
46 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
47 List-Post: <mailto:notmuch@notmuchmail.org>
\r
48 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
49 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
51 X-List-Received-Date: Thu, 17 Apr 2014 22:52:16 -0000
\r
53 Allan Streib <astreib@indiana.edu> writes:
\r
57 > I've been using notmuch on OpenBSD for a while, and I really appreciate
\r
60 I hope you don't mind my replying to the list. Notmuch is not a one man project...
\r
63 > In recent days I've had a couple problems building. First issue was a
\r
64 > complaint about "cannonicalize_file_name" being an unknown symbol. I
\r
65 > fixed that with the following:
\r
67 Yeah, that's actually a bug in my fix other fix for openbsd.
\r
68 There's actually a patch queued for merging on the mailing list, see
\r
70 id:1397042643-10975-1-git-send-email-david@tethera.net
\r
72 > The other issue is with the support for gzipped dump and restore;
\r
73 > OpenBSD currently provides zlib version 1.2.3 which apparently is too
\r
74 > old for what you are doing. For now I am just building from commit
\r
75 > 69867c33 which pre-dates the inclusion of the zlib version checks. Is
\r
76 > there a convenient way to make the gzipped dump and restore optional, so
\r
77 > that I can continue to keep up with other changes?
\r
79 > If not I can look into building a newer version of zlib for use with
\r
82 Unfortunately I can't think of a simple change to make gzipped dump and
\r
83 restore optional; somewhat ironically we actually need the later zlib
\r
84 for dumping uncompressed backups. This is clearly not a feature we want
\r
85 to take away. I guess it would be possible to write a compat shim on
\r
86 top of zlib that implemented the passthrough that we need. Tomi Ollila,
\r
87 who runs notmuch on various old systems, might a have a comment about
\r
88 that. Meanwhile, unlike libc, it should be possible to compile a newer
\r