Void Linux discussion
 help / color / mirror / Atom feed
From: MJ <5565millerj@gmail.com>
To: voidlinux <voidlinux@googlegroups.com>
Subject: Re: webkitgtk-2.4.11_6: broken, unresolvable shlib `libicudata.so.62'
Date: Fri, 2 Nov 2018 10:59:51 -0700 (PDT)	[thread overview]
Message-ID: <6413a611-2330-426a-977c-9c2e643d5b4a@googlegroups.com> (raw)
In-Reply-To: <818cf8a2-e2ce-4efd-ac28-3fe1dd219e5d@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 2555 bytes --]

On Thursday, November 1, 2018 at 4:21:53 AM UTC-5, Steve Litt wrote:
>
> 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
>
> I had the same issue except I only had one utility that depended on 
webkitgtk2. I removed that package (yad) in order to uninstall gtkwebkit2 
so as to be able to do my system updates. Note that webkit2gtk is present 
on my system: I'm not sure what is the relationship between webkit2gtk and 
webkitgtk2, but for purposes of the package I removed, it is apparently not 
a drop-in replacement. The system now refuses to reinstall yad: "MISSING: 
webkitgtk2>=2.4.8_2 Transaction aborted due to unresolved dependencies."

Seems kind of strange that a package that cannot be installed due to 
dependency on a recently-removed package would even remain in the 
repository. So what do I have to do to get yad back? Compile from source 
and see whether I can stipulate that it use webkit2gtk instead of 
webkitgtk2?

Btw, what became of https://forum.voidlinux.org/? It's been unreachable for 
me for a couple days now. I know there had been some talk about shutting it 
down: did that finally happen? Thanks

-- 
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/6413a611-2330-426a-977c-9c2e643d5b4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 3854 bytes --]

  parent reply	other threads:[~2018-11-02 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  9:21 Steve Litt
2018-11-01 19:34 ` Leah Neukirchen
2018-11-02 17:59 ` MJ [this message]
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=6413a611-2330-426a-977c-9c2e643d5b4a@googlegroups.com \
    --to=5565millerj@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).