From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] MISSING: MesaLib-devel-19.2.1_1
Date: Thu, 17 Oct 2019 00:34:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15544@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
New issue by kyunal on void-packages repository
https://github.com/void-linux/void-packages/issues/15544
Description:
### System
* xuname:
MISSING: MesaLib-devel-19.2.1_1
Transaction aborted due to unresolved dependencies.
Void 5.3.6_1 x86_64 AuthenticAMD uptodate rrmFFFF
* package:
MesaLib-devel-19.2.1_1
### Expected behavior
Attempting to upgrade my system as usual.
I should be able to do `xbps-install -Syu` just fine.
### Actual behavior
`MISSING: MesaLib-devel-19.2.1_1
Transaction aborted due to unresolved dependencies.`
### Steps to reproduce the behavior
I suppose having an old version of it installed, then trying to upgrade. This could also be caused due to the inconsistency of versions across `current` and `multilib`. Please check the last note of this issue for more information.
### Further information
[Here's](https://pastebin.com/z31LLu78) the output of `xbps-install -Svud`
Also, `xbps-query -Rs MesaLib-devel` reports that the version found is 19.1.7_3. However, `MesaLib-devel-32bit` is version 19.2.1_1 . This is rather confusing.
next reply other threads:[~2019-10-16 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 22:34 voidlinux-github [this message]
2019-10-16 23:08 ` voidlinux-github
2019-10-17 8:38 ` voidlinux-github
2019-10-17 8:38 ` [ISSUE] [CLOSED] " voidlinux-github
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-15544@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).