The message below basically says don't file a bug unless I understand the message. I understand the message, so I'm filing a bug. As far as I can tell, this package is conflicting with itself. I can't simply ignore the collision since it causes the emerge to fail. ---- >>> Messages generated by process 7003 on 2014-06-27 19:28:21 EDT for package sys-kernel/aufs-sources-3.12.20: ERROR: preinst This package will overwrite one or more files that may belong to other packages (see list below). You can use a command such as `portageq owners / <filename>` to identify the installed package that owns a file. If portageq reports that only one package owns a file then do NOT file a bug report. A bug report is only useful if it identifies at least two or more packages that are known to install the same file(s). If a collision occurs and you can not explain where the file came from then you should simply ignore the collision since there is not enough information to determine if a real problem exists. Please do NOT file a bug report at http://bugs.gentoo.org unless you report exactly which two packages install the same file(s). See http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to solve the problem. And once again, please do NOT file a bug report unless you have completely understood the above message. package sys-kernel/aufs-sources-3.12.20 NOT merged Detected file collision(s): /usr/src/linux-3.12.20-aufs/Makefile /usr/src/linux-3.12.20-aufs/Kbuild /usr/src/linux-3.12.20-aufs/patches.txt /usr/src/linux-3.12.20-aufs/README /usr/src/linux-3.12.20-aufs/Kconfig /usr/src/linux-3.12.20-aufs/.gitignore /usr/src/linux-3.12.20-aufs/MAINTAINERS ... /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/hweight.h /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/const_hweight.h /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/builtin-ffs.h /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/builtin-fls.h /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/non-atomic.h /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/arch_hweight.h /usr/share/doc/aufs-sources-3.12.20/0000_README.bz2 /usr/src/linux-3.12.20-aufs/arch/microblaze/boot/dts/system.dts Searching all installed packages for file collisions... Press Ctrl-C to Stop None of the installed packages claim the file(s). Package 'sys-kernel/aufs-sources-3.12.20' NOT merged due to file collisions. If necessary, refer to your elog messages for the whole content of the above message. emerge --info in a separate comment since it's too large for this one
ugh, doesn't fit in a comment on its own, even.. maybe 16k is too small? https://pastebin.mozilla.org/5483829
(In reply to Dustin J. Mitchell from comment #1) > ugh, doesn't fit in a comment on its own, even.. maybe 16k is too small? > > https://pastebin.mozilla.org/5483829 Don't use external paste sites. Just attach it. (In reply to Dustin J. Mitchell from comment #0) > Detected file collision(s): > > /usr/src/linux-3.12.20-aufs/Makefile > /usr/src/linux-3.12.20-aufs/Kbuild > /usr/src/linux-3.12.20-aufs/patches.txt > /usr/src/linux-3.12.20-aufs/README > /usr/src/linux-3.12.20-aufs/Kconfig > /usr/src/linux-3.12.20-aufs/.gitignore > /usr/src/linux-3.12.20-aufs/MAINTAINERS > > ... > > /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/hweight.h > > /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/const_hweight.h > /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/builtin-ffs.h > /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/builtin-fls.h > /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/non-atomic.h > /usr/src/linux-3.12.20-aufs/include/asm-generic/bitops/arch_hweight.h > /usr/share/doc/aufs-sources-3.12.20/0000_README.bz2 > /usr/src/linux-3.12.20-aufs/arch/microblaze/boot/dts/system.dts > > Searching all installed packages for file collisions... > > Press Ctrl-C to Stop > > None of the installed packages claim the file(s). No package claims those files, so there is no file collision between packages in the tree. How those files and directories got there is something only you know. I guess you didn't understand the message after all.
The ebuild itself installed them -- something must have failed to record that correctly. Either a bug in the ebuild or in portage?
I doubt it. Also, you didn't provide a build log for either merge and you didn't post your `emerge --info' output either.
Created attachment 379834 [details] emerge --info
Well, you managed to pose an imposible challenge, since Gentoo doesn't actually keep logs of merges, and obviously I've closed my terminal session since the first merge on June 8 so it's not in scrollback. Your kindness overwhelms me.
