this post was submitted on 14 Jan 2026
34 points (100.0% liked)

Linux

5067 readers
1 users here now

Shit, just linux.

Use this community for anything related to linux for now, if it gets too huge maybe there will be some sort of meme/gaming/shitpost spinoff. Currently though… go nuts

founded 2 years ago
MODERATORS
 

The Wine team is proud to announce that the stable release Wine 11.0 is now available. This release represents a year of development effort, around 6,300 individual changes, and more than 600 bug fixes.

It contains a large number of improvements that are listed below.

https://gitlab.winehq.org/wine/wine/-/releases/wine-11.0

you are viewing a single comment's thread
view the rest of the comments
[–] pglpm@lemmy.ca 3 points 2 months ago* (last edited 2 months ago)

Edit: apt --fix-broken install solved the problem.

I got it from apt today, but, mmm...

Preparing to unpack .../00-winehq-stable_11.0.0.0~noble-1_amd64.deb ...
Unpacking winehq-stable (11.0.0.0~noble-1) over (10.0.0.0~noble-1) ...
Preparing to unpack .../01-wine-stable_11.0.0.0~noble-1_amd64.deb ...
Unpacking wine-stable (11.0.0.0~noble-1) over (10.0.0.0~noble-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-BKWjQD/01-wine-stable_11.0.0.0~noble-1_amd64.deb (--unpack):
 trying to overwrite '/opt/wine-stable/bin/wine', which is also in package wine-stable-i386:i386 10.0.0.0~noble-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../02-wine-stable-i386_11.0.0.0~noble-1_i386.deb ...
Unpacking wine-stable-i386:i386 (11.0.0.0~noble-1) over (10.0.0.0~noble-1) ...
Preparing to unpack .../03-wine-stable-amd64_11.0.0.0~noble-1_amd64.deb ...
Unpacking wine-stable-amd64 (11.0.0.0~noble-1) over (10.0.0.0~noble-1) ...

After retrying,

The following packages have unmet dependencies.
 wine-stable : Depends: wine-stable-i386 (= 10.0.0.0~noble-1)
               Depends: wine-stable-amd64 (= 10.0.0.0~noble-1) but 11.0.0.0~noble-1 is installed
 winehq-stable : Depends: wine-stable (= 11.0.0.0~noble-1)

Not sure if there's something wrong in the way I installed v10, or something quirky in their installer. I'll investigate further before going for apt --fix-broken install.