I'll repack the existing 1.9.0 tarballs tomorrow and put them back at the same URLs, and republish the hashes.
A new version number please - packaging systems expect tarballs once published to be invariant (since they store their own hashes), and the same file name with different contents looks like an attack. From my viewpoint, it's better to just let this be than to change the contents of an already published file. Why doesn't the setup code force the umask? It seems like this should not depend on the environment.
pgpaM25ynDbgG.pgp
Description: PGP signature
_______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev