From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: broken libraries but library-linking is consistent ;-)
Date: Wed, 14 Jun 2006 14:38:08 +0200 (CEST) [thread overview]
Message-ID: <41019.141.38.43.231.1150288688.squirrel@ulm114.server4you.de> (raw)
In-Reply-To: <60fece8f0606140524n2dfe5d72qa1965fd4314c00d0@mail.gmail.com>
>> according to revdep-rebuild, quite a few libraries on my system are
> broken.
>> But at the end of revdep-rebuild, it tells me, my system was consistent.
>
> This means the broken libraries don't belong to any package. Something
> touched/altered them (probably fix libtool script when updating gcc) so
> they
> had different mtime/md5sum than what was recorded in the package db. Such
> altered files are not unmerged. It's quite safe to delete them. I suppose
> you updated kde 3.4 to 3.5 and unmerged the old 3.4... as the kde
> configuration howto says, you can remove whole /usr/kde/3.4 dir (but look
> into there first and use common sense :) For that avifile stuff, I have no
> idea which package it came from, but probably you can remove it too (or is
> it something installed not from portage?)
>
>> I think some libraries are really broken, because the sound of my vlc
>> player stutters sometimes lately.
>
> I don't suppose it could have this effect. Broken linking usually means
> stuff won't run at all :)
>
> Caster
>
I am a Gnome-User ;-).
I will delete them now. I have only Netbeans installed, that ist not in
portage, and that ist installed by a user in the home directory.
So i think i can delete that.
Norman
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-06-14 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 12:24 [gentoo-user] Re: broken libraries but library-linking is consistent ;-) Caster
2006-06-14 12:38 ` Norman Rieß [this message]
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=41019.141.38.43.231.1150288688.squirrel@ulm114.server4you.de \
--to=norman@smash-net.org \
--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