From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Can't upgrade WINE to v5.19_1
Date: Mon, 12 Oct 2020 15:08:56 +0200 [thread overview]
Message-ID: <20201012130856.h5GWM-s2esfcqvaCfn-s5SOPzbJ5YdZIlD7PTX5sG0M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25523@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Closed issue by chilledfrogs on void-packages repository
https://github.com/void-linux/void-packages/issues/25523
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.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...
prev parent reply other threads:[~2020-10-12 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 13:54 [ISSUE] " chilledfrogs
2020-10-11 15:19 ` sug0
2020-10-11 15:20 ` sug0
2020-10-11 16:29 ` chilledfrogs
2020-10-11 18:34 ` ev-ermakov
2020-10-11 18:41 ` sug0
2020-10-11 18:42 ` sug0
2020-10-11 18:47 ` ev-ermakov
2020-10-12 11:08 ` ahesford
2020-10-12 13:03 ` sug0
2020-10-12 13:08 ` ahesford [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=20201012130856.h5GWM-s2esfcqvaCfn-s5SOPzbJ5YdZIlD7PTX5sG0M@z \
--to=ahesford@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).