From: Logen Kain <walach.o...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: unresolved shlibs
Date: Sat, 7 Mar 2015 00:45:12 -0800 (PST) [thread overview]
Message-ID: <9e159951-dfe9-44ab-8794-0a1be2b8d736@googlegroups.com> (raw)
In-Reply-To: <47fd85ef-74cd-448b-9240-218936050ddd@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 376 bytes --]
Everything is working fine now. I don't believe I've ever run xbps-pkgdb,
and just so you are aware, I did NOT use your solution, all I did was run
a sync and upgrade. The changes you have made seemed to have fixed
everything without my intervention.
I was able to update everything, and ran the update check again for good
measure. No shlib errors anymore.
[-- Attachment #1.2: Type: text/html, Size: 420 bytes --]
next prev parent reply other threads:[~2015-03-07 8:45 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
2015-03-07 8:45 ` Logen Kain [this message]
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=9e159951-dfe9-44ab-8794-0a1be2b8d736@googlegroups.com \
--to="walach.o..."@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).