Bug 449131 - 1.9.4 & 1.9.3 confusion
Summary: 1.9.4 & 1.9.3 confusion
Status: RESOLVED FIXED
Alias: None
Product: kdiff3
Classification: Applications
Component: application (show other bugs)
Version: 1.9.4
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: michael
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-25 11:42 UTC by 石庭豐
Modified: 2022-01-28 22:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
During setup, 1.9.3 is shown instead of 1.9.4 (28.79 KB, image/png)
2022-01-25 11:42 UTC, 石庭豐 		Details
Version of KDiff3 in App is also shown as 1.9.3 instead of 1.9.4 (19.03 KB, image/png)
2022-01-25 11:43 UTC, 石庭豐 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description 石庭豐 2022-01-25 11:42:04 UTC 
STEPS TO REPRODUCE
1. Go to https://download.kde.org/stable/kdiff3/ and download kdiff3-1.9.4-windows-64-cl.exe
2. Run the setup to install it
3. Open "Apps" and read the installed version

OBSERVED RESULT
1. KDiff3 setup window title shows KDiff3 1.9.3 (see attached image)
2. KDiff3 version is shown as 1.9.3 (see the other attached image)

EXPECTED RESULT
1. KDiff3 setup window title shows KDiff3 1.9.4
2. KDiff3 version is shown as 1.9.4

SOFTWARE/OS VERSIONS
Windows: Windows 10 (but this is unrelated)
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Help > About shows 1.9.4
Comment 1 石庭豐 2022-01-25 11:42:40 UTC 
Created attachment 145903 [details]
During setup, 1.9.3 is shown instead of 1.9.4
Comment 2 石庭豐 2022-01-25 11:43:27 UTC 
Created attachment 145904 [details]
Version of KDiff3 in App is also shown as 1.9.3 instead of 1.9.4
Comment 3 石庭豐 2022-01-28 14:26:35 UTC 
I saw that a new kdiff3-1.9.4-windows-64-cl.exe was available at https://download.kde.org/stable/kdiff3/
This new file corrected all the issues stated in this ticket.
This ticket can be closed.

PS: Normally, a distinguished new filename, eg kdiff3-1.9.4-1-windows-64-cl.exe, should have been used instead of using exactly the same name to avoid further confusion.