Apparently, though unproven, at 18:46 on Saturday 27 November 2010, Joseph did opine thusly:
> On 11/27/10 17:51, Adam Carter wrote: > >> * package sys-apps/portage-2.1.9.24 NOT merged > >> > >> * > >> * Detected file collision(s): > >> * > >> * /usr/bin/quickpkg > >> > >> Should I remove the quickpkg to install new portage or comment-out > >> "collision-protect" in make.conf? > >> > >> I just ran the same update (and it reported it was going ahead with the > > > >update despite the collision). Looks like quickpkg is now in portage; > > > ># qfile /usr/bin/quickpkg > >sys-apps/portage (/usr/bin/quickpkg) > > I just "--sync" and it stopping at the same place :-/ > Detected file collision(s): > /usr/bin/quickpkg You didn't do anything about the collision, so it's still happening. Read the portage man pages to gain an understanding of how portage works and what --sync updates (it will not fix your problem) Some package installed /usr/bin/quickpkg, now portage wants to install it. Presumably, the old package is now part of portage itself. Anyway, while that binary is there portage is not going to install itself. This is a good thing and you do not ever want to disable it. So sit quietly for a moment and figure out why you need to delete /usr/bin/quickpkg, then do so and emerge portage. This time it will work. -- alan dot mckinnon at gmail dot com
