* Package: net-mail/mailgraph-1.14-r1 * Repository: gentoo * Maintainer: net-mail@gentoo.org * USE: elibc_glibc kernel_linux test userland_GNU vhosts x86 * FEATURES: sandbox test userpriv usersandbox >>> Unpacking source... >>> Unpacking mailgraph-1.14.tar.gz to /var/tmp/portage/net-mail/mailgraph-1.14-r1/work >>> Source unpacked in /var/tmp/portage/net-mail/mailgraph-1.14-r1/work >>> Preparing source in /var/tmp/portage/net-mail/mailgraph-1.14-r1/work/mailgraph-1.14 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/net-mail/mailgraph-1.14-r1/work/mailgraph-1.14 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/net-mail/mailgraph-1.14-r1/work/mailgraph-1.14 ... >>> Source compiled. >>> Install mailgraph-1.14-r1 into /var/tmp/portage/net-mail/mailgraph-1.14-r1/image/ category net-mail >>> Completed installing mailgraph-1.14-r1 into /var/tmp/portage/net-mail/mailgraph-1.14-r1/image/ * 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 / ` 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. * * Detected file collision(s): * * /usr/bin/mailgraph * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-mail/mailgraph-1.14 * /usr/bin/mailgraph * * Package 'net-mail/mailgraph-1.14-r1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message.