public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <wabenbau@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sys-fs/-MERGING-static-dev installed but unable to find it
Date: Mon, 14 Sep 2015 06:36:33 +0200	[thread overview]
Message-ID: <20150914063633.72f15f31@hal9000.localdomain> (raw)
In-Reply-To: <55F642F9.5020402@gmail.com>

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


  reply	other threads:[~2015-09-14  4:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  3:46 [gentoo-user] sys-fs/-MERGING-static-dev installed but unable to find it Dale
2015-09-14  4:36 ` wabenbau [this message]
2015-09-14  5:00   ` wabenbau
2015-09-14  5:21     ` Dale
2015-09-14  5:14   ` Dale
2015-09-14  7:41   ` Neil Bothwick
2015-09-14  5:07 ` wraeth
2015-09-14  5:14   ` wabenbau
2015-09-14  5:34     ` [SOLVED] " Dale
2015-09-14  5:50       ` wraeth
2015-09-14  8:37         ` Peter Humphrey
2015-09-14  8:45         ` Dale
2015-09-14  9:09           ` wraeth
2015-09-14  9:16             ` Dale
2015-09-14  5:28   ` Dale
2015-09-14  9:28 ` Marc Joliet
2015-09-14 11:24   ` Dale
2015-09-14 14:56   ` Peter Humphrey
2015-09-14 15:38     ` [gentoo-user] " james
2015-09-14 20:41     ` [gentoo-user] " Neil Bothwick
2015-09-15  8:50       ` Peter Humphrey
2015-09-15  9:07         ` wraeth
2015-09-15  9:30         ` Neil Bothwick
2015-09-15 12:30           ` Peter Humphrey
2015-09-15  9:05     ` Dale
2015-09-15 12:29       ` Peter Humphrey

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=20150914063633.72f15f31@hal9000.localdomain \
    --to=wabenbau@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