Quote:
Originally Posted by MetalOllie
I have the same problem. I've downloaded the file from the Calibre site, and tried from the mirrors as well, to eliminate DNS caching. I've run the update, but it still shows 2.9.0, and when reopened offers me the update to 2.11.0 again.
|
Here's the details of 2.9 and 2.11 as I have them
Code:
calibre-64-bit-2-9.0 Revision {8FBC8DFD-FDF6-4E81-8622-65644FD6FCD1}
CRC32 40550977
MD5 f30269bc99c0709ca258afa070c2966b
SHA-1 60b069470f1f6d6df3bc75d6a1fea10dca4b9390
calibre-64-bit-2-11.0 Revision {6342411D-58FD-47E9-B395-5B6ED8B373BB}
CRC32 9cf6cb9d
MD5 ca2790456a05e796527bddc75f6b7066
SHA-1 804e2e95e8a17b5b7ad11c2aeec186e57c2c2a26
You can get Revision numbers in Properties->Details and I use Nirsofts Hashmyfiles for checksums
Whoa - I suspect there was a correction release for 2.11, approx 241 minutes after initial release - the current file size, revision number and hash codes are different.
Code:
calibre-64-bit-2-11.0 Revision {8C814D0B-8B4B-415F-BFB1-0523EB6E7844}
CRC32 48fb7005
MD5 ee5dbfb7261fb465067c693df5f5ac1b
SHA-1 e0e9c3f6a5dfce98ddf29645b64d0c3eca2151b9
That's where use of third segment of version number would be useful.
BR