On 2020-04-23 at 15:18, Dale Harris wrote: > On Thu, Apr 23, 2020 at 2:39 PM The Wanderer <wande...@fastmail.fm> wrote:
>> (It does seem *really* odd to be getting Debian packages from an >> OpenSUSE repository, but I have no specific reason to expect them to be >> a problem.) > > I don't disagree. FTR for the list's awareness: this is in regard / reference to one of the two repositories added as a result of following the directions at https://computingforgeeks.com/how-to-install-wine-on-debian/ >> ...that looks like an unnecessarily complicated install procedure, to >> me. I'm not sure what the benefit is supposed to be, vs. just installing >> the wine or wine-development package from the official Debian >> repositories. I certainly don't think it came from anyone on the Debian >> side, nor is it something that Debian is likely to particularly support. > > Right, well, I went that route hoping to get anything installed, because > wine32 was failing. > >> What do you get if you just try >> >> # apt-get install wine > > # apt install wine32 This isn't actually the same package. I expect that the same result would follow, because wine will pull in wine32, but exact package names can be important and I think this may be the second time in this process that you've tried installing a different one from what was suggested. > Reading package lists... Done > Building dependency tree > Reading state information... 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: > wine32:i386 : Depends: libwine:i386 (= 4.0-2) but it is not going to be > installed > E: Unable to correct problems, you have held broken packages. What (if anything) do you get from the following commands? $ apt-mark showhold $ grep wine /etc/apt/preferences /etc/apt/preferences.d/* What does the following command report? $ apt-cache policy wine wine32 wine64 libwine >> The wine-development package available in stable has version 4.2-4, and >> the one in testing has version 5.4-1, at least as of a few days ago or >> so. For myself, I run the latter, when I need to run Wine. > > I don't necessarily need a newer version of wine, I just need anything, and > that's what I'm not getting currently, because nothing is installing. That you don't need newer than what's in stable is good, because the failure of any such packages to install is something we can probably troubleshoot and get fixed. It might take a bit of working at, but this sort of thing is resolved all of the time. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature