Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#63838 - [wine] msi regression, not installing dotnet35sp1

Attached to Project: Community Packages
Opened by Allan (4llan) - Thursday, 19 September 2019, 12:01 GMT
Last edited by Felix Yan (felixonmars) - Tuesday, 14 January 2020, 07:54 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Dear Maintainer,

There's a msi issue since wine-4.11 causing trouble to Service Pack installers.

Example: try to install dotnet35sp1 and you will get these errors from terminal:
0030:err:msi:MSI_OpenDatabaseW unknown flag 00000000
0030:err:msi:msi_apply_patch_package failed to open patch collection L"y:\\c5844c6052203b28ace1352bce70\\wcu\\dotNetFramework\\dotnetfx20\\ASPNET_64.msp"
0030:err:msi:ITERATE_Actions Execution halted, action L"CA_ScheduleCacheGACAssembly.3643236F_FC70_11D3_A536_0090278A1BB8" returned 1627

Office 2007 SP3 installer fails too.

I already filed a bug report upstream[1] describing what commit causes the regression more than a week ago, but still "unconfirmed".

[1] https://bugs.winehq.org/show_bug.cgi?id=47724

It's weird that I tested the old packages from Arch Linux archive, and it's reproducible since wine-4.10-1
This task depends upon

Closed by  Felix Yan (felixonmars)
Tuesday, 14 January 2020, 07:54 GMT
Reason for closing:  Upstream
Comment by Kevin Puertas (kprkpr) - Sunday, 27 October 2019, 14:13 GMT
For me is doing same weird thing some some time ago..
I commented to your wine bug (I had another, marked now as duplicate
Some fix..?
Comment by Felix Yan (felixonmars) - Tuesday, 14 January 2020, 07:54 GMT
Closing as upstream suggests that it's already fixed since 4.21.

Loading...