From: "Sven Köhler" <skoehler@upb.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Revdep-rebuild reports kde breakage and then says its all okay; what's up with that
Date: Sun, 29 Oct 2006 18:45:12 +0100 [thread overview]
Message-ID: <ei2pb8$ec0$1@sea.gmane.org> (raw)
In-Reply-To: <9acccfe50610290745k4a658dc5k1d67db0f06482af0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
> 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.
Old *.la files are broken. They have not been unmerged. That's a known
bug, because some gentoo-tools have modified the files, and so they were
not unmerged.
Just delete them.
You can verify, that they don't belong to any installed package by using
"equery b <filename>"
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2006-10-29 18:18 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 ` Sven Köhler [this message]
2006-10-30 17:39 ` Mick
2006-10-30 17:50 ` Kevin O'Gorman
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='ei2pb8$ec0$1@sea.gmane.org' \
--to=skoehler@upb.de \
--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