From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Removing shared libraries
Date: Wed, 4 Feb 2009 13:28:51 -0600 [thread overview]
Message-ID: <58965d8a0902041128y4f55198al576d06e5bd6d843e@mail.gmail.com> (raw)
In-Reply-To: <47a330c50902041109s62e0a125r596503012fc7405d@mail.gmail.com>
On Wed, Feb 4, 2009 at 1:09 PM, Damian <damian.only@gmail.com> wrote:
> Hi,
>
> After I ran reconcilio (I guess revdep-rebuild will yield a similar
> output) I got the following message:
> The following broken files are not owned by any installed package:
> /usr/lib64/kde4/plasma_applet_sysmoni_nvidia.so (requires libplasma.so.2)
> /usr/lib64/kde4/plasma_applet_sysmoni_portage.so (requires libplasma.so.2)
> /usr/lib64/kde4/plasma_applet_sysmoni_ram.so (requires libplasma.so.2)
> /usr/lib64/kde4/plasma_applet_sysmoni_sys.so (requires libplasma.so.2)
> /usr/lib64/kde4/plasma_applet_sysmoni_top.so (requires libplasma.so.2)
> /usr/lib64/kde4/plasma_yawp.so (requires libplasma.so.2)
> /usr/lib64/kde4/sysmoni_engine.so (requires libplasma.so.2)
> /usr/lib64/libsysmoni.so (requires libplasma.so.2)
>
> Those shared objects were installed when I manually compiled plasmoids
> some time ago (using kde 4.1, now I have kde 4.2). So my question is
> if I can safely remove those files without beaking anything. I think
> it is safe but I want to be cautious.
I think so. I always manually delete when they show up like that and
nothing has broken that I know of. For some reason they don't always
get removed during unmerge or upgrade.
next prev parent reply other threads:[~2009-02-04 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 19:09 [gentoo-user] Removing shared libraries Damian
2009-02-04 19:28 ` Paul Hartman [this message]
2009-02-04 19:46 ` Jesús Guerrero
2009-02-05 11:54 ` Damian
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=58965d8a0902041128y4f55198al576d06e5bd6d843e@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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