[pkg-wine-party] WoW64 implemented Re: Call for testing: automatically detect wine arch and WoW64

[Jens Reyer]

On 01/03/2016 12:45 AM, Michael Gilbert wrote:
> On Sat, Jan 2, 2016 at 6:39 PM, Austin English wrote:
>>> The change to default WINEDEBUG level and its documentation isn't desired.
>>
>> Upstream would greatly prefer if WINEDEBUG weren't overriden, currently bug
>> reports from users on Debian are usually worthless.

I (as user) see this usefullness already in an earlier stage. I need
this to get apps running/working. This was and is the case for every (3
out of 3) windows apps that I use, and is needed on an on-going basis
with every wine or app update.

With this information I can install relevant dll overrides, find
existing bugs, or submit bugs (for the latter see Austin's arguments).

Personally I solved this in .bashrc with
  export WINEDEBUG="fixme+all,err+all"


> Can't that be solved by kindly asking for a retry with WINEDEBUG=all?

In my experience WINEDEBUG=all isn't practically usable, because it
outputs way too much. For really debugging a problem you have to look up
specific debug channels that are documented on
https://wiki.winehq.org/DebugChannels. But as a starting point, to know
at all what is going on, I absolutely depend on some general, medium
log-level output. Unfortunately, there is no easily accessible
information available, what to use for this task, neither in Debian, nor
upstream (since it's already their default).

Therefore, can we at least document "fixme+all,err+all"?

If yes, instead or additionally to "all"? Maybe also include the
DebugChannels link and update the "Resources" section for winehq's major
documentation update last year?

Greets
jre