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
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <kristovatlas@gmail.com>) id 1Wd49n-00056l-TG
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:52:39 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.171 as permitted sender)
client-ip=209.85.216.171; envelope-from=kristovatlas@gmail.com;
helo=mail-qc0-f171.google.com;
Received: from mail-qc0-f171.google.com ([209.85.216.171])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wd49m-0005d8-TR
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:52:39 +0000
Received: by mail-qc0-f171.google.com with SMTP id c9so1563070qcz.16
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Apr 2014 13:52:33 -0700 (PDT)
X-Received: by 10.229.96.199 with SMTP id i7mr24511193qcn.20.1398286353453;
Wed, 23 Apr 2014 13:52:33 -0700 (PDT)
Received: from [10.0.2.15] (c-50-191-76-100.hsd1.pa.comcast.net.
[50.191.76.100])
by mx.google.com with ESMTPSA id w14sm3731033qaw.11.2014.04.23.13.52.31
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 23 Apr 2014 13:52:32 -0700 (PDT)
Message-ID: <5358280F.2050108@gmail.com>
Date: Wed, 23 Apr 2014 16:52:31 -0400
From: Kristov Atlas <kristovatlas@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Warren Togami Jr." <wtogami@gmail.com>,
Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
References: <CAEz79PrAg=yydd3UOk51wGQUWey-KZHUH1Npzwb=qL+6zTj+pQ@mail.gmail.com> <53581D1D.1000709@gmail.com>
<CAEz79Poy0XEVyC=nOdhYNVOASvfB-2zHJcjU2hvjA7iDWGDDyw@mail.gmail.com>
In-Reply-To: <CAEz79Poy0XEVyC=nOdhYNVOASvfB-2zHJcjU2hvjA7iDWGDDyw@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------050406050105030801020907"
X-Spam-Score: -0.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
(kristovatlas[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Wd49m-0005d8-TR
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
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: Wed, 23 Apr 2014 20:52:40 -0000
This is a multi-part message in MIME format.
--------------050406050105030801020907
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
On 04/23/2014 04:39 PM, Warren Togami Jr. wrote:
> On Wed, Apr 23, 2014 at 10:05 AM, Kristov Atlas
> <kristovatlas@gmail.com <mailto:kristovatlas@gmail.com>> wrote:
>
> I see that the latest nightly build (thanks for that, Warren) is
> still not compatible with Tails/Debian Squeeze. Is there still an
> intention to address this issue? Might it be fixed by 0.9.2?
>
>
> If I understand the situation, bitcoind does work but not bitcoin-qt
> due to qt-4.6? If that is so, then the official Bitcoin 0.8.6
> binaries didn't work on Squeeze either this is not a regression.
>
> The priority is for bitcoind to work on as many distributions as
> reasonably possible as older stable distributions are most often
> headless. If you are a rare user who needs Bitcoin-Qt on an
> incompatible system you can at least build it from source.
>
> Warren
Bitcoin-Qt 0.8.6 worked fine on Tails (and Debian Squeeze, I assume).
So, it is a regression.
Here's output from the latest nightly build for Linux:
amnesia@amnesia:~/bitcoin-0.9.99.0-20140422-2bbecc8-linux/bin/32$ ./bitcoin-qt
./bitcoin-qt: symbol lookup error: ./bitcoin-qt: undefined symbol: _ZN19QAbstractProxyModel11setItemDataERK11QModelIndexRK4QMapIi8QVariantE
Since Tails has many simple development tools like "make" stripped out
for security reasons, one could not simply build from source in Tails.
It might be possible to build in Debian Squeeze and transplant that,
however. I'll have to give that a shot some time. I'd argue that Tails
is an incredibly important -- and hardly obscure -- Linux distribution
that Bitcoin should endeavour to support. See:
https://tails.boum.org/press/index.en.html
-Kristov
--------------050406050105030801020907
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 04/23/2014 04:39 PM, Warren Togami Jr. wrote:<br>
<blockquote
cite="mid:CAEz79Poy0XEVyC=nOdhYNVOASvfB-2zHJcjU2hvjA7iDWGDDyw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Apr 23, 2014 at 10:05 AM,
Kristov Atlas <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kristovatlas@gmail.com" target="_blank">kristovatlas@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div class="">I see that the latest nightly build
(thanks for that, Warren) is still not compatible with
Tails/Debian Squeeze. Is there still an intention to
address this issue? Might it be fixed by 0.9.2?<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">If I understand the situation, bitcoind
does work but not bitcoin-qt due to qt-4.6? If that is so,
then the official Bitcoin 0.8.6 binaries didn't work on
Squeeze either this is not a regression.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">The priority is for bitcoind to work on
as many distributions as reasonably possible as older stable
distributions are most often headless. If you are a rare user
who needs Bitcoin-Qt on an incompatible system you can at
least build it from source.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Warren</div>
</div>
</blockquote>
<br>
Bitcoin-Qt 0.8.6 worked fine on Tails (and Debian Squeeze, I
assume). So, it is a regression.<br>
<br>
Here's output from the latest nightly build for Linux:<br>
<pre><a class="moz-txt-link-abbreviated" href="mailto:amnesia@amnesia:~/bitcoin-0.9.99.0-20140422-2bbecc8-linux/bin/32$">amnesia@amnesia:~/bitcoin-0.9.99.0-20140422-2bbecc8-linux/bin/32$</a> ./bitcoin-qt
./bitcoin-qt: symbol lookup error: ./bitcoin-qt: undefined symbol: _ZN19QAbstractProxyModel11setItemDataERK11QModelIndexRK4QMapIi8QVariantE</pre>
Since Tails has many simple development tools like "make" stripped
out for security reasons, one could not simply build from source in
Tails. It might be possible to build in Debian Squeeze and
transplant that, however. I'll have to give that a shot some time.
I'd argue that Tails is an incredibly important -- and hardly
obscure -- Linux distribution that Bitcoin should endeavour to
support. See: <a class="moz-txt-link-freetext" href="https://tails.boum.org/press/index.en.html">https://tails.boum.org/press/index.en.html</a><br>
<br>
-Kristov<br>
</body>
</html>
--------------050406050105030801020907--
|
