Void-packages: Can't upgrade WINE to v5.19_1

Created on 11 Oct 2020  路  7Comments  路  Source: void-linux/void-packages

System

  • xuname:
    Void 5.8.13_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFF
  • package:
    wine-common

Expected behavior

Should get upgraded along with all other WINE components to 5.19_1

Actual behavior

MISSING: wine-common>=5.19_1
Transaction aborted due to unresolved dependencies.

Steps to reproduce the behavior

Just a simple system upgrade

Considering that wine-common is a subpackage of wine by the looks of it, I'm wondering if it's a repo bug or something on my side since they should all remain in sync...

Most helpful comment

This is a consequence of a large update that is being processed and holding back the availability of the new wine-common. It should be resolved soon.

All 7 comments

I can reproduce.

The problem lies in the fact the repo data hasn't been updated yet; wine is still on version 5.18, while wine-32bit is on version 5.19.

Indeed, just checked with a local build with ./xbps-src, seems to be a repo update problem

$ xuname 
Void 5.8.14_1 x86_64-musl GenuineIntel uptodate rFFFFF

Can't reproduce.

@ev-ermakov Could you please run the following?

$ xbps-query -R wine | grep pkgver && xbps-query -R wine-32bit | grep pkgver

The 64-bit version of wine installs for me, too; unfortunately, the 32-bit version doesn't. The repository data for the 64-bit version is outdated, as of the time of my writing.

Also, please bear in mind you are on the musl libc version of the repos.

@sug0, Yeah, there is only 32-bit version:

$ xbps-query -R wine | grep pkgver && xbps-query -R wine-32bit | grep pkgver
pkgver: wine-5.19_1

This is a consequence of a large update that is being processed and holding back the availability of the new wine-common. It should be resolved soon.

Solved.

Was this page helpful?
0 / 5 - 0 ratings