This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 4401a18702 git-site-role commit from build_staging.sh
4401a18702 is described below
commit 4401a18702e772a7b19e3547e8116690b31c4722
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Dec 11 22:35:22 2024 +0000
git-site-role commit from build_staging.sh
---
content/download/checksums.html | 27 +++++++++++++++------------
content/feed.xml | 4 ++--
2 files changed, 17 insertions(+), 14 deletions(-)
diff --git a/content/download/checksums.html b/content/download/checksums.html
index ef60941ee7..dcfa80e0af 100644
--- a/content/download/checksums.html
+++ b/content/download/checksums.html
@@ -53,11 +53,11 @@
Windows - Verify with SHA256 and MD5</a></h3></li>
<li><h3><a href="#pgp_linux" title="How to verify with PGP/ASC and KEYS
signatures on Linux">
Linux - Verify with PGP and KEYS</a></h3></li>
- <li><h3><a href="#hash_linux" title="How to verify with SHA256 and MD5
hash values on Linux">
- Linux - Verify with SHA256 and MD5</a></h3></li>
- <li><h3><a href="#pgp_mac" title="How to verify with PGP/ASC and KEYS
signatures on Mac OS">
+ <li><h3><a href="#hash_linux" title="How to verify with SHA512 / SHA256
and MD5 hash values on Linux">
+ Linux - Verify with SHA512 / SHA256 and MD5</a></h3></li>
+ <li><h3><a href="#pgp_mac" title="How to verify with PGP/ASC and KEYS
signatures on macOS">
Mac OS - Verify with PGP and KEYS</a></h3></li>
- <li><h3><a href="#hash_mac" title="How to verify with SHA256 and MD5
hash values on Mac OS">
+ <li><h3><a href="#hash_mac" title="How to verify with SHA256 and MD5
hash values on macOS">
Mac OS - Verify with SHA26 and MD5</a></h3></li>
<li><h3><a href="#no_match" title="What to do when the values do not
match?">
What to do when the values do not match?</a></h3></li>
@@ -74,8 +74,8 @@
processed on the downloaded file is a way to make sure that the content is
transferred OK and has not been damaged during
the download process.</p>
<p><b>Note:</b><br />
-There is no need to do all the verifications. The best is to check the PGP
signature (.asc) file. Failing that, use the
-SHA256 hash, otherwise use the MD5 hash.</p>
+There is no need to do all the verification. The best is to check the PGP
signature (.asc) file. Failing that, use the
+SHA512 / SHA256 hash, or (for older releases) the MD5 hash.</p>
<br />
<h3 id="internet">Verify in the Internet</h3>
@@ -143,7 +143,7 @@ SHA256 hash, otherwise use the MD5 hash.</p>
<ul>
<li>There are several tools available like
- <a href="http://implbits.com/products/hashtab/"; title="HashTab (by
Implbits.com)">"HashTab"</a>,
+ <a href="https://implbits.com/hashtab"; title="HashTab (by
Implbits.com)">"HashTab"</a>,
<a href="http://www.pc-tools.net/win32/md5sums/"; title="MD5sums (by
PC-Tools.Net)">"MD5sums"</a>,
<a href="https://www.slavasoft.com/fsum/"; title="FSUM (by
SlavaSoft.com)">"FSUM"</a>,
<a href="https://sourceforge.net/projects/quickhash/"; title="Quick Hash GUI
(by tedtechnology)">"Quick Hash GUI"</a>,
@@ -190,20 +190,23 @@ SHA256 hash, otherwise use the MD5 hash.</p>
</ul>
<br />
-<p id="hash_linux"><b>How to verify SHA256 / MD5 hash values</b></p>
+<p id="hash_linux"><b>How to verify SHA512 / SHA256 / MD5 hash values</b></p>
<br />
<ul>
- <li>The instructions to compare SHA256 and MD5 hash values are very similar.
Therefore both are mentioned together.</li>
+ <li>The instructions to compare SHA512 / SHA256 and MD5 hash values are very
similar. Therefore they are mentioned together.</li>
<li> </li>
- <li>Open a terminal and change to the directory with the downloaded AOO and
SHA256 / MD5 file.</li>
+ <li>Open a terminal and change to the directory with the downloaded AOO and
SHA512 / SHA256 / MD5 file.</li>
<li>Type in the following commands:</li>
<li> </li>
- <li><pre>cd <path_to_AOO_and_SHA256/MD5_files></pre></li>
+ <li><pre>cd <path_to_AOO_and_SHA512/SHA256/MD5_files></pre></li>
<li><pre>md5sum -c <AOO file>.tar.gz.md5</pre></li>
<li>or</li>
<li><pre>sha256sum -c <AOO file>.tar.gz.sha256</pre></li>
<li> </li>
+ <li>or</li>
+ <li><pre>sha512sum -c <AOO file>.tar.gz.sha512</pre></li>
+ <li> </li>
<li>If the hash matches this is indicated by "<AOO file>.tar.gz: OK".
<br />Otherwise "WARNING: 1 of 1 computed checksum did NOT match".</li>
<li>If they do not match, please see the <a href="#no_match" title="What to
do when the values do not match?">
@@ -213,7 +216,7 @@ SHA256 hash, otherwise use the MD5 hash.</p>
<p class="footer"><small><a href="#" title="Go to the start of the page">Start
of page</a></small></p>
<br />
-<h3 id="pgp_mac">Verify on Mac OS</h3>
+<h3 id="pgp_mac">Verify on macOS</h3>
<p><b>How to verify with PGP/ASC signatures</b></p>
<br />
diff --git a/content/feed.xml b/content/feed.xml
index 1611e5605e..af4bfe706f 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -6,8 +6,8 @@
<atom:link href="http://localhost:8820/feed.xml"; rel="self"
type="application/rss+xml" />
<description>OpenOffice.org Feed</description>
<language>en-us</language>
- <pubDate>Wed, 11 Dec 2024 22:24:17 +0000</pubDate>
- <lastBuildDate>Wed, 11 Dec 2024 22:24:17 +0000</lastBuildDate>
+ <pubDate>Wed, 11 Dec 2024 22:34:13 +0000</pubDate>
+ <lastBuildDate>Wed, 11 Dec 2024 22:34:13 +0000</lastBuildDate>
</channel>
