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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WgIC9-0004rE-1o
for bitcoin-development@lists.sourceforge.net;
Fri, 02 May 2014 18:28:25 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.177 as permitted sender)
client-ip=209.85.213.177; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f177.google.com;
Received: from mail-ig0-f177.google.com ([209.85.213.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WgIC8-0000lG-8l
for bitcoin-development@lists.sourceforge.net;
Fri, 02 May 2014 18:28:25 +0000
Received: by mail-ig0-f177.google.com with SMTP id h3so2241263igd.4
for <bitcoin-development@lists.sourceforge.net>;
Fri, 02 May 2014 11:28:18 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.155.209 with SMTP id lj17mr3377563icc.94.1399055298437;
Fri, 02 May 2014 11:28:18 -0700 (PDT)
Received: by 10.64.22.168 with HTTP; Fri, 2 May 2014 11:28:18 -0700 (PDT)
In-Reply-To: <5363D9FD.4070509@anonymousbitcoinbook.com>
References: <CA+s+GJARfPhMo8ucE7E40bE890NsuzuWPq1DQuK6ZVMvps0LVQ@mail.gmail.com>
<535BECDC.9070804@anonymousbitcoinbook.com>
<CA+s+GJC_1YzKNwQKSreWB73vZVMYmM=+CqonqP7XWcDFP7ZZLw@mail.gmail.com>
<5363D9FD.4070509@anonymousbitcoinbook.com>
Date: Fri, 2 May 2014 20:28:18 +0200
Message-ID: <CA+s+GJCOdoO0STE-pcGC+dSLxbSmw07T=Uuv50RBeHVP36uuwQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Kristov Atlas <author@anonymousbitcoinbook.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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-Headers-End: 1WgIC8-0000lG-8l
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Compatibility Bitcoin-Qt with Tails
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 02 May 2014 18:28:25 -0000
On Fri, May 2, 2014 at 7:46 PM, Kristov Atlas
<author@anonymousbitcoinbook.com> wrote:
> Nice work! I can confirm that this dev binary runs smoothly in the latest
Thanks for testing!
> version of Tails, v1.0. Screenshot proof here [1]. When this is incorporated
> into the next release of Bitcoin Core, will this make the usual Linux binary
> compatible, or will there be a special binary just for systems running the
> older Qt?
The normal binary will be compatible.
At some point we may add a binary that is linked to Qt 5.x as well for
newer distributions, but compatibility is most important.
Wladimir
|
