* Detected file collision(s): * * /usr/bin/yacc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'dev-util/yacc-1.9.1-r6' NOT merged due to file collisions. If ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-developer_libressl-test_20180406-190612 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-util/yacc [ebuild N ] dev-util/yacc-1.9.1-r6
Created attachment 526846 [details] emerge-info.txt
Created attachment 526848 [details] dev-util:yacc-1.9.1-r6:20180408-081425.log
Created attachment 526850 [details] emerge-history.txt
Created attachment 526852 [details] etc.portage.tbz2
Created attachment 526854 [details] logs.tbz2
Hi Toralf I understand that the package you're trying to install collides with yacc but which one is it? Please let me know.
(In reply to Patrice Clement from comment #6) IMO exactly that's the portage. portage refuses to install although no package does claim the file.
sys-devel/bison (all versions) install the symlink in pkg_postinst (whence without taking ownership). Probably, this should better be done in src_install (so that ownership is taken), depending on a USE-flag whether the symlink should be generated (and in this case block dev-util/yacc).
Alright thanks Martin. I need to look into this issue further.
*** This bug has been marked as a duplicate of bug 90089 ***