Re: [lmi] [lmi-commits] master a6eb063a: Adapt to wine-7.0.1

[Greg Chicares]

On 1/20/23 00:43, Vadim Zeitlin wrote:
> On Thu, 19 Jan 2023 19:29:49 -0500 (EST) Greg Chicares 
> <gchicares@sbcglobal.net> wrote:
[...]
> GC>     Upgrading from
> GC>       wine-7.0 (Debian 7.0~repack-8)
> GC>     to
> GC>       wine-7.0.1 (Debian 7.0.1~repack-1)
> GC>     causes some unwanted diagnostics to appear. Filtered them out, because
> GC>     there seems to be no safe and easy way to suppress them with 
> $WINEDEBUG.
[...]
>  I'm somewhat surprised that these messages happen now if they didn't
> happen before because this typically just indicates that there is no X
> server running and this is not something that can possibly change with a
> Wine upgrade.

Correct. I tried running while connected to an actual TTY, and did not
see these messages. The cause was not a 'wine' upgrade, but rather
running with no TTY, e.g.:
  nohup ./lmi_setup_00.sh >log_"$(date -u +"%Y%m%dT%H%MZ")" 2>&1 & disown; exit

These messages occur only when building for msw--never for GNU/Linux.
It would seem that 'wine' expects a TTY (and diagnoses its absence)
even when everything is redirected and nothing would be written on
the msw "console". IIRC, msw always requires a console, so maybe
'wine' is just emulating msw faithfully here.

Incidentally, these messages appear only for command-line tasks,
but not for the GUI test that is run under xvfb.

I just pushed a change that suppressed these messages only when '! tty -s'.