Re: [gentoo-user] sys-fs/-MERGING-static-dev installed but unable to find it

[Dale <rdalek1967@gmail.com>]

wabenbau@gmail.com wrote:
> Dale <rdalek1967@gmail.com> wrote:
>
>> Howdy,
>>
>> I ran eix-test-obsolete and in the output, I get the following:
>>
>>
>> The following installed packages are not in the database:
>>
>> sys-fs/-MERGING-static-dev
>> --
>>
>> Equery gives me this:
>>
>> root@fireball / # equery list *static-dev*
>>  * Searching for *static-dev* ...
>> !!! No installed packages matching '*static-dev*'
>> root@fireball / # 
>>
>>
>>
>> Other tools report this:
>>
>>
>>
>> root@fireball / # emerge -s static-dev
>>  
>> [ Results for search key : static-dev ]
>> Searching...
>>
>> *  sys-fs/static-dev
>>       Latest version available: 0.1
>>       Latest version installed: [ Not Installed ]
>>       Size of files: 0 KiB
>>       Homepage:      https://bugs.gentoo.org/107875
>>       Description:   A skeleton, statically managed /dev
>>       License:       GPL-2
>>
>> [ Applications found : 1 ]
>>
>> root@fireball / # eix static-dev
>> * sys-fs/static-dev
>>      Available versions:  0.1
>>      Homepage:            https://bugs.gentoo.org/107875
>>      Description:         A skeleton, statically managed /dev
>>
>> root@fireball / #
>>
>>
>>
>> So, it's installed but I can't find it to remove it.  What the heck is
>> this about?  Anyone else ever run into this?  Is there a way to "find"
>> it??  Can I remove it somehow??
>>
>> Thanks.
>>
>> Dale
>>
>> :-)  :-) 
>>
> It's also installed on my system and probably it's a forgotten relict from 
> ancient times (my last gentoo installation on this machine was in 2007).
>
> To be honest, I never ran eix-test-obsolete. My system is running fine and
> atm I don't have much time. So I will leave it as it is.
>
> Maybe the static dev is useful in the case that udev refuses to work for 
> any reason. :-)
>
> --
> Regards
> wabe
>
>


What gets me, that MERGING is in all caps.  I don't recall ever seeing a
package name with caps like that.  To me, it looks like something was
being installed/upgraded and during the process some cruft got left
behind by portage.  Now I don't know that to be true but I'm grasping at
straws here.  I think I built this rig about 2011 or 2012.  I could dig
out the invoices to be sure.  Anyway, mines not as old a install as
yours but it has been around for a while. 

That has been there for a while and everything is working fine, even
rebooting.  Thing is, it bugs me that it is there and I don't know what
exactly it is or where it came from.  Also, that I can't figure out how
to clean it up either.  o_O  I mostly want to clean it up. 

Maybe someone else has ran into this and has a clue, or a 2 x 4.  ;-) 

Dale

:-)  :-)