This ensures that package core doesn't depend on package accounts and
resolves an age-old TODO.

Support for legacy version 0.9.x is gone. The compiler version is no
longer cached. Compilation results (and the version) are read directly
from stdout using the --combined-json flag. As a workaround for
ethereum/solidity#651, source code is written to a temporary file before
compilation.

Integration of solc in package ethapi and cmd/abigen is now much simpler
because the compiler wrapper is no longer passed around as a pointer.

Fixes #2806, accidentally

The account manager was previously created by packge cmd/utils as part
of flag processing and then passed down into eth.Ethereum through its
config struct. Since we are starting to create nodes which do not have
eth.Ethereum as a registered service, the code was rearranged to
register the account manager as its own service. Making it a service is
ugly though and it doesn't really fix the root cause: creating nodes
without eth.Ethereum requires duplicating lots of code.

This commit splits utils.MakeSystemNode into three functions, making
creation of other node/service configurations easier. It also moves the
account manager into Node so it can be used by those configurations
without requiring package eth.

rpc: client bug fixes

eth/downloader: abort sync if master drops (timeout prev)

eth, eth/downloader: don't forward the DAO challenge header

eth, eth/downloader: better remote head tracking

Makefile, build: move cross compilation into ci.go

core/vm: hide ecrecover error message

Fixes #2825

It's inconsistent not to pass it and most callers will
work with contexts anyway.

I initially made the client block if the 100-element buffer was
exceeded. It turns out that this is inconvenient for simple uses of the
client which subscribe and perform calls on the same goroutine, e.g.

    client, _ := rpc.Dial(...)
    ch := make(chan int) // note: no buffer
    sub, _ := client.EthSubscribe(ch, "something")
    for event := range ch {
        client.Call(...)
    }

This innocent looking code will lock up if the server suddenly decides
to send 2000 notifications. In this case, the client's main loop won't
accept the call because it is trying to deliver a notification to ch.

The issue is kind of hard to explain in the docs and few people will
actually read them. Buffering is the simple option and works with close
to no overhead for subscribers that always listen.

Godeps: update github.com/rjeczalik/notify to f627deca7a51

Fixes #2829

node, p2p, internal: Add ability to remove peers via admin interface

Fix README typo

"fine graned" -> "fine-grained"

containers/docker: use shallow clone of single branch

eth/downloader: fix the stall checks/drops during sync

rpc: add new client, use it everywhere

eth, eth/downloader, eth/fetcher: delete eth/61 sync code

The new client implementation supports concurrent requests,
subscriptions and replaces the various ad hoc RPC clients
throughout go-ethereum.

If a batch request contained an invalid method, the server would reply
with a non-batch error response. Fix this by tracking an error for each
batch element.

The server delayed closing of connections for 3s when stopping. This was
supposed to allow for slow handlers, but it didn't really work. When
geth quits, it will just exit immediately after quitting the server.

Removing the timer makes testing easier because all connections will be
closed after Stop returns.

eth/api: rename signAndSendTransaction to sendTransaction

The eth/61 protocol was disabled in #2776, this commit removes its
message handlers and hash-chain sync logic.

containers/docker: update to alpine 3.4

eth: cancel DAO challenge on peer drop (annoying log)

Godeps: bump github.com/syndtr/goleveldb/... to ab8b5dcf104