LibreOffice 188.8.131.52, 184.108.40.206 are not offering 220.127.116.11 build on Windows when running "Check for updates"
Also, rolled back and clean installed 18.104.22.168, and 22.214.171.124 (nor a 4.4 build) was not being offered.
Is this simply a repeat of issues in bug 84441 #c19?
I can confirm the bug reported by Stuart above....
Also filed to Redmine Infrastructure, if that is preferred.
The server is reporting 4.2.8 as the latest available (it's easy to check with LibreOffice 3.6.7 Portable)
So any version newer than that is reported as up-to-date.
(In reply to Pedro from comment #3)
> The server is reporting 4.2.8 as the latest available (it's easy to check
> with LibreOffice 3.6.7 Portable)
> So any version newer than that is reported as up-to-date.
No. 4.2.8 is the latest 'stable'. From 4.3.x you'd be updated to 4.3.5. No idea why this update.php is not updated regularly. Thanks for reporting it to Redmine, Stuart.
LibreOffice itself appears to be behaving correctly based on the information provided to it, so this isn't a bug of the Product "LibreOffice".
As the cause is in server infrastructure, as discussed above, I'd suggest that the Redmine issue is the right place to represent this, and this bug can be closed.
-> RESOLVED NOTABUG (...in LibreOffice itself)
hasn't been updated, as 4.4.0 had a regression re saving pw-protected documents with images that could lead to data-loss.
and you're only cross-updated (from x.y.z to x.y+1.u) if u>=z
(In reply to Christian Lohmaier from comment #6)
> hasn't been updated, as 4.4.0 had a regression re saving pw-protected
> documents with images that could lead to data-loss.
> and you're only cross-updated (from x.y.z to x.y+1.u) if u>=z
OK, that explains it. But not sure that we should have reached the 4.4.2 (x.y.z) release and still have it not offering updates within the 4.4 branch.
Also, would suggest that a more rational logic for "offering" the cross-update, e.g. x.y.z -> x.y+1.u, should be if u >= z-2. A u>=z seems too conservative.
Also, whats happening on the 4.3 side? Seems like a 4.3.5 < should be offering 4.3.6.
And of course with existing logic, 4.2.8 can now never get a cross update notice.
@Cloph, do you want this here or in Redmine?
Also for me reproducible with LO 126.96.36.199, Win 8.1. I had this problem already in the past several times with previous LO releases (I thought I had also opened a bug for this in the past, but I could not find it).
Per https://redmine.documentfoundation.org/issues/1210 check.php configuration has been updated, setting this resolved fixed.
But still, may need some logic adjustment for "offering" the cross-update, e.g. x.y.z -> x.y+1.u, should be if u >= z-2.
A u>=z seems too conservative.
Especially given that the updates remain manual decisions by the users.
*** Bug 116906 has been marked as a duplicate of this bug. ***
(In reply to V Stuart Foote from comment #11)
> *** Bug 116906 has been marked as a duplicate of this bug. ***
Added latest to Redmine as https://redmine.documentfoundation.org/issues/2594
*** Bug 126472 has been marked as a duplicate of this bug. ***