goran at krampe.se writes:
> Yes, this is an unfortunate situation that I need to go through. The
> problem is that after I introduced the server side cache and SHA
> checksumming apparently lots of releases either were non-available at
> the time I initially populated the cache (which lead to crap files in
> the server cache, and to make things worse - crappy checksums!) OR have
> been unavailable when releases have been registered. I think.

I run into this as well if SqueakMap downloads while the network is
unavailable.  It saves to the file an error message, and so of course
its checksum is wrong.  So, the tool could be more careful about
checking that the HTTP request worked, before saving the file.

Recursive delete on the SqueakMap directories works fine in this case.
You can then restart SqueakMap and it will repopulate its directories
from the network.

I also ran into this when I tried to update the URL of a released
SqueakMap version.  Maybe this is more in the line of what you discuss
with bad cached information on the server.  I ended up bumping the
version number even though the actual file content had not changed.


-Lex