From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [SOLVED] Re: [gentoo-user] sys-fs/-MERGING-static-dev installed but unable to find it
Date: Mon, 14 Sep 2015 00:34:51 -0500 [thread overview]
Message-ID: <55F65C7B.6090608@gmail.com> (raw)
In-Reply-To: <20150914071411.40174343@hal9000.localdomain>
wabenbau@gmail.com wrote:
> wraeth <wraeth@wraeth.id.au> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On 14/09/15 13:46, Dale wrote:
>>> 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??
>> I'm not certain, but I believe the -MERGING-* files are left over from
>> an interrupted Install phase. Dr. Google suggests manually removing
>> [1,2] and while I did come across this many moons ago, I can't recall
>> how I dealt with it myself.
>>
>> 1:
>> http://negativesum.net/tech/linux/gentoo/log/fixing-portage-when-it-has-
>> wedged-a-package-as-merging
>> 2: https://forums.gentoo.org/viewtopic-t-882687.html
> @Dale
>
> Have you tried to install it again? If that works, you can maybe remove
> it afterwards.
>
> --
> Regards
> wabe
>
>
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. ;-)
Thanks all.
Dale
:-) :-)
next prev parent reply other threads:[~2015-09-14 5:35 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 ` Dale [this message]
2015-09-14 5:50 ` [SOLVED] " 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=55F65C7B.6090608@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