corrupted planet file on stopping update

[GoogleCodeExporter]

What steps will reproduce the problem?

1.During planet file update "stop" was selected (to save 4+ hours of 
processing) and output reported "planet file (xxx) does not match..."  
Unfortunately I did not capture exact message and log file was subsequently 
over-written but it indicated that file was "corrupted".
2.On next run planet file is checked and then new planet file is downloaded 
(20Gb!) 
3.

What is the expected output? What do you see instead?

I expect that planet update exits gently when "stop" is selected. Alternatively 
is there a method to use the planet backup file?

Please use labels and text to provide additional information.

ver 1.2 r253, Ubuntu 11.10

Original issue reported on code.google.com by mappit...@gmail.com on 1 Mar 2013 at 7:20

• Merged into: #96

[GoogleCodeExporter]

There was a bug in the software causing unintentional delete of the old planet 
file when planet download was stopped - see Issue 96. The problem was fixed in 
r253.

Without a log with indicative message, your report can't be verified for 
further processing.

Original comment by mantl...@gmail.com on 1 Mar 2013 at 7:46

• Changed state: Duplicate