[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Nuisance message from 'wine'
From: |
Greg Chicares |
Subject: |
Re: [lmi] Nuisance message from 'wine' |
Date: |
Sun, 5 Jun 2022 23:06:29 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 |
On 6/5/22 22:58, Greg Chicares wrote:
> On 6/5/22 22:34, Vadim Zeitlin wrote:
>> On Sun, 5 Jun 2022 22:28:33 +0000 Greg Chicares <gchicares@sbcglobal.net>
>> wrote:
> [...]
>> GC> it looks like wine32 is missing, you should install it.
> [...]
>> I hated this warning so much that I've worked around this in the CI
>> workflow file, see this part of it:
>>
>> # Set WINEDEBUG to avoid annoying warnings about wine32 being
>> # missing: this is not a problem in our case, we want to only
>> # run 64-bit programs in this build, so set WINEDEBUG to a
>> # value equivalent to its default/unset value but recognized
>> # as disabling error output by Debian /usr/bin/wine script.
>> echo 'WINEDEBUG=-all,err+all,fixme+all' >> $GITHUB_ENV
>>
>> Of course, you should set WINEDEBUG in your environment directly instead
>> of using (non-existent) $GITHUB_ENV.
>>
>> I think it's a bad decision to do this in Debian wrapper script, but at
>> least it's simple enough to work around it (after looking at what this
>> script does).
>
> Thanks. BTW, this:
>
> /opt/lmi/bin[0]$wine64 ./lmi_wx_shared.exe --ash_nazg
> --data_path=/opt/lmi/data
>
> seems to work smoothly, though it misses whatever benefit this line:
> export WINELOADER=$wine64
> would otherwise provide...so instead of putting that in lmi scripts,
> I'll trying installing the 'wine64' package only.
I forgot that I could do that manually:
#apt-get remove wine
#apt-get update
#apt-get install wine64
/home/greg[1]#wine
zsh: command not found: wine
/home/greg[127]#wine64
zsh: command not found: wine64
#`whence wine64-stable`
[prints "Usage:" message]
It seems better to install the 'wine' package and use your workaround.