blob: f42b660ad4fbc95cf7aa1dca2541ccf7b90c03d1 (
plain)
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
|
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 <gavinandresen@gmail.com>) id 1RRnex-0005Uk-QY
for bitcoin-development@lists.sourceforge.net;
Sat, 19 Nov 2011 16:20:55 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.161.47 as permitted sender)
client-ip=209.85.161.47; envelope-from=gavinandresen@gmail.com;
helo=mail-fx0-f47.google.com;
Received: from mail-fx0-f47.google.com ([209.85.161.47])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RRnex-0002qo-1H
for bitcoin-development@lists.sourceforge.net;
Sat, 19 Nov 2011 16:20:55 +0000
Received: by faat2 with SMTP id t2so7377993faa.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 19 Nov 2011 08:20:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.152.109.33 with SMTP id hp1mr4814702lab.36.1321719648678; Sat,
19 Nov 2011 08:20:48 -0800 (PST)
Received: by 10.152.30.69 with HTTP; Sat, 19 Nov 2011 08:20:48 -0800 (PST)
Date: Sat, 19 Nov 2011 11:20:48 -0500
Message-ID: <CABsx9T2KkFC9_sibE4gYdd2JCTSSdbVQcOmK1nbKFYns820_7A@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
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
(gavinandresen[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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RRnex-0002qo-1H
Subject: [Bitcoin-development] Need help testing/debugging: Linux64
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: Sat, 19 Nov 2011 16:20:55 -0000
There is one issue holding up a 0.5.0/0.4.1 final release: I've seen
a couple of bug reports of crashes on startup when re-encrypting
previously encrypted wallets on Linux64 systems.
I've tried to reproduce on Ubuntu 10.10 server and "it worked for me"
-- so I need help figuring out what is going on (is it only bitcoin-qt
that is crashing? Is Ubuntu OK but other linux variations broken?
etc)
--
--
Gavin Andresen
|
