May15: Mention backport option

This commit is contained in:
Luke Dashjr 2013-05-09 02:43:09 +00:00
parent df897ceefe
commit 8944bb8042

View file

@ -7,7 +7,9 @@ layout: base-en
<h2>What is happening</h2> <h2>What is happening</h2>
<p> <p>
If you are using an old version of Bitcoin-Qt (or bitcoind, the server bitcoin software), If you are using an old version of Bitcoin-Qt (or bitcoind, the server bitcoin software),
you must either upgrade to version 0.8.0 or later before May 15, 2013 or <a href="#workaround">modify a file</a> and you must either upgrade to version 0.8.0 or later before May 15, 2013,
<a href="#backports">upgrade to an up-to-date "backport" release</a>,
or <a href="#workaround">modify a file</a> and
restart bitcoin to work around a bug with the old software. restart bitcoin to work around a bug with the old software.
</p> </p>
<p>This bug does not affect any bitcoins you already have, but if you do nothing you will <p>This bug does not affect any bitcoins you already have, but if you do nothing you will
@ -22,9 +24,15 @@ We recommend that you
before the 15th of May to avoid any issues. If you are a solo miner or mining pool operator, before the 15th of May to avoid any issues. If you are a solo miner or mining pool operator,
please see the the notes at the end of this page for how to upgrade safely. please see the the notes at the end of this page for how to upgrade safely.
</p> </p>
<h2 id="workaround">If you cannot upgrade to version 0.8.1</h2> <h2 id="backports">If you cannot upgrade to version 0.8.1</h2>
<p> <p>
If you cannot upgrade to the latest version, you can still avoid the problem. If you cannot upgrade to the latest version,
<a href="https://bitcointalk.org/?topic=199699">backports to older branches are now in final testing</a>.
These include not only compatibility for the 15 May changes, but also fixes for known vulnerabilities and bugs, which have already been included and tested in the latest release.
</p>
<h2 id="workaround">If you cannot upgrade to a backport</h2>
<p>
If you cannot upgrade to any of the above, you can still avoid the problem.
Create a file called DB_CONFIG in the bitcoin data directory, containing Create a file called DB_CONFIG in the bitcoin data directory, containing
these two lines: these two lines:
</p> </p>
@ -45,7 +53,8 @@ re-indexing operation; you <b>must</b> wait for the reindex to complete before
serving work to miners. serving work to miners.
</p> </p>
<p> <p>
And if you are creating blocks and cannot upgrade to version 0.8.1 for some And if you are creating blocks and cannot upgrade to version 0.8.1 or a
backport for some
reason, you should <b>not</b> set_lk_max_locks in a DB_CONFIG file until reason, you should <b>not</b> set_lk_max_locks in a DB_CONFIG file until
May 15th; if you increase locks before then you run the risk of creating May 15th; if you increase locks before then you run the risk of creating
or building on blocks incompatible with the rest of the network. or building on blocks incompatible with the rest of the network.