> Here /usr/lib is a symlink to /usr/lib64
Now that you mention it: /usr/lib is supposed to be a symlink to
/usr/lib64 on my workstation too (like it is on all my other machines).
But it's not. Seems like something went wrong during installation. Maybe
a bad stage3 image. I created the symlink man
On 03/12/2012 01:23:21 PM, Michael Hampicke wrote:
> man qfile and look at the section on finding orphan files.
>
> Emerge portage-utils if you don't have qfile.
I just ran
# find /usr/lib* -type f -print0 | xargs -0 qfile -o | more
an was suprised how much orphans there are, already excluding
On Mon, Mar 12, 2012 at 1:53 AM, Helmut Jarausch
wrote:
> Hi,
>
> even the most recent portage 2.2.0_alpha90 has difficulties handling
> @preserved-rebuild especially after many binary emerge operations.
> It tries to re-emerge the same packages again and again.
> As a last resort I have to remov
> man qfile and look at the section on finding orphan files.
>
> Emerge portage-utils if you don't have qfile.
I just ran
# find /usr/lib* -type f -print0 | xargs -0 qfile -o | more
an was suprised how much orphans there are, already excluding the python
and perl stuff.
Here's some suprising st
On Mon, 12 Mar 2012 09:53:29 +0100, Helmut Jarausch wrote:
> Is there an elegant way to find these old libraries? (Removing them
> would alert revdep-rebuild afterwards).
man qfile and look at the section on finding orphan files.
Emerge portage-utils if you don't have qfile.
--
Neil Bothwic
Hi,
even the most recent portage 2.2.0_alpha90 has difficulties handling
@preserved-rebuild especially after many binary emerge operations.
It tries to re-emerge the same packages again and again.
As a last resort I have to remove
/var/lib/portage/preserved_libs_registry.
But after that the
6 matches
Mail list logo
