# emerge mailbase --oneshot Calculating dependencies ...done! >>> emerge (1 of 1) net-mail/mailbase-0.00-r8 to / >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) mailbase-0.00-r4.ebuild >>> md5 files ;-) mailbase-0.00-r5.ebuild >>> md5 files ;-) mailbase-0.00-r6.ebuild >>> md5 files ;-) mailbase-0.00-r7.ebuild >>> md5 files ;-) mailbase-0.00-r8.ebuild >>> md5 files ;-) files/common-pamd >>> md5 files ;-) files/aliases >>> md5 files ;-) files/mailcap >>> md5 files ;-) files/digest-mailbase-0.00-r4 >>> md5 files ;-) files/digest-mailbase-0.00-r5 >>> md5 files ;-) files/digest-mailbase-0.00-r6 >>> md5 files ;-) files/digest-mailbase-0.00-r7 >>> md5 files ;-) files/digest-mailbase-0.00-r8 * Checking for possible file collisions... * //etc/pam.d/pop3 exists and wasn't provided by mailbase * //etc/pam.d/imap exists and wasn't provided by mailbase * Those files listed above have to be removed in order to * install this version of mailbase. * If you edited them, remember to backup and when restoring make * sure the first line in each file is: * # Provided by mailbase (dont remove this line!) !!! ERROR: net-mail/mailbase-0.00-r8 failed. !!! Function pkg_setup, Line 50, Exitcode 0 !!! Can't be installed, files will collide !!! If you need support, post the topmost build error, NOT this status message. # qpkg -f /etc/pam.d/pop3 net-mail/courier-imap * # qpkg -f /etc/pam.d/imap net-mail/courier-imap *
Remove those files manually. If you modified them, backup them elsewhere. rm /etc/pam.d/{pop{,3},imap}
This can't be a real solution, can it? We should decide that either mailbase *or* courier-imap provides such files.
It will be fixed by the maintainer of courier-imap. Removing them is only a temporary solution.
ok, thx for your information. Thats what I want to know.
Hey, where's the maintainer of courier-imap then? The bug is still not resolved after more than a year. Please see bug #79240 as well.
