The obvious issues aside, I'm quite surprised the file collision didn't show up earlier: lrwxrwxrwx 1 root root 58 5. Aug 2005 /usr/lib/mono/2.0/nunit.util.dll -> ../gac/nunit.util/2.2.0.0__96d09a1eb7f44a77/nunit.util.dll Fri Aug 5 14:07:20 2005 >>> dev-lang/mono-1.1.8.3 merge time: 43 minutes and 1 second. Don't know, if you want to do anything about it. Didn't bother to check, if the old ebuild is to blame. Likely it's the old Portage_doesn't_deal_properly_with_symlinks issue. ;) --- * QA Notice: The following files contain executable stacks * Files with executable stacks will not work properly (or at all!) * on some architectures/operating systems. A bug should be filed * at http://bugs.gentoo.org/ to make sure the file is fixed. * For more information, see http://hardened.gentoo.org/gnu-stack.xml * Please include this file in your report: * /var/tmp/portage/dev-lang/mono-1.9.1/temp/scanelf-execstack.log * RWX --- --- usr/bin/mono RWX --- --- usr/lib/libmono.so.0.0.0 removing executable bit: usr/lib/libikvm-native.la removing executable bit: usr/lib/libmono.la removing executable bit: usr/lib/libMonoPosixHelper.la removing executable bit: usr/lib/libmono-profiler-aot.la removing executable bit: usr/lib/libmono-profiler-cov.la removing executable bit: usr/lib/libMonoSupportW.la * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * loader.c:1522: warning: implicit declaration of function ‘mono_profiler_method_free’ * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: http://www.go-mono.com * checking 816 files for package collisions * 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). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * package dev-lang/mono-1.9.1 NOT merged * * Detected file collision(s): * * /usr/lib/mono/2.0/nunit.util.dll * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s).
I did not encounter this with mono-2.0.1
