https://bugs.winehq.org/show_bug.cgi?id=47724
--- Comment #8 from Allan alln_medeiros@hotmail.com --- (In reply to Hans Leidekker from comment #7)
(In reply to Allan from comment #6)
I was able to downgrade wine and track what version introduced this issue. From 4.9 to 4.10
4.15: FAIL 4.14: FAIL 4.13: FAIL 4.12: FAIL 4.11: FAIL 4.10: FAIL 4.9: SUCCESS 4.8: SUCCESS
I'm using Arch Linux (https://archive.archlinux.org/packages/w/wine/)
Can you perform a regression test to find the commit between 4.9 and 4.10 that broke it? See https://wiki.winehq.org/Regression_Testing
I have a basic knowledge of git, c, compiling in Linux... So, sorry if I delay to reply. I'm very interested to improve in these things and thanks for pointing out the Regression Testing.
I made a big mistake of judge wine-4.10 as bisect bad and wine-4.9 as good. Made the bisect till the end just to see that 4.10 runs as expected. LOL
The current master fails to install SP3, returning 004b:err:msi:msi_apply_patch_package failed to open patch collection
I'll try to track down the real git tag that is failing, and then do the bisect.
Question: there's some trick to accelerate build time? I'm currently building win64, then win32 and the whole proccess takes more than 1 hour with my laptop.