From emerge.log: 1219581248: === (71 of 356) Post-Build Cleaning (sys-libs/ncurses-5.6-r2::/usr/portage/sys-libs/ncurses/ncurses-5.6-r2.ebuild) 1219581248: ::: completed emerge (71 of 356) sys-libs/ncurses-5.6-r2 to / 1219581248: >>> emerge (72 of 356) media-sound/lame-3.98 to / 1219581249: >>> emerge (73 of 356) sys-libs/gpm-1.20.5 to / 1219581249: === (72 of 356) Cleaning (media-sound/lame-3.98::/usr/portage/media-sound/lame/lame-3.98.ebuild) 1219581249: === (72 of 356) Compiling/Merging (media-sound/lame-3.98::/usr/portage/media-sound/lame/lame-3.98.ebuild) 1219581250: === (73 of 356) Cleaning (sys-libs/gpm-1.20.5::/usr/portage/sys-libs/gpm/gpm-1.20.5.ebuild) 1219581250: === (73 of 356) Compiling/Merging (sys-libs/gpm-1.20.5::/usr/portage/sys-libs/gpm/gpm-1.20.5.ebuild) 1219581269: === (73 of 356) Merging (sys-libs/gpm-1.20.5::/usr/portage/sys-libs/gpm/gpm-1.20.5.ebuild) 1219581274: *** terminating. 1219581275: Started emerge on: Aug 24, 2008 05:34:35 It never really said "completed" for gpm. I think it aborted the overall update because of failure of some other package. The log file of gpm from this time doesn't have any failure in it. What I noticed is that second gpm merge failed with collisions because the files which gpm merged at 05:34:35 did not belong to any installed package. 'genlop -t gpm' (I think it searches for 'completed' in emerge.log) shows that gpm wasn't merged. The timestamps on the merged files match with 05:34. One thing about collision protect: Can we list the package ("unknown" if the package is not installed) which the colliding files belong to?
Portage 2.2_rc8 (default-linux/x86/2007.0, gcc-4.3.1, glibc-2.8_p20080602-r0, 2.6.26.3 i686)
Please re-open if the problem still exists. (In reply to comment #0) > One thing about collision protect: Can we list the package ("unknown" if the > package is not installed) which the colliding files belong to? That was bug #153282.
