WineHQ's WINE depends on Ubuntu's WINE?

[BOplaid]

So, I just upgraded to Linux Mint 22 (Ubuntu Noble/24.04), and the upgrade process removed WINE.
When I added the Noble repos and did everything, when I did sudo apt install winehq-devel (I always use the development branch), I got this error:

Code: Select all

boplaid@BOplaid-LMPC:~$ sudo apt install winehq-devel
[sudo] password for boplaid:         
Reading package lists... Done
Building dependency tree... Done
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:
 winehq-devel : Depends: wine-devel (= 9.17~noble-1)
E: Unable to correct problems, you have held broken packages.

The system is very much up to date, here's me doing sudo apt update && sudo apt upgrade:

Code: Select all

boplaid@BOplaid-LMPC:~$ sudo apt update && sudo apt upgrade
Hit:1 http://dl.google.com/linux/earth/deb stable InRelease
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease                         
Hit:3 http://security.ubuntu.com/ubuntu noble-security InRelease               
Hit:4 https://dl.winehq.org/wine-builds/ubuntu noble InRelease                 
Hit:5 https://repo.waydro.id noble InRelease                                   
Hit:6 http://archive.ubuntu.com/ubuntu noble-updates InRelease                 
Ign:7 https://fastly.linuxmint.io wilma InRelease                              
Hit:8 http://archive.ubuntu.com/ubuntu noble-backports InRelease               
Hit:9 https://debrepo.freedownloadmanager.org jammy InRelease       
Hit:10 https://fastly.linuxmint.io wilma Release
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I then tried winehq-stable, but the system failed to acknowledge its existence:

Code: Select all

boplaid@BOplaid-LMPC:~$ sudo apt install winehq-stable
[sudo] password for boplaid:         
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package winehq-stable

After some Ecosia-ing I figured out that the latest version of winehq-stable (which I think is 9.0) was released before Noble came out, and thus the stable branch doesn't exist for Noble.

Then I tried winehq-staging:

Code: Select all

boplaid@BOplaid-LMPC:~$ sudo apt install winehq-staging
Reading package lists... Done
Building dependency tree... Done
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:
 winehq-staging : Depends: wine-staging (= 9.17~noble-1)
E: Unable to correct problems, you have held broken packages.

So the exact same thing.
Also, if you're confused on which branch I want to use, I want to use the development branch. Just thought that wasn't clear enough.
So, what should I do?

[dimesio]

https://gitlab.winehq.org/wine/wine/-/w ... stall-wine

[BOplaid]

https://gitlab.winehq.org/wine/wine/-/w ... stall-wine

Well the page says to install whatever dependency it needs, but in my case that would mean the Ubuntu WINE.
And if I did just that, and then tried to install WineHQ's WINE, (assuming there isn't anything else blocking it from being installed) that would cause me to have two instances of WINE.
Which I do not want.

[dimesio]

Well the page says to install whatever dependency it needs, but in my case that would mean the Ubuntu WINE.

No, that would be our wine-devel package, which is the first package you're blocked on. The winehq- packages are merely compatibility packages that enable you to use our package as the default wine on your system; they pull in our 32 and 64 bit wine- packages as dependencies.

[BOplaid]

Well the page says to install whatever dependency it needs, but in my case that would mean the Ubuntu WINE.

No, that would be our wine-devel package, which is the first package you're blocked on. The winehq- packages are merely compatibility packages that enable you to use our package as the default wine on your system; they pull in our 32 and 64 bit wine- packages as dependencies.

Okay, I understand, but shouldn't it pull it by itself? There must be reason why apt isn't pulling it in by itself.

[dimesio]

Okay, I understand, but shouldn't it pull it by itself? There must be reason why apt isn't pulling it in by itself.

Yes, it should; you're trying to find out why it isn't. Somewhere down the line there is a dependency that apt can't install. You have to follow the dependencies until you find it, then fix the problem manually. Read the wiki instructions I linked to above.

[BOplaid]

Okay, I understand, but shouldn't it pull it by itself? There must be reason why apt isn't pulling it in by itself.

Yes, it should; you're trying to find out why it isn't. Somewhere down the line there is a dependency that apt can't install. You have to follow the dependencies until you find it, then fix the problem manually. Read the wiki instructions I linked to above.

Well, I installed wine-devel, and it installed perfectly. It didn't complain about any other dependencies.
Then I tried installing winehq-devel again, and it just installed a single "winehq-devel" package. Nothing else.
Then I fired up winecfg, and after also trying to install wine mono and failing and then killing wine and deleting the half-done wineprefix, I fired up winecfg again. And it worked!

I then tried installing Notepad++ (and submitted an AppDB report in the process) and it also worked!
So now, this issue is solved!