Bugzilla Bug 291372

It is not possible to emerge qmail because there is a file collision
between netqmail and man-pages

 * Messages for package mail-mta/netqmail-1.05-r8:

 * 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.
 * 
 * Detected file collision(s):
 * 
 *      /usr/share/man/man3/error.3.bz2
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * sys-apps/man-pages-3.22
 *      /usr/share/man/man3/error.3.bz2
 * 
 * Package 'mail-mta/netqmail-1.05-r8' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.

For documentation;
        elog "If you are looking for documentation, check those links:"
        elog "http://www.gentoo.org/doc/en/qmail-howto.xml"
        elog "  -- qmail/vpopmail Virtual Mail Hosting System Guide"
        elog "http://www.lifewithqmail.com/"
        elog "  -- Life with qmail"
netqmail-1.06 does not include the man pages or installed documentation but
refers to the same elog as above. Included a patch to remove man and
documentation from 1.05 until 1.06 becomes stable

Created an attachment (id=208913) [details]
remove doman and dodoc

*** This bug has been marked as a duplicate of bug 137207 ***