Closed dplarina closed 10 years ago
The failure is because it's comparing the hash against the contents of the MD5 file which has the filename next to the hash. "556e753d7c4c8033593ad34aab607d52" != "556e753d7c4c8033593ad34aab607d52 planet-140122.osm.pbf"
I've fixed that now and tested it on a full planet installation. Working OK, so closing this ticket.
Ran the check against the whole planet download manually and the hash is an exact match to the MD5 file. The script fails reporting the MD5 check failed.