Mike Kazantsev wrote: > On Sun, 22 Feb 2009 17:32:57 -0500 > CJoeB <[email protected]> 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
