https://bugs.winehq.org/show_bug.cgi?id=47018
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|https://mega.nz/#!P35GwAZI! | |lhBkgqiKTHSbFgvgMr4zitLMc1O | |iQmB6z7YcSUWtS7A | Severity|normal |minor Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #14 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to masteruser82841 from comment #11)
if you touch my links again I will complain to you.
Threatening? Great! I'll will have the opportunity to hone my lawyer skills and get my vacations paid from you. Which country do you live in?
Joke aside, threatening will lead you nowhere but put you in trouble. If you have a personal problem with me I suggest that you contact me privately.
(In reply to masteruser82841 from comment #13)
What should I do if there is no other way to detect a bug? I don't care what you think, I provided security evidence files, and it was rebooted by me on mega due to the fact that with a hitfile where it was originally, it took a very long time to download it, and not for free. I will continue to return the url.
It depends on the license of the software which I don't know anything about.
Usually, license to use a software doesn't allow you to publicly share it. If the license and local laws allows it, you may send a private copy to a software specialist that will test the application on your behalf, but that must be done confidentially and under professional secret. Otherwise it is a violation of the copyright and/or of the licensing terms.
Moreover, you may be violating the rights of the owner of the software by making a free public link of his software while he wanted to earn money from paid download links, and The Wine project may be held liable for publishing the link. That's why linking to your private copy is discouraged.
In the situation where there are no free links to a legitimate redistributable copy or demo of the software, the bug reporter is expected to state that the software is proprietary and wait for instructions from the devs. While having access to the software helps in debugging, it is not required: The affected users can run commands and provide feedback. The devs could also test the application themselves if they have a legitimate copy of their own.
There is no point in insisting to make the link publicly visible.
Also, a black background in the installer logo is a minor issue that doesn't prevent the application from working. It doesn't seem to affect any other applications or else there would already be a bug about it, and this one would just be a dupe. There are official .NET framework installers from Microsoft that run fine in Wine and you provide no use case that requires the use of that specific repackaging.
Regards