http://bugs.winehq.org/show_bug.cgi?id=2932
------- Additional Comments From Speeddymon@gmail.com 2005-10-05 22:12 ------- Got your email, unfortunately, a bit too late. I won't be available for a few days in the evening (any time in the morning is good though lol).
Basically if you go to the main winehq site and look thru the faqs/docs for regression testing you can find step by step instructions. You have the hard part of compiling from CVS down, which is compiling the source. You don't _need_ the wine-cvsdirs package though, although you can get it if you want..
Basically you login to cvs with cvs login, checkout the current version of wine and copy (not move) the directory you checked it out to.
Update the original download directory to a _previous_ date a minute or so before the time in this email: http://www.winehq.org/hypermail/wine-cvs/2005/01/0107.html is good..
Then compile and test, and report whether it works or not. If it does, update to about a minute after that email and do the same. If it still works, update to a minute or so before the time in this email: http://www.winehq.org/hypermail/wine-cvs/2005/01/0278.html test and report. If it _still_ does, update to a minute or so after that email, and do the same. If it works after that, we are back to square one.
The first time it stops working (in a version a minute after a patch time in cvs) is your signal that the patch you just updated 1 minute past is the one causing the problem..
Make sure you include the timezone in the update commands, or else we wont know which version of the files you are testing with, in case none work..
By the way, the link to the regression testing info is at: http://winehq.org/site/docs/wine-devel/x1316
-
Wine Bugs