public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [SOLVED] Re: [gentoo-user] sys-fs/-MERGING-static-dev installed but unable to find it
Date: Mon, 14 Sep 2015 03:45:44 -0500	[thread overview]
Message-ID: <55F68938.5080602@gmail.com> (raw)
In-Reply-To: <55F6601C.5070302@wraeth.id.au>

wraeth wrote:
> On 14/09/15 15:34, Dale wrote:
> > Well, I'd be chicken to have two packages dealing with /dev at the
> > same time, although portage says it is not a blocker.
>
> > For future reference, I went and dug in this path:
>
> > /var/db/pkg/sys-fs
>
> > It turned out it was just a empty directory and deleting it cleared
> > it up.  Since it was empty, I guess that was safe enough.  If
> > anything was in it, then I'd be wanting to make sure it was safe to
> > remove first.
>
> > So, it's fixed.  I get a clean eix run and if its happy, I'm happy.
> > ;-)
>
> Granted I don't know your setup, but having nothing installed from
> sys-fs/* seems a little odd to me. For example, I have the following
> packages installed from the sys-fs category:
>
> eix -cI\#C sys-fs
> sys-fs/btrfs-progs
> sys-fs/cryptsetup
> sys-fs/e2fsprogs
> sys-fs/fuse
> sys-fs/lvm2
> sys-fs/ntfs3g
> sys-fs/udev
> sys-fs/udev-init-scripts
> sys-fs/udisks
>
> Accordingly, I have the following in /var/db/pkg/sys-fs/
>
> ls -lhn /var/db/pkg/sys-fs
> total 0
> drwxr-xr-x 1 0 0 534 2015-09-14 09:51 btrfs-progs-4.2
> drwxr-xr-x 1 0 0 520 2015-09-10 11:14 cryptsetup-1.6.8
> drwxr-xr-x 1 0 0 494 2015-09-10 12:56 e2fsprogs-1.42.13
> drwxr-xr-x 1 0 0 494 2015-09-10 18:29 fuse-2.9.4
> drwxr-xr-x 1 0 0 526 2015-09-10 21:41 lvm2-2.02.116
> drwxr-xr-x 1 0 0 520 2015-09-10 11:13 ntfs3g-2015.3.14
> drwxr-xr-x 1 0 0 538 2015-09-10 22:21 udev-225
> drwxr-xr-x 1 0 0 464 2015-09-10 19:02 udev-init-scripts-30
> drwxr-xr-x 1 0 0 512 2015-09-11 03:26 udisks-2.1.6
>
> If you legitimately don't have anything installed from the sys-fs
> category, then all should be safe I guess; but if you do, then other
> mysteries may be afoot...
>


I have this:

root@fireball / # equery list sys-fs/*
 * Searching for * in sys-fs ...
[IP-] [  ] sys-fs/dfc-3.0.5-r1:0
[IP-] [  ] sys-fs/dosfstools-3.0.28:0
[IP-] [  ] sys-fs/e2fsprogs-1.42.13:0
[IP-] [  ] sys-fs/eudev-3.1.2-r10:0
[IP-] [  ] sys-fs/fuse-2.9.4:0
[IP-] [  ] sys-fs/lvm2-2.02.110:0
[IP-] [  ] sys-fs/mdadm-3.3.1-r2:0
[IP-] [  ] sys-fs/mtools-4.0.15:0
[IP-] [  ] sys-fs/ntfs3g-2014.2.15-r1:0
[IP-] [  ] sys-fs/reiser4progs-1.0.9:0
[IP-] [  ] sys-fs/reiserfsprogs-3.6.24:0
[IP-] [  ] sys-fs/shake-0.999:0
[IP-] [  ] sys-fs/treesize-0.54.1:0
[IP-] [  ] sys-fs/udev-init-scripts-27:0
[IP-] [  ] sys-fs/udisks-2.1.4:2
root@fireball / #  

I use eudev to manage /dev.  Since I know I already have software to
manage that, I didn't want to emerge that failed one since it could
clash with what I already have installed.  That said, portage didn't
show it as a blocker or anything.  I likely could have emerged it, then
unmerged it and not cause a problem.  I was just to chicken to do it is
all. 

In my search, I was searching for static-dev so it would only show
matches to that and not the other packages in sys-fs.  If I had searched
for sys-fs/* then it would have shown what was installed in that category. 

The biggest thing, I just didn't want to screw something up and google
wasn't returning anything when I searched.  No clue why it didn't tho. 
It's rare that google shows no matches.  It usually finds something even
if it is off the mark a bit. 

Dale

:-)  :-) 



  parent reply	other threads:[~2015-09-14  8:45 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
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 [this message]
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=55F68938.5080602@gmail.com \
    --to=rdalek1967@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