Bug 115243 - Installed Amiri version 0.111 gets downgraded to 0.109 after installation
Summary: Installed Amiri version 0.111 gets downgraded to 0.109 after installation
Status: RESOLVED DUPLICATE of bug 39743
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
6.0.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Installer-Windows
  Show dependency tree / graph
 
Reported: 2018-01-26 15:22 UTC by Volga
Modified: 2018-04-06 00:59 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
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 Volga 2018-01-26 15:22:16 UTC 
Description:
I've downloaded & installed Amiri 0.111, but after I installed LO 6.0.0.3, it was downgraded to 0.109. 
This release is available here: https://github.com/alif-type/amiri/releases/tag/0.111

Steps to Reproduce:
1. Download LibreOffice from http://dev-builds.libreoffice.org/pre-releases/win/x86_64/

Actual Results:  
After installation, when I open C:\Windows\Fonts, I saw Amiri font, but the version is 0.109. 

Expected Results:
If Amiri and other fonts are newer than bundled version, the installation wizard shouldn't replace them.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.0.0.3 (x64)
Build ID：64a0f66915f38c6217de274f0aa8e15618924765
CPU 线程：4; 操作系统：Windows 10.0; UI 渲染：默认; 
区域语言：zh-CN (zh_CN); Calc: group


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 Volga 2018-02-09 16:01:46 UTC 
Oh no, this problem appearing to me again after I update to 6.01.

Version: 6.0.1.1 (x64)
Build ID：60bfb1526849283ce2491346ed2aa51c465abfe6
CPU 线程：4; 操作系统：Windows 10.0; UI 渲染：默认; 
区域语言：zh-CN (zh_CN); Calc: group
Comment 2 Buovjaga 2018-03-03 18:38:50 UTC 

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