public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: wraeth <wraeth@wraeth.id.au>
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 15:50:20 +1000	[thread overview]
Message-ID: <55F6601C.5070302@wraeth.id.au> (raw)
In-Reply-To: <55F65C7B.6090608@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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...

- -- 
wraeth <wraeth@wraeth.id.au>
GnuPG Key: B2D9F759
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAlX2YBgACgkQXcRKerLZ91lp1QD/ZTJvDfpdti6HxdmZK9ecB0pD
qPFQSbc+P9iRIvwmYy8A/2bDtIy6CfAZ6ewpZg438y1lk4axUQ8U3VHjOx8CHzAq
=4w2J
-----END PGP SIGNATURE-----


  reply	other threads:[~2015-09-14  5:50 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 [this message]
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=55F6601C.5070302@wraeth.id.au \
    --to=wraeth@wraeth.id.au \
    --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