mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 09:46:12 +00:00
7d98f798ab
Gemfile:
- Upgrade to Jekyll 3.x (3.0.1 tested). This brings several new
features I want to use, most notably *collections* which allows us
to add blog-like collections. I've converted the `_releases` and
`_alerts` pages into collections, although their plugins are
maintained to handle the Download and Active Alert features.
- Upgrade to latest Kramdown.
- Lock Less at 2.4.0. This prevents breaking our Less plugin. Jekyll
3.x provides native support for SCSS, so we may want to switch to
that in time.
- Lock HTML Proofer at 2.1.0. The most recent version was taking
forever to check our pages (I never actually got it to complete).
I'll look into it when I get more time.
Makefile:
- New `make clean` command. Jekyll 3.x by default attempts to do
incremental rebuilds. The new `jekyll clean` command cleans up the
metadata necessary for than so that a full build is performed, and
this new `make clean` command is a wrapper around it so that we
automatically do full rebuilds in the relevant cases. Note: our
plugins aren't fully compatible with the incremental rebuilds, but
I'd like to fix that in the future.
- Remove WEBrick hack to enable previewing with default URL paths (/
instead of /index.html).
- Filter out compliants from Rouge
README.md:
- Now that Alerts (_alerts) are part of a collection, the file names
are no longer parsed for dates, so instructions on adding the date
to the YAML metadata have been added.
_alerts/*:
- Now that alerts are part of a collection, the file names are no
longer parsed to provide dates, so a `date:` field has been added to
the YAML metadata.
_config.yml:
- Some variables renamed per upgrade instructions.
- Switched from old default syntax highlighter Pygments to new default
Rouge. I tried to use Rouge options to keep new output as similar
to old output as possible to making diffing easy, but Rouge adds
extra CSS class info.
- Move `_alerts` and `_releases` into Jekyll 3.x "collections", which
provide the organizational features we were using plugins to
manange. I haven't removed the old plugins because we still use
some of their features (alerts.rb provides active issue and banner
features; releases.rb provides info to Download page)
- _layouts/* can no longer provide default global metadata; that is now
provided in the new `defaults:` section in _config.yml.
_layouts/*:
- Default metadata can no longer be provided in the layout files for
collections, so I've removed it and left a message to see
_config.yml.
_plugins/*:
- Remove filter_for.rb. It's completely broken on Jekyll 3.x because
of changes to Liquid which prevent adding new arguments to the
inherited Liquid::For class. Existing uses of filter_for have been
migrated to built-in for loops prefaced by sorts.
- Remove remove-html-extension.rb: at it said in the comments, this
was a temporary hack to get us to Jekyll 3.0.
_releases/*:
- Rename all the files: prefix a v to the file name so the output html
(e.g. v10.0.0.html) is the same as the source filename (e.g.
v10.0.0.md). This is necessary to migrate them to a Jekyll collection.
- Remove %v from titles: we have to explicitly set the title, like we
used to. Again required for migration to collections.
_templates/events.html & en/rss/events.rss:
- Sort events by date and then loop with regular for loop rather than
filter_for
en/alerts.html & en/rss/alerts.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
en/bitcoin-core/index.md & en/version-history.html & en/rss/releases.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
73 lines
3.2 KiB
HTML
73 lines
3.2 KiB
HTML
---
|
|
title: "15 May 2013 Upgrade Deadline"
|
|
shorturl: "may15"
|
|
active: false
|
|
banner: ""
|
|
date: 2013-03-15
|
|
---
|
|
<h2 id="what-is-happening">What is happening</h2>
|
|
<p>
|
|
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,
|
|
<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.
|
|
</p>
|
|
<p>This bug does not affect any bitcoins you already have, but if you do nothing you will
|
|
be out of sync with the rest of the Bitcoin network and will be unable to receive
|
|
bitcoins (payments sent to you will look like they never get confirmed, or will be confirmed
|
|
very slowly). You also risk being the victim of a "double-spend" attack, where somebody sends
|
|
you bitcoins that the rest of the network would reject as invalid.
|
|
</p>
|
|
<p>
|
|
We recommend that you
|
|
<a href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.1/">upgrade to version 0.8.1</a>
|
|
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.
|
|
</p>
|
|
<h2 id="backports">If you cannot upgrade to version 0.8.1</h2>
|
|
<p>
|
|
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 this line:
|
|
</p>
|
|
<blockquote>
|
|
<pre>
|
|
set_lk_max_locks 537000
|
|
</pre>
|
|
</blockquote>
|
|
<p>
|
|
<a href="https://en.bitcoin.it/wiki/Data_directory">Look here</a> if you need help
|
|
finding the bitcoin data directory.
|
|
</p>
|
|
<h2 id="miners">Miners/mining pool operators</h2>
|
|
<p>
|
|
If you are creating new blocks (you are a solo miner or mining pool operator), then
|
|
you should be aware that upgrading from 0.7 to 0.8 requires a lengthy
|
|
re-indexing operation; you <b>must</b> wait for the reindex to complete before
|
|
serving work to miners.
|
|
</p>
|
|
<p>
|
|
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
|
|
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.
|
|
</p>
|
|
<h2 id="why-necessary">Why this is necessary</h2>
|
|
<p>
|
|
A bug caused a <a href="/chainfork">temporary block chain fork on 11 March, 2013</a>.
|
|
After investigating
|
|
that bug, we determined that the bug can happen even if the entire network was
|
|
still running old versions of Bitcoin-Qt/bitcoind. Therefore, the only option is to
|
|
require everybody to either upgrade or workaround the bug.
|
|
</p>
|
|
|
|
<div style="text-align:right">
|
|
<i>This notice last updated: Fri, 10 May 2013 21:30:00 UTC</i>
|
|
</div>
|