From: CJoeB <colleen.beamer@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Issue with e2fsprogs
Date: Mon, 23 Feb 2009 00:12:20 -0500 [thread overview]
Message-ID: <49A23034.7080705@gmail.com> (raw)
In-Reply-To: <20090223084408.0f9514cb@coercion>
Mike Kazantsev wrote:
> On Sun, 22 Feb 2009 17:32:57 -0500
> CJoeB <colleen.beamer@gmail.com> wrote:
>
>
>> On step 3, e2fsprogs-libs emerged fine, but at the end of the emerge of
>> e2fsprogs, the emerge bombed and I got a message saying that e2progs was
>> not merged due to file collisions.
>>
>
> You can use 'equery b <PATH>' (app-portage/gentoolkit) to determine
> which package owns the offending files, then either unmerge it or just
> set "FEATURES=-collision-protect" to force installation despite
> collisions.
>
>
The "FEATURES=collision-protect" didn't work. I assume I entered the
command correctly because protage didn't give me grief.
I have no idea how to determine what is the offending package because I
don't know what the path is where the offending package is. This is the
message I get at the end when emerge bombs:
Package 'sys-fs/e2fsprogs-1.40.9' NOT merged due to file collisions.
* If necessary, refer to your elog messages for the whole content of the
* above message.
I've looked at emerge.log, but nothing sheds any light. And if this
isn't where I'm supposed to look, I'm not sure where I should be looking.
Regards,
Colleen
--
Registered Linux User #411143 with the Linux Counter, http://counter.li.org
next prev parent reply other threads:[~2009-02-23 5:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 22:32 [gentoo-user] Issue with e2fsprogs CJoeB
2009-02-23 3:44 ` Mike Kazantsev
2009-02-23 5:12 ` CJoeB [this message]
2009-02-23 5:23 ` Volker Armin Hemmann
2009-02-23 7:42 ` AllenJB
2009-02-23 14:22 ` CJoeB
2009-02-23 14:45 ` AllenJB
2009-02-24 0:37 ` Neil Bothwick
2009-02-24 3:00 ` CJoeB
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=49A23034.7080705@gmail.com \
--to=colleen.beamer@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