Edit: explicitly downgrading to 10.1 with

sudo apt install wine-staging=10.1~focal-1 wine-staging-amd64=10.1~focal-1 wine-staging-i386:i386=10.1~focal-1 winehq-staging=10.1~focal-1

worked for me, but see other solutions posted below.

Thank you for the help!


On Ubuntu, the last apt upgrade of Wine broke down, bringing down the whole apt system:

The following packages have unmet dependencies. wine-staging : Depends: wine-staging-amd64 (= 10.2~focal-2) but 10.2~focal-1 is installed

At the suggestion of running sudo apt --fix-broken install, this is what happens:

Unpacking wine-staging-amd64 (10.2~focal-2) over (10.2~focal-1) ... dpkg: error processing archive /var/cache/apt/archives/wine-staging-amd64_10.2~focal-2_amd64.deb (--unpack): trying to overwrite '/opt/wine-staging/bin/wine', which is also in package wine-staging-i386:i386 10.2~focal-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/wine-staging-amd64_10.2~focal-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

Apparently this is also happening on Linux Mint: https://forums.linuxmint.com/viewtopic.php?t=441158

Any suggestions? Cheers!

  • stravanasuOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 days ago

    Edit: explicitly installing 10.1 with

    sudo apt install wine-staging=10.1~focal-1 wine-staging-amd64=10.1~focal-1 wine-staging-i386:i386=10.1~focal-1 winehq-staging=10.1~focal-1
    

    worked.

    Thank you for the help!

    But I can’t remove wine-staging, at least not via apt:

    $ sudo apt remove wine-staging-i386
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    You might want to run 'apt --fix-broken install' to correct these.
    The following packages have unmet dependencies.
     wine-staging : Depends: wine-staging-i386 (= 10.2~focal-2)
                    Depends: wine-staging-amd64 (= 10.2~focal-2) but 10.2~focal-1 is to be installed
    E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
    

    So no go there. --fix-broken doesn’t work either:

    $ sudo apt --fix-broken install
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Correcting dependencies... Done
    The following additional packages will be installed:
      wine-staging-amd64
    The following packages will be upgraded:
      wine-staging-amd64
    1 to upgrade, 0 to newly install, 0 to remove and 9 not to upgrade.
    3 not fully installed or removed.
    Need to get 0 B/114 MB of archives.
    After this operation, 15.4 kB of additional disk space will be used.
    Do you want to continue? [Y/n] Y
    Preconfiguring packages ...
    (Reading database ... 393922 files and directories currently installed.)
    Preparing to unpack .../wine-staging-amd64_10.2~focal-2_amd64.deb ...
    Unpacking wine-staging-amd64 (10.2~focal-2) over (10.2~focal-1) ...
    dpkg: error processing archive /var/cache/apt/archives/wine-staging-amd64_10.2~focal-2_amd64.deb (--unpack):
     trying to overwrite '/opt/wine-staging/bin/wine', which is also in package wine-staging-i386:i386 10.2~focal-2
    dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
    Errors were encountered while processing:
     /var/cache/apt/archives/wine-staging-amd64_10.2~focal-2_amd64.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    

    Any idea on how to remove Wine manually, bypassing apt?

      • catloaf@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        I’m not sure I’d recommend that. Seems like it’d result in more breakage from mismatched architecture files.

        • ryannathans@aussie.zone
          link
          fedilink
          arrow-up
          1
          ·
          1 day ago

          Probably but it’s fucked anyway and now you can at least replace it with another wine or wait till it’s fixed tomorrow