From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Revdep-rebuild reports kde breakage and then says its all okay; what's up with that
Date: Mon, 30 Oct 2006 09:50:01 -0800 [thread overview]
Message-ID: <9acccfe50610300950g3fa268d4k4bb94482bb6b6bba@mail.gmail.com> (raw)
In-Reply-To: <200610301739.47167.michaelkintzios@gmail.com>
On 10/30/06, Mick <michaelkintzios@gmail.com> wrote:
> On Sunday 29 October 2006 15:45, Kevin O'Gorman wrote:
> > When I run revdep-rebuild, it reports a bunch (around 100) breakages
> > involving early kde *.la files, but then it reports that
> > Dynamic linking on your system is consistent... All done.
> >
> > These "broken" files are text, and say they're not to be deleted, but
> > equery can't find out for me what package, let alone version, they belong
> > to. Could it be that they are abandoned relic artifacts?
> > Should I just delete them anyway?
>
> Run emerge --deep -v -p to see if there's a couple of updated/removed apps
> that have left libs cruft behind and need to be removed. I can vaguely
> remember going through something like this a few months ago (about
> ImageMagick?), so if you do a gmane search you may find it - otherwise post
> back and I'll see if I can find it.
>
> HTH
I checked a number of them, and they were clearly orphans: the
libraries they were
associated with originally had ceased to exist, which makes sense because they
where also coordinated with KDE versions (3.2 and such) that I no longer have.
So I deleted the lot, and everything seems okay.
--
Kevin O'Gorman, PhD
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-30 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 15:45 [gentoo-user] Revdep-rebuild reports kde breakage and then says its all okay; what's up with that Kevin O'Gorman
2006-10-29 17:45 ` [gentoo-user] " Sven Köhler
2006-10-30 17:39 ` [gentoo-user] " Mick
2006-10-30 17:50 ` Kevin O'Gorman [this message]
2006-10-30 18:17 ` Alan McKinnon
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=9acccfe50610300950g3fa268d4k4bb94482bb6b6bba@mail.gmail.com \
--to=kogorman@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