Mining on private network & wrong DAG epoch

[debris]

After mining on main network, I unable to mine on private one.

--- ethereum/go-ethereum ‹develop* ?› » ./geth console                                                                                                                                                  2 ↵
Welcome to the FRONTIER
> admin.miner.start()
true
> eth.blockNumber
51365
> ^C
2015/04/08 20:21:18 [TXP] Stopped
2015/04/08 20:21:18 [Blockpool] Stopping...
2015/04/08 20:21:18 [Blockpool] Stopped
--- ethereum/go-ethereum ‹develop* ?› » ./geth --datadir="/Users/marekkotewicz/Library/eth0" --bootnodes="" --protocolversion="101" --rpc=true --rpccorsdomain="http://localhost:2000" console
Welcome to the FRONTIER
> admin.miner.start()
[native] error Saved DAG in '/tmp/dag' reports to be from future epoch 1 (current epoch is 0)

> eth.blockNumber
955

[obscuren]

This will be addressed once ethash takes core of file handling. #555

Once ethash is finished, its API will allow us to specify the in which location the DAG is saved and properly revisions the DAGs. This will then be a non-issue.