Bug 128535 - Updater offers incorrect new version
Summary: Updater offers incorrect new version
Status: RESOLVED DUPLICATE of bug 90456
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL: https://cgit.freedesktop.org/libreoff...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-01 15:23 UTC by dbonham+bugzilla
Modified: 2019-11-02 03:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Check for Updates window (10.60 KB, image/png)
2019-11-01 15:30 UTC, dbonham+bugzilla 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dbonham+bugzilla 2019-11-01 15:23:45 UTC 
Description:
If I check for updates and a new version is available, I am only offered a slightly newer release... not the correct most current version available. For example, if I am running v6.3.1.2, the updater offers me 6.3.2 even though 6.3.3 is available. The updater should always offer the most current release, not a step in between.

This can cause a user to download the slightly newer release and install it, then be immediately told there is a newer release.

Steps to Reproduce:
1. Select Help -> Check for Updates from within a LO program
2. Note current version installed & offered version for download
3. Visit website and note the actual newest release available.

Actual Results:
Offered one minor version newer than currently installed.

Expected Results:
I should be offered the most current release.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Comment 1 dbonham+bugzilla 2019-11-01 15:30:15 UTC 
Created attachment 155451 [details]
Check for Updates window
Comment 2 V Stuart Foote 2019-11-02 03:45:27 UTC 
This is an infrastructure issue. The ref CURL posted check script again needs signature updates done periodically during release cycles.

*** This bug has been marked as a duplicate of bug 90456 ***