[lmi] Problem upgrading 'wine'

[Greg Chicares]

Vadim--I use 'wine' only in a chroot, debian_version being:

  /home/greg[0]$cat /etc/debian_version 
  9.6
  /home/greg[0]$cat /srv/chroot/lmi-buster/etc/debian_version
  buster/sid

for host and chroot. Today I successfully upgraded the host with
the same series of command I always use:
  #apt-get update
  #apt-get upgrade
  #apt-get dist-upgrade
  #apt-get autoremove
but when I then tried to upgrade the chroot in the same way,
on the second step I saw:

---------8<--------8<--------8<--------8<--------8<--------8<--------8<-------
#apt-get upgrade     
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 wine : Depends: wine64 (>= 4.0~rc6-1) but 3.0.3-2 is to be installed or
                 wine32 (>= 4.0~rc6-1)
E: Broken packages
--------->8-------->8-------->8-------->8-------->8-------->8-------->8-------

According to /var/log/apt/history.log I last upgraded wine here:
  wine32:i386 (3.0.2-2, 3.0.3-2)
  wine64:amd64 (3.0.2-2, 3.0.3-2)2:8.1.0320-1)
  wine:amd64 (3.0.2-2, 3.0.3-2)
  libwine:amd64 (3.0.2-2, 3.0.3-2)
  libwine:i386 (3.0.2-2, 3.0.3-2)
  End-Date: 2018-11-15  03:23:44
and my last upgrade of the chroot (which didn't affect wine) was:
  Start-Date: 2018-12-10  16:31:42
  Commandline: apt-get upgrade

[Migrating eventually to a 64-bit-only universe will make such
upgrades simpler, among its other advantages.]

Now, according to
  https://tracker.debian.org/pkg/wine
as of 2018-12-11 (a day after my last chroot upgrade) a new version
of wine has entered the stable and testing distributions. My
currently-installed version
  $wine --version
  wine-3.0.3 (Debian 3.0.3-2)
still works (lmi's msw GUI test still runs successfully), so the
"Broken packages" message would seem to refer to the new version 4,
and I'd be tempted to guess that this message:
  wine : Depends: wine64 (>= 4.0~rc6-1) but 3.0.3-2 is to be installed
means that apt-get thinks that the 'wine' package requires a new
'wine64', but that the old 'wine64' is required for some other reason.
(Is there any real likelihood that debian's 'wine' packaging is really
inconsistent, and has remained so for about a month?)

I recall that some time ago we discussed using a 'wine' backport, but
I don't seem to be using any backports in this chroot:

  $cat /etc/apt/sources.list 
  deb http://deb.debian.org/debian/ buster main
  deb http://deb.debian.org/debian/ buster-updates main
  deb http://security.debian.org/   buster/updates main

so I don't know why its debian_version is 'buster/sid'.

Anyway, what should I do now? I imagine that I could uninstall and then
reinstall 'wine', and that might actually work; however, since it might
not, I'd probably put this working chroot aside for safety and create a
new one. Is there any simpler or safer way forward?