https://bugs.winehq.org/show_bug.cgi?id=53720
--- Comment #3 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Dmytro Bagrii from comment #2)
Do you mean to bisect upstream wine if it doesn't work too? But it works. As i understand, for wine-staging i should bisect https://github.com/wine-staging/wine-staging, not https://source.winehq.org/git/wine.git, right?
Hello,
If it works with upstream Wine then, yes, it is different.
Wine-staging is only a set of patches applied on the upstream wine source. You'll need to be able to compile wine from source (https://wiki.winehq.org/Building_Wine).
It is easier to bisect wine-staging by hand (See https://wiki.winehq.org/Wine-Staging#Building_from_source and https://wiki.winehq.org/Wine-Staging#Regressions_between_Staging_versions)
There is two way to do the regression test: - Set wine and wine-staging to 7.18 and disable wine-staging patchset one at a time between each rebuild, until you find the patchset(s) that breaks the game. - Rebuild wine and wine-staging to each of the respective commit numbers from the rebase history (https://github.com/wine-staging/wine-staging/commits/master) until you find the first commit that breaks the game.
Regards.