https://bugs.winehq.org/show_bug.cgi?id=48243
--- Comment #9 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Bugzilla is no place for discussion and I'm not open to debate, but since you would like me to be polite I'll reply.
1. My position toward the reporter is not without reasons.
He's an adept of filing bugs against cracked or repackaged software, and have been repeatedly disrespectful and rude towards those who referred to the rules and guidelines (bug 47113, bug 48127, bug 48128).
Other than that I don't have anything personal against him. I tried to help him with his issues nonetheless. I would treat anyone who repeatedly breaks the rules the same.
Rules and policies have to be enforced or they loose their meaning. Someone has to do it and if it means being rude to offenders, then so be it.
If you're too nice some people will think they can do it again and get away with it. You have to be firm and show determination when you tell them to stop. Some people don't listen if you don't yell at them.
It would be great if everyone was nice and only did innocent mistakes, but that's not the world I live in.
2. Excerpt from https://archive.org/about/:
"Anyone with a free account can upload media to the Internet Archive. We work with thousands of partners globally to save copies of their work into special collections."
Anyone can upload anything and make it available to the public, so it's equivalent to a generic filesharing website.
When it's the only way to get the software, generic filesharing websites are acceptable (copyright matters aside), however, the problem is more that the authenticity of files on a generic filesharing website can't be verified without comparing them with a 'known-good' copy.
In this case the redistributable can easily be found on the publisher's website. I'll not loose time verifying whether the redistributable on archive.org is repackaged or not. I was nice enough to put the link to the publisher's website myself and tell the reporter to test the official redistributable. The reporter could have put the link himself instead of making up blatant lies.
3. At first look, the two bugs looked the same to me - No crash, same fixmes.
I was only triaging the bug and had no intention of testing the application.
Thanks for digging into the issue and disambiguate the bugs.
Regards.