You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: TomH [Added to the original trac issue at 7.34am, Thursday, 5th October 2017]
Well the checksum is correct which is what matters - the name isn't right because I had to rollback a failed dump and I just copied the checksum files for the previous week rather than editing them to change all the filenames.
Author: boldtrn [Added to the original trac issue at 11.30pm, Monday, 9th October 2017]
Ah ok, thanks for the explanation. The name is not unimportant, if you use the md5sum tool to verify the md5, it will fail. For a one time incident this does not really matter, but I thought the whole import process might have changed and due to that all upcoming files would have the same issue.
Reporter: boldtrn
[Submitted to the original trac issue database at 8.05am, Thursday, 14th September 2017]
I hope this is the right place to report this. Currently, the planet-latest.osm.pbf.md5 found here https://planet.osm.org/pbf/planet-latest.osm.pbf.md5 is not correct.
It contains
04bbd08cb4a6abfd2f6aba0759e877c0 planet-170925.osm.pbf
but it should be04bbd08cb4a6abfd2f6aba0759e877c0 planet-latest.osm.pbf
.The text was updated successfully, but these errors were encountered: