From: Steve Litt <littdom@gmail.com>
To: voidlinux <voidlinux@googlegroups.com>
Subject: webkitgtk-2.4.11_6: broken, unresolvable shlib `libicudata.so.62'
Date: Thu, 1 Nov 2018 02:21:53 -0700 (PDT) [thread overview]
Message-ID: <818cf8a2-e2ce-4efd-ac28-3fe1dd219e5d@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1430 bytes --]
Tonight, when I tried xbps-install Su , I got the following errors:
[root@mydesk ~]# xbps-install -u
webkitgtk-2.4.11_6: broken, unresolvable shlib `libicudata.so.62'
webkitgtk2-2.4.11_6: broken, unresolvable shlib `libicudata.so.62'
webkitgtk-2.4.11_6: broken, unresolvable shlib `libicui18n.so.62'
webkitgtk2-2.4.11_6: broken, unresolvable shlib `libicui18n.so.62'
webkitgtk-2.4.11_6: broken, unresolvable shlib `libicuuc.so.62'
webkitgtk2-2.4.11_6: broken, unresolvable shlib `libicuuc.so.62'
Transaction aborted due to unresolved shlibs.
[root@mydesk ~]#
https://build.voidlinux.eu/waterfall shows no problem.
[root@mydesk ~]# uname -a
Linux mydesk 4.18.16_1 #1 SMP PREEMPT Sun Oct 21 03:00:36 UTC 2018 x86_64
GNU/Linux
[root@mydesk ~]#
What can I do to get past this. De-installing webkitgtk and webkitgtk2
would require removal of 10 or more often used apps. I tried changing my
repos, but got the same symptom.
Thanks,
SteveT
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/818cf8a2-e2ce-4efd-ac28-3fe1dd219e5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2128 bytes --]
next reply other threads:[~2018-11-01 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 9:21 Steve Litt [this message]
2018-11-01 19:34 ` Leah Neukirchen
2018-11-02 17:59 ` MJ
2018-11-25 3:00 ` Nashat Samir
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=818cf8a2-e2ce-4efd-ac28-3fe1dd219e5d@googlegroups.com \
--to=littdom@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).