I was updating system. vmware-modules-1.0.0.15-r1 was blovked by earlier version, so I unmerged the old version. Now the new version fails with file collision: >>> Completed installing vmware-modules-1.0.0.15-r1 into /var/tmp/portage/vmware-modules-1.0.0.15-r1/image/ man: strip: x86_64-pc-linux-gnu-strip --strip-unneeded * checking 3 files for package collisions existing file /lib/modules/2.6.18-gentoo-r3/misc/vmmon.ko is not owned by this package existing file /lib/modules/2.6.18-gentoo-r3/misc/vmnet.ko is not owned by this package * spent 0.0422749519348 seconds checking for file collisions * This package is blocked because it wants to overwrite * files belonging to other packages (see messages above). * If you have no clue what this is all about report it * as a bug for this package on http://bugs.gentoo.org package app-emulation/vmware-modules-1.0.0.15-r1 NOT merged 1. Why emerge didn't remove *.ko files when I unmerged old vmware-modules? Is it ok? 2. If above is ok, maybe the ebuild should remove them in postrm() or something?
Just disable collision-protect temporarily, or delete the files, or use COLLISION_IGNORE="/lib/modules" - see man make.conf. Nothing that could be fixed in the ebuild, every external kernel module behaves the same way due to CONFIG_PROTECT *** This bug has been marked as a duplicate of 103100 ***
