Xpra: Ticket #2089: Hashes for installation files

Files with hashes for the "official" version are wrong:


Also, is there a reason files are named '.sha' for the SHA-1 hash? HashCheck (at least v2.4.0, https://github.com/gurnec/HashCheck) recognizes (and binds automatically during installation) .sha1 files to match & check them.

Unless there is some reason, would you consider renaming them?

Fri, 21 Dec 2018 05:33:03 GMT - Antoine Martin: status, description changed; resolution set

Done, we still have both in the download directories for now. Just in case there are links to those.

Fri, 21 Dec 2018 09:34:52 GMT - stdedos:

Maybe I should've been more specific (or opened a separate ticket?)

The dist files contain wrong data for verification purposes:

bfbf0f47cbb7c8df9e4468c161aa3053  Xpra-x86_64_Setup_2.4.2-r21077.exe
e2da148f53f4147d99dd63a529e7e0217f21910c  Xpra-x86_64_Setup_2.4.2-r21077.exe

whereas the setup filename is Xpra-x86_64_Setup.exe (https://www.xpra.org/dists/windows/Xpra-x86_64_Setup.exe)

I understand why, but it impedes automatic verification.

Fri, 21 Dec 2018 16:34:49 GMT - Antoine Martin:

Oh, now I get it.

Wontfix: those are symlinks, apache doesn't know how to show them.

Sat, 23 Jan 2021 05:41:55 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2089