From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] wine-devel-32bit install unresolved dependencies
Date: Sat, 02 Jan 2021 01:39:26 +0100 [thread overview]
Message-ID: <20210102003926.95R-7B-xgcho5Oq9QM8c3eqJfa5nc5l14BPnahByb6A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27572@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Closed issue by floyza on void-packages repository
https://github.com/void-linux/void-packages/issues/27572
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.9.16_1 x86_64 AuthenticAMD uptodate rrrmFFFFF
* package:
wine-devel-32bit
On running `sudo xbps-install -Su wine-devel-32bit`, it fails to install with this error message:
```
MISSING: libwine-32bit-5.22_1
Transaction aborted due to unresolved dependencies.
```
It seems that the dependency was not updated to `libwine-32bit-6.0rc4_1`?
prev parent reply other threads:[~2021-01-02 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 3:57 [ISSUE] " floyza
2021-01-02 0:39 ` ericonr
2021-01-02 0:39 ` ericonr [this message]
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=20210102003926.95R-7B-xgcho5Oq9QM8c3eqJfa5nc5l14BPnahByb6A@z \
--to=ericonr@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).