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.
winehq-staging : Depends: wine-staging (= 4.0~rc7~bionic)
E: Unable to correct problems, you have held broken packages.

1. I removed all Wine packages that I'm aware of other than PlayOnLinux as that shouldn't affect this. I also left the Wineasio & Wineasio-amd64 packages from the kxstudio repo as I need them. I went to remove the Wine-rt and Wine-rt-amd64 packages which also came from the kxstudio repo, but removing them will also remove Wineasio and PlayOnLinux, so I left them installed.

That is the default system version of Wine for Mint (which is not even listed in the software manager) so I think it's ok to leave it as the new install should just go over it like it has in the past when I've installed Wine this way.

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.
winehq-staging : Depends: wine-staging (= 4.0~rc7~bionic)
E: Unable to correct problems, you have held broken packages.

Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
wine-staging-i386:i386
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

In the past I had installed Wine staging from the Wine repo and it worked fine. I had issues with the repo at some point in the past couple of months though so I just removed it and went back to the system version while I waited for them to sort out the repo/key issues. It seems like there is still some stuff left over from the previous Wine Staging install. I tried deleting the Wine Staging folder in /opt/ and then ran an update and tried installing Wine Staging again but was met with the same error message. Anyone know how to fix this?

Thanks!

Last edited by Death on Thu Jan 31, 2019 2:37 am, edited 1 time in total.

Very probably unrelated, but I just installed wine-staging and linvst current binaries in Xubuntu 18.04 LTS following the Ubuntu instructions found at wineHQ and it installed OK. Haven't tested the setup yet, though.

If there are other wine versions hanging around then that might cause some installation errors, maybe.

Yeh I did I did uninstall all versions of Wine that I could find and removed the WineHQ ppa. I think it's something to do with the previous WineHQ install when I had an early version of v4 installed because that's what was referenced in the terminal output and it was only from the previous WineHQ install that I had version 4 - I didn't get it from anywhere else.

jonetsu wrote:Very probably unrelated, but I just installed wine-staging and linvst current binaries in Xubuntu 18.04 LTS following the Ubuntu instructions found at wineHQ and it installed OK. Haven't tested the setup yet, though.

Yeh it worked fine for me when I last installed it until there was an issue with the key which led to me uninstalling it. Since trying to reinstall from WineHQ, I've had this issue.

jonetsu wrote:Just an idea, before re-trying is there a complete purge of a previous version like by using dpkg --purge ?

There is something in the Mint update manager called "Purge residual configuration". I'm 99% sure I already ran that but I could try it again, or I could try via the terminal instead. Is the exact command

What I posted was an example run. As in the basic flow on how it goes, how to verify if things gets done. You have to read the output of the commands that your OS will return and not just follow what I've shown as output. This is why I posted the output of the command for my OS: to show the basic flow of how it goes by the removal of only two packages, including an error, then the reinstall from the winehq Ubuntu instructions. In a real case you'd be removing all wine-related packages then make sure they are removed, then restart from the winehq Ubuntu instructions.

jonetsu wrote:What I posted was an example run. As in the basic flow on how it goes, how to verify if things gets done. You have to read the output of the commands that your OS will return and not just follow what I've shown as output. This is why I posted the output of the command for my OS: to show the basic flow of how it goes by the removal of only two packages, including an error, then the reinstall from the winehq Ubuntu instructions. In a real case you'd be removing all wine-related packages then make sure they are removed, then restart from the winehq Ubuntu instructions.

Yeh I get that. I don't just blindly copy and paste things people tell me - I try to learn as I go. I just didn't realise I need to add the "i386" part. I mean why didn't I need to put "wine-rt-i386:i386" as that's how it's written.. it's just a bit confusing making sense of these terminal outputs sometimes. Anyway, it appears I've removed that and now got Wine Staging installed again now Hopefully it's all good so I'll see how it goes and then post back if there's issues. Thanks for the help!

Should be OK. I've installed it recently on a similar system, Xubuntu 18.04 LTS and it installed just fine, along with the linvst binaries. By now I've re-installed several Windows VSTs and they work fine (in Bitwig 2.4.3 - should be the same with Mixbus32C) except for the Melda plugins which have a serious problem or rather, linvst has a serious problem with them. Used to work very fine in Linux MInt 18.1 KDE and I still have this system as dual-boot.

Death, thanks for posting this thread. I recently migrated back to Mint a few weeks ago and ran into this same problem, but never attempted to solve it because I've been trying to stop using WINE (it's a crutch in my audio workflow). I had the same issue of mentally blocking out the "i386" part of the package install. WINE is up and running on my system, now I just need the discipline to stop using it so much...