While rebuilding world .... >>> emerge (114 of 186) net-mail/mailbase-0.00-r9 to / >>> md5 files ;-) mailbase-0.00-r9.ebuild >>> md5 files ;-) mailbase-0.00-r4.ebuild >>> md5 files ;-) mailbase-0.00-r6.ebuild >>> md5 files ;-) mailbase-0.00-r8.ebuild >>> md5 files ;-) mailbase-1.ebuild >>> md5 files ;-) mailbase-0.00-r5.ebuild >>> md5 files ;-) mailbase-0.00-r7.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/common-pamd >>> 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 >>> md5 files ;-) files/digest-mailbase-0.00-r9 >>> md5 files ;-) files/common-pamd-include >>> md5 files ;-) files/mailcap >>> md5 files ;-) files/aliases >>> md5 files ;-) files/digest-mailbase-1 * 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 * //etc/pam.d/imap4 exists and wasn't provided by mailbase * //etc/pam.d/imap4s exists and wasn't provided by mailbase * //etc/pam.d/imaps 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!) Reproducible: Always Steps to Reproduce: 1. emerge mailbase 2. emerge courier-imap 3. emerge mailbase Actual Results: >>> emerge (114 of 186) net-mail/mailbase-0.00-r9 to / >>> md5 files ;-) mailbase-0.00-r9.ebuild >>> md5 files ;-) mailbase-0.00-r4.ebuild >>> md5 files ;-) mailbase-0.00-r6.ebuild >>> md5 files ;-) mailbase-0.00-r8.ebuild >>> md5 files ;-) mailbase-1.ebuild >>> md5 files ;-) mailbase-0.00-r5.ebuild >>> md5 files ;-) mailbase-0.00-r7.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/common-pamd >>> 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 >>> md5 files ;-) files/digest-mailbase-0.00-r9 >>> md5 files ;-) files/common-pamd-include >>> md5 files ;-) files/mailcap >>> md5 files ;-) files/aliases >>> md5 files ;-) files/digest-mailbase-1 * 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 * //etc/pam.d/imap4 exists and wasn't provided by mailbase * //etc/pam.d/imap4s exists and wasn't provided by mailbase * //etc/pam.d/imaps 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!) Expected Results: It should have merged fine ... Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc- 2.3.4.20041102-r1, 2.6.11-gentoo-r11 i686) ================================================================= System uname: 2.6.11-gentoo-r11 i686 AMD-K7(tm) Processor Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Jun 30 2005, 01:13:51)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-Os -march=athlon -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/ config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=athlon -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo/" MAKEOPTS="" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 7zip X509 aalib abook accounting acl acpi activefilter alsa apache2 async authdaemond authfile avi bash-completion bcmath berkdb bzip2 c++ caps cdr clamav clamd crypt ctype cups curl curlwrappers dbm dhcp doc dvdr encode erandom fam foomaticdb ftp gcj gd gdbm gif gmp gmtfull gmthigh gmtsuppl gmttria gpm gsl hardened hardenedphp iconv idea imlib innodb java jpeg lcms libclamav libg++ libwww logrotate lzw-tiff mad maildir mcal memlimit mhash mime ming mmap mmx mono msession mysql mysqli ncurses nls nptl ntlm ntlm_unsupported_patch oss pam pcntl pcre pdflib perl php pic png posix postfix python readline recode reiserfs rtc samba sasl sdl session sharedext sharedmem skey slang slp soap sockets spell spl ssl suid tcpd tiff unicode urandom usb uudeview xinetd xml2 xsl xslt zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
*** This bug has been marked as a duplicate of 94820 ***
The check has been removed for mailbase-1, you'll get collision-protect error instead if you have it enabled in FEATURES; a.k.a. too many people failed to follow trivial instructions.
Since I can't reopen the duplicate bug, I will have to reopen this one. -- OK, I am stumped. There is a bug here. I didn't put those files there, courier-imap did. So, is the issue with Courier-IMAP or with mailbase? It seems appropriate for courier-imap to put these files there, and as such, I posted this bug. Either courier-imap or mailbase need to be fixed, and it seems logical to me it is the latter.
Oh yes, for what it is worth, the reason simple instructions can not solve this problem is that it completely breaks an automated system rebuild. Consider: emerge --Deu world
Please, read the instruction, or wait for/unmask the next version. *** This bug has been marked as a duplicate of 94820 ***
CLOSED.
