Hi Jim, Am 03.11.18 um 19:48 schrieb Jim Jagielski: > I'm not exactly sure 100% what needs to be changed... Plus, if we change the > names of files, don't we need to ensure that the sourceforge links are > correct as well? Has that been looked at?
I assume you are referring to our discussion about the SHA512 files? Pedro explained it here: > Actually there is a bigger problem with the SHA512 files for _all_ the > binaries in the RC1 folder: they include the folder name > > Example > SHA512(./en-US/Apache_OpenOffice_4.1.6_Linux_x86-64_install-deb_en-US.tar.gz)= > > c8caa278fd881be393ad2905ef1c89d5e96710ab4d758c254102b2f9f6fbca21ad9bfba8ef375b13b3d982da0627d195ac40dbd9e7aa10c780b6d2ea6891bcfb > > Should be > SHA512(./Apache_OpenOffice_4.1.6_Linux_x86-64_install-deb_en-US.tar.gz)= > c8caa278fd881be393ad2905ef1c89d5e96710ab4d758c254102b2f9f6fbca21ad9bfba8ef375b13b3d982da0627d195ac40dbd9e7aa10c780b6d2ea6891bcfb > > Or even easier > > c8caa278fd881be393ad2905ef1c89d5e96710ab4d758c254102b2f9f6fbca21ad9bfba8ef375b13b3d982da0627d195ac40dbd9e7aa10c780b6d2ea6891bcfb > *Apache_OpenOffice_4.1.6_Linux_x86-64_install-deb_en-US.tar.gz > > Thanks! > Pedro There was a little problem in our script "hash-sign.sh", which is now solved (hopefully). I did correct all sha512 files for the Windows builds, so the ones for macOS and Linux32/64 remain to be updated. Regards, Matthias > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
smime.p7s
Description: S/MIME Cryptographic Signature
