http://bugs.winehq.org/show_bug.cgi?id=25074
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hans@meelstraat.net
--- Comment #15 from Austin English austinenglish@gmail.com 2010-11-15 23:00:44 CST --- (In reply to comment #14)
I just confirmed the regression test, and my suspicion that the commit identified has already been fixed.
I.e., git reset --hard 966d722752b659a12ffa355a1e559f94907cd66d ./configure make produces a wine that fails to install dotnet30 (though with error 67 for me, not 87 as reported.) And, git reset --hard 966d722752b659a12ffa355a1e559f94907cd66d git reset --hard HEAD~1 ./configure make produces a wine that installs dotnet30. However, git reset --hard 966d722752b659a12ffa355a1e559f94907cd66d git cherry-pick 68fceb5e5b4c345dd6d7f77d2d250f1e8a779007 ./configure make also produces a wine that installs dotnet30.
So, the remaining regression is elsewhere, and a new regression test is needed.
austin@aw21 ~/wine-git $ git bisect bad ca7cd1bf89d057d9c48896b70c441fad941e6ee0 is the first bad commit commit ca7cd1bf89d057d9c48896b70c441fad941e6ee0 Author: Hans Leidekker hans@codeweavers.com Date: Wed Oct 6 15:44:08 2010 +0200
msi: Validate packages based on supported version, platform and languages.
:040000 040000 1ef576e28c83ea59db6043d13d6921f475e26b9d 9d1df66c16e2c640d0a24677ec122f1ac773421c M dlls
Reverting that commit on HEAD fails, but I reverted it over itself (after cherry-picking 68fceb5e5b4c345dd6d7f77d2d250f1e8a779007) and that succeeds.
Unless there's a third regression somewhere, fixing this should fix dotnet30.