summaryrefslogtreecommitdiff
path: root/6e/37206c85338b0598d820894bd38ca32e4ecb5a
blob: 7a123ef8b9e9751251717e268c0112358c342233 (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
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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1Qf7Ya-0002I5-Po
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Jul 2011 09:41:08 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.175 as permitted sender)
	client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-vx0-f175.google.com; 
Received: from mail-vx0-f175.google.com ([209.85.220.175])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Qf7YZ-0003TS-Po
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Jul 2011 09:41:08 +0000
Received: by vxa37 with SMTP id 37so1896523vxa.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 08 Jul 2011 02:41:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.110.105 with SMTP id hz9mr2499230vdb.189.1310118062278;
	Fri, 08 Jul 2011 02:41:02 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.164.225 with HTTP; Fri, 8 Jul 2011 02:41:02 -0700 (PDT)
In-Reply-To: <CA+8xBpcm2n4M=1KfqhaXPb-TQEeV5nk8sNkA8NZph3HcgPHKNA@mail.gmail.com>
References: <CA+8xBpeJcz-RJ9EtDKB-svu=chBQUNzsBPRi8ts+8-0bGHnFNw@mail.gmail.com>
	<CA+8xBpcm2n4M=1KfqhaXPb-TQEeV5nk8sNkA8NZph3HcgPHKNA@mail.gmail.com>
Date: Fri, 8 Jul 2011 11:41:02 +0200
X-Google-Sender-Auth: fFo8t3plUyrV2pbLxpNZ5mVW510
Message-ID: <CANEZrP1CN5g-n16TfQoyuaX+1MGUnpm5fBKLwFiaeUWKGn0uaQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.5 (-)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	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: 1Qf7YZ-0003TS-Po
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin v0.3.24 release candidate
	available
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 Jul 2011 09:41:08 -0000

A quick release would be good. The network is getting really sick:

   http://forum.bitcoin.org/index.php?topic=3D26894.40

I brought up the latest rc3 on plan99.net.

Though it's not relevant for this release, there seems to be some kind
of shutdown issue. I did a "bitcoin stop" and then waited for the log
to indicate successful shutdown. But the parent process didn't quit,
leaving a zombie. I did a kill -9 on the parent to get rid of it, and
then the addr.dat file became corrupted. I had to remove it and the
"database" directory as running the db_recover command didn't work.

On Wed, Jul 6, 2011 at 10:05 PM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> Bitcoin 0.3.24rc3 has been uploaded.
>
> Fixes appeared after -rc2 was tagged, so we just skipped straight to -rc3=
.
>
> Maybe final release on Friday?
>
> Changes since 0.3.24rc1:
>
> Gavin Andresen (2):
> =C2=A0 =C2=A0 =C2=A0Block-chain lock-in at 134444
> =C2=A0 =C2=A0 =C2=A0Do not use comma as thousands separator =C2=A0 =C2=A0=
 Using the comma as thousands s
>
> Matt Corallo (3):
> =C2=A0 =C2=A0 =C2=A0Added a couple minor things to match newer build proc=
ess.
> =C2=A0 =C2=A0 =C2=A0Revert "Make UPnP default on Bitcoin but not on Bitco=
ind."
> =C2=A0 =C2=A0 =C2=A0Enable UPnP by default on bitcoin, but not on bitcoin=
d (on gitian)
>
> Pieter Wuille (1):
> =C2=A0 =C2=A0 =C2=A0Fix synchronization of default key
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> dec9ff63fe6d0cffb2abc723281a4135c22f19ef =C2=A0bitcoin-0.3.24rc3-linux.ta=
r.gz
> c171c6e5128d570d5d7d5a6896b672fcab778933 =C2=A0bitcoin-0.3.24rc3-src.tar.=
gz
> d4b5425eff673551a326d5326b92a06359dc1a3d =C2=A0bitcoin-0.3.24rc3-win32-se=
tup.exe
> 0653302ac7f8b052d58667ae30da53c4f6230be5 =C2=A0bitcoin-0.3.24rc3-win32.zi=
p
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQIVAwUBThS+Xdodwg8tvwyoAQINthAAqxOnungGYS1o7IB3D3M1NRPD/O/WNoB4
> ANIn+oZLYy5+0yZylckT/gbkPY3PkhsIE8hVqbxGDYaDzUpjwN+DLd+EMPg5/2vr
> Tp2b77Lzh6QszZzZhrs9LPLsB8Q/jzCAbbChAekkAAe4sGm0MFkxMEYaXE+RF/uj
> PX36hdtmWYMzeXwf3PtbI8rAE9ESwXVVF8B7/qFvDhy4lrbXaNnGb3hGyowrNVBM
> m1s4jyk/Lq5pPcoKlRN6kiujCbZBIy6VKgc74YaoMOrznHryoeYQVCg4tySfKkuG
> gfiZFEL6EwYeY8ipjcRBVLFGxbwzCbIhBcBO/Je2yC+EwAOplfyy+GBE3rXLuUkn
> AzMiL1i5nX6dNmkYqVE0+pbv81FeT+uc1i63CIjquLdVbxh3omdpYdYHs9q/zN/9
> geHU4WnpwwZhTFEclzZUOGo8IJ0wiNsTyQv9mwVEjoslnubXh4omqbW7Tpm7cXiP
> jlDZ42Ay+Z+AvafdLYP27vfjWJoMbjcu6qU2EXBOhmpkeaIcV43oEAd7suy0OLUq
> 8iNMpQHjlLnH0pcN8r38Tq+vuCuhPZtiPZd5dVKSF3PaCB6vAv8MulE0yhP2LEq3
> Q4MzxSlgGNEWCGIv19YfMnURxGMNMKB0cyQ8SMdLDR+IIB3NB5SreeG8c8P97s5p
> VnHOvTnpHyw=3D
> =3DvKTJ
> -----END PGP SIGNATURE-----
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>
> -------------------------------------------------------------------------=
-----
> All of the data generated in your IT infrastructure is seriously valuable=
.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>