sudo emerge -av mailbase These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] net-mail/mailbase-0.00-r8 [0.00-r6] +pam 0 kB Total size of downloads: 0 kB Do you want me to merge these packages? [Yes/No] >>> emerge (1 of 1) net-mail/mailbase-0.00-r8 to / * 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. The files belong to net-mail/courier-imap equery belongs /etc/pam.d/pop3 /etc/pam.d/imap [ Searching for file(s) /etc/pam.d/pop3,/etc/pam.d/imap in *... ] net-mail/courier-imap-4.0.1-r1 (/etc/pam.d/imap) net-mail/courier-imap-4.0.1-r1 (/etc/pam.d/pop3) How should I proceed? Reproducible: Always Steps to Reproduce: 1. 2. 3.
You can safely remove mentioned files and remerge mailbase-0.00-r8. All imap and pop3 packages, which use (and provide their own) files in /etc/pam.d/ are being changed to depend on mailbase-0.00-r8 and not to install their own versions. The rationale is that these pam.d files provided by various packages were practically identical. Feel free to comment here if you have questions to ask about this, or take it to the gentoo-user mailinglist.
I hate raining on people's parades but I wouldn't call this "FIXED". Because the current situation is that if you install/upgrade courier-imap it will replace the /etc/pam.d files and if you subsequently install/upgrade mailbase the ebuild bombs out because the files don't match the ones that it would have previously installed. Wouldn't it have been a better idea to mask the new versions of mailbase until the mail packages had been updated so as not to cause this problem?
