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-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1U3xgy-0001Wz-T7
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Feb 2013 23:49:16 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.48 as permitted sender)
client-ip=74.125.82.48; envelope-from=gavinandresen@gmail.com;
helo=mail-wg0-f48.google.com;
Received: from mail-wg0-f48.google.com ([74.125.82.48])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1U3xgx-0005g0-TE
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Feb 2013 23:49:16 +0000
Received: by mail-wg0-f48.google.com with SMTP id 16so3361525wgi.27
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 Feb 2013 15:49:09 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.59.40 with SMTP id w8mr12680527wjq.51.1360367349635;
Fri, 08 Feb 2013 15:49:09 -0800 (PST)
Received: by 10.194.176.164 with HTTP; Fri, 8 Feb 2013 15:49:09 -0800 (PST)
Date: Fri, 8 Feb 2013 18:49:09 -0500
Message-ID: <CABsx9T1D08uOenXch7ZwrEaCeOdFCFOtzK8ochN8z3REGm0mLQ@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
X-Headers-End: 1U3xgx-0005g0-TE
Subject: [Bitcoin-development] 0.8.0rc1 status
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, 08 Feb 2013 23:49:17 -0000
Linux builds of 0.8.0rc1 are in good shape; easily gitian-reproduceable.
Windows builds are varying with every compile, and I think I finally
figured out why: we are not passing the -frandom-seed flag down into
the leveldb build (I used objdump to dump two different binaries, and
they differed only in the names of some leveldb objects). That should
be an easy makefile fix.
The OSX build is in pretty good shape, but needs
https://github.com/bitcoin/bitcoin/pull/2286 to compile.
So: I think the path forward is to announce 0.8.0rc1 with the binaries
we've got, to get more testing.
Then before final release (or rc2, if that is needed) pull #2286 and
create and pull a patch to fix the windows non-determinism problem.
I'm done for today, but should have time to sign the windows setup.exe
and send out a rc1 announcement tomorrow.
--
--
Gavin Andresen
|
