From: Vile Ento <vile...@gmail.com>
To: voidlinux@googlegroups.com
Subject: update error on freshly installed o/s
Date: Tue, 31 Mar 2015 09:01:23 -0700 (PDT) [thread overview]
Message-ID: <fc5f4c4c-3b37-475a-b577-6ddd39034c3c@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1284 bytes --]
On a freshly installed void (using void-live-x86_64-latest.iso /
75ec1eeded4bdf16e046637e6f6e8da0) I selected 'local' as the source.
After installing and rebooting I ran '# xbps-install -Su' and got the
following errors:
ncurses-libs-5.9_13 breaks `bash-4.3.033_1' (needs `libncursesw.so.6', got
'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `less-471_1' (needs `libncursesw.so.6', got
'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `libedit-20141030.3.1_1' (needs
`libncursesw.so.6', got 'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `ncurses-5.9_9' (needs `libncursesw.so.6', got
'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `nvi-1.81.6_7' (needs `libncursesw.so.6', got
'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `procps-ng-3.3.10_2' (needs `libncursesw.so.6',
got 'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `psmisc-22.21_2' (needs `libncursesw.so.6', got
'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `readline-6.3.008_2' (needs `libncursesw.so.6',
got 'libncursesw.so.5')
ncurses-libs-5.9_13 breaks `util-linux-2.26_1' (needs `libncursesw.so.6',
got 'libncursesw.so.5')
Transaction aborted due to unresolved shlibs.
[*] Updating `http://repo.voidlinux.eu/current/x86_64-repodata' ...
What is the recommended way to resolve?
[-- Attachment #1.2: Type: text/html, Size: 1317 bytes --]
next reply other threads:[~2015-03-31 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 16:01 Vile Ento [this message]
2015-03-31 17:47 ` Duncan O
2015-03-31 18:13 ` Vile Ento
2015-04-30 13:49 ` siotorp
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=fc5f4c4c-3b37-475a-b577-6ddd39034c3c@googlegroups.com \
--to="vile..."@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).