• Status Closed
  • Percent Complete
  • Task Type Bug Report
  • Category Packages
  • Assigned To
    Erich Eckner
  • Operating System
  • Severity High
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Archlinux32
Opened by Jeff Hodd - 10.12.2017
Last edited by Erich Eckner - 17.12.2017

FS#19 - [wine-staging] PKGBUILD does not include 'provides=("wine=2.21")'

The current build of wine-staging (2.21) in the community repository has no ‘provides’ tag for wine, even though wine-staging includes wine-2.21 in its entirety. This causes massive conflicts when installing wine-staging and any package with a wine dependency. Literally every file in the wine package conflicts with the identical file found in wine-staging. Personally, I’ve had to provide my users with a fixed version of wine-staging via my own repository positioned before the community repository setting in pacman.conf in order to avoid this conflict - something I’d rather not do.

Closed by  Erich Eckner
17.12.2017 16:24
Reason for closing:  Fixed
Erich Eckner commented on 16.12.2017 20:17

hmm, this is strange: The source says, it should "provide=(wine=2.21)" but the binary package does not. I'll schedule a rebuild and watch if it does the right thing now.

Erich Eckner commented on 16.12.2017 20:21

found the issue, I'll fix it ...

Erich Eckner commented on 16.12.2017 21:26

ok, wine-staging in community-staging works, but unfortunately, there are some (probably unrelated) broken packages, which prevent wine-staging from being moved to community-testing and community thereafter :-/

Erich Eckner commented on 17.12.2017 08:05

I force-moved wine-staging and wine-staging-nine to [community] can you have a quick glance if it works (or if it misses some libraries which are still in testing or staging)?

Jeff Hodd commented on 17.12.2017 14:51

Absolutely, give me a bit to set it up and I'll let you know asap.

Jeff Hodd commented on 17.12.2017 14:57

It looks like your community conflict may be due to a mismatch in the versions of wine. wine-staging-2.21 provides wine-2.21 and you already have wine-2.22 pushed to community. I think if you update wine-staging to 2.22, your conflict will go away.

On my end, everything's installing as expected. wine-staging is pushing out the wine installation as it should - no conflicts. Looks good.

Jeff Hodd commented on 17.12.2017 15:49

Ok. Reordered my repositories and ran the package installation portion of an archiso run on my distro and everything is good.

Thanks for the fix, Erich.

Erich Eckner commented on 17.12.2017 16:23

um, the upstream versions of wine are:
wine 3.0rc2-1
wine-staging 2.21-1
wine-staging-nine 2.21-1

our wine-2.22-1 is in fact _outdated_ (with respect to upstream), the current one is in community-testing, currently.
The "conflicts" is w/o versions, so it should work. The "provides" correctly has verions.


Available keyboard shortcuts


Task Details

Task Editing