From: camthesaxman <camthesaxman@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] wine-32bit still reports version 8.3, even though 8.7 is supposedly installed
Date: Thu, 04 May 2023 05:51:50 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43740@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
New issue by camthesaxman on void-packages repository
https://github.com/void-linux/void-packages/issues/43740
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.15_1 x86_64 GenuineIntel notuptodate hold rrrmDFFFFFF
### Package(s) Affected
wine-32bit-8.7_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
wine and wine-32bit are both version 8.7_1, so `wine --version` and `wine64 --version` should both report version 8.7. Because of this, I cannot run winecfg or any programs in wine. The following error appears.
```
wine client error:0: version mismatch 762/761.
Your wine binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?
```
### Actual behaviour
`wine --version` (the 32-bit one) reports `wine-8.3` even though I have version 8.7_1 installed. `wine64 --version` does in fact report `wine-8.7`.
### Steps to reproduce
1. Remove both the wine and wine-32bit packages if installed. `xbps-remove wine wine-32bit`
2. Install them again. `xbps-install -S` followed by `xbps-install wine wine-32bit`
3. Attempt to run `winecfg`. You cannot due to a version mismatch.
4. Run `wine --version` and `wine64 --version`. The versions are different somehow.
next reply other threads:[~2023-05-04 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 3:51 camthesaxman [this message]
2023-05-04 3:59 ` classabbyamp
2023-05-04 5:13 ` camthesaxman
2023-05-04 5:13 ` [ISSUE] [CLOSED] " camthesaxman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43740@inbox.vuxu.org \
--to=camthesaxman@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).