From: Juan RP <xtr...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: unresolved shlibs
Date: Fri, 6 Mar 2015 23:25:26 -0800 (PST) [thread overview]
Message-ID: <47fd85ef-74cd-448b-9240-218936050ddd@googlegroups.com> (raw)
In-Reply-To: <b896d125-9045-40b2-a2dd-8db2f2b48245@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 547 bytes --]
Found another issue that has appeared for some people.
The xbps 0.44 shlib code skips packages that have the "transaction" obj set
to "remove". If you've been using
xbps for a while and never ran xbps-pkgdb(8) there could be some packages
with that obsolete obj.
Solution:
for f in $(xbps-query -s '' -p transaction|cut -d ':' -f1); do sudo
xbps-pkgdb $f; done
If this does not fix the unresolved shlib there's a pkg that is missing the
`shlib-provides` obj, submit a new issue
in the void-packages github repo.
Thanks.
[-- Attachment #1.2: Type: text/html, Size: 591 bytes --]
next prev parent reply other threads:[~2015-03-07 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 1:32 Logen Kain
2015-03-07 2:46 ` Logen Kain
2015-03-07 6:18 ` Juan RP
2015-03-07 7:25 ` Juan RP [this message]
2015-03-07 8:45 ` Logen Kain
2018-04-08 2:22 pastel raschke
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=47fd85ef-74cd-448b-9240-218936050ddd@googlegroups.com \
--to="xtr..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/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).