https://bugs.winehq.org/show_bug.cgi?id=33450
--- Comment #15 from Austin English austinenglish@gmail.com --- (In reply to Anastasius Focht from comment #14)
Hello Jarkko,
--- quote --- Is this really valid? --- quote ---
if you are questioning the validity of this bug you should come up with a thorough research/explanation.
I have no problem to hear alternate conclusions - which do happen, albeit very rarely. Make sure you are up to the task of understanding what all these bugs are about before making claims. Just stating "still a problem with Wine <version>" is ok. Guesswork should be avoided unless you can substantiate it with details/facts.
The bug is still valid and it's easily verifiable: remove the workaround for this bug in 'dotnet35' recipe in 'winetricks' script and run the recipe on a clean 32-bit WINEPREFIX.
Regards
Hi Anastatius,
So while poking around in winetricks today, I noticed that it isn't applying this workaround for wine versions < 1.5.28.
To be sure, I removed the whole section, and ran: $ winetricks -q -v --verify dotnet35
------------------------------------------------------ .Net Verifier returned 0 ------------------------------------------------------ ------------------------------------------------------ verify_dotnet35 succeeded! ------------------------------------------------------
The patch still partially applies, though, so I'm not sure what's happening. None of the dependencies of dotnet35 install native msxml3 either, so it's not that..
This was with wine-2.8-540-ge0e4f9bbcd, for reference.