Description: I got a prompt that an update is available (yay!), Check for Updates says "LibreOffice 6.0.3 is available." But when I click [Download...], the web page offers a download of 6.0.4. Steps to Reproduce: 1. Choose Help > Check for Updates 2. Click [Download...] Actual Results: The Check for Updates window displays Status LibreOffice 6.0.3 is available. The installed version is LibreOffice 6.0.2.1. and Description The automatic download of the update is currently not available. Click 'Download...' to download LibreOffice 6.0.3 manually from the web site. Clicking the [Download...] button opens the URL https://www.libreoffice.org/download/download/?lang=en-US&version=6.0.3 in my browser, but that page is offering LibreOffice 6.0.4 for download. Expected Results: It's odd that the versions don't match, the Check for Updates window should display LibreOffice 6.0.4 is available. ... to download LibreOffice 6.0.4 manually ... Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.0.2.1 (x64) Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: group User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Thanks for posting, valid. But this is a release issue to refresh the PNP used for the Update check dialog [1] handled on the Redmine tracker. @cloph? =-ref-= https://cgit.freedesktop.org/libreoffice/website/tree/check.php?h=update
This is happening again, Windows LibreOffice 6.3.1.2 Check for Updates reports LibreOffice 6.4.4 is available. but if you click the [Download...] link, the LibreOffice /download/download/ page offers "LibreOffice 6.4.5" I'm reopening here because I don't have access to or understanding of the "Redmine" system to which this was MOVED. The issue there https://redmine.documentfoundation.org/issues/2594 mentions https://cgit.freedesktop.org/libreoffice/website/tree/check.php?h=update , whose complicated $build_hash_to_version array ends at 6.3.2, so the fix now probably lies elsewhere; I couldn't find it in https://github.com/tdf/
see https://redmine.documentfoundation.org/issues/3233 fact that you were advised update was available shows it is working--but as with the PHP the config file for the http is only tweaked periodically.