updating tevent-0.9.8 to tevent-0.9.14 fails with file collision with sys-libs/talloc. Reproducible: Always Steps to Reproduce: 1.have sys-libs/tevent-0.9.8 and sys-libs/talloc-2.0.5 installed 2.emerge sys-libs/tevent-0.9.14 3. Actual Results: * Detected file collision(s): * * /usr/lib/python2.7/site-packages/talloc.so * /usr/share/man/man3/talloc.3.bz2 * /usr/include/pytalloc.h * /usr/lib/libtevent.so.0 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-libs/talloc-2.0.5 * /usr/include/pytalloc.h * /usr/lib/python2.7/site-packages/talloc.so * /usr/share/man/man3/talloc.3.bz2 * * Package 'sys-libs/tevent-0.9.14' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. Expected Results: Clean install. sys-libs/talloc-2.0.5 (/usr/lib/python2.7/site-packages/talloc.so) sys-libs/talloc-2.0.5 (/usr/share/man/man3/talloc.3.bz2) sys-libs/talloc-2.0.5 (/usr/include/pytalloc.h) sys-libs/tevent-0.9.8 (/usr/lib/libtevent.so.0.9.8)
Created attachment 288183 [details] sys-libs/tevent-0.9.14 build.log
Created attachment 288185 [details] emerge --info
I've just hitted this, let me find out what was the intention of tevent providing talloc.so
sys-libs/tevent needs to DEPEND on dev-util/pkgconfig to "detect" a working talloc, or otherwise it will try to build its own. I've fixed this in sys-libs/tevent-0.9.14
*** Bug 389247 has been marked as a duplicate of this bug. ***