As part of an emerge world operation I've seen this on two machines: >>> md5 files ;-) files/digest-mailbase-0.00-r9 >>> md5 files ;-) files/common-pamd-include >>> md5 files ;-) files/digest-mailbase-1 * Checking for possible file collisions... * //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!) !!! ERROR: net-mail/mailbase-0.00-r9 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. dragonfly ~ # Indeed, editing the above 4 files by hand and adding the comment to line 1 fixes the problem, but for documentation sake the comment isn't true. (AFAIK) Reproducible: Always Steps to Reproduce: 1. emerge mailbase Actual Results: dragonfly ~ # emerge --update --deep --newuse mailbase Calculating dependencies ...done! >>> emerge (1 of 1) net-mail/mailbase-0.00-r9 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 ;-) mailbase-0.00-r9.ebuild >>> md5 files ;-) mailbase-1.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 >>> md5 files ;-) files/digest-mailbase-0.00-r9 >>> md5 files ;-) files/common-pamd-include >>> md5 files ;-) files/digest-mailbase-1 * Checking for possible file collisions... * //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!) !!! ERROR: net-mail/mailbase-0.00-r9 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. dragonfly ~ # Expected Results: emerge cleanly or tell me there's something blocking. dragonfly ~ # emerge info 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-r6 i686) ================================================================= System uname: 2.6.11-gentoo-r6 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 7 2005, 04:19:12)] 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="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo.ccccom.com http://gentoo.osuosl.org/ http://gentoo.seren.com/gentoo ftp://gentoo.mirrors.tds.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apache2 audiofile avi berkdb bitmap-fonts caps cdr crypt cups curl dvd dvdr dvdread eds emboss encode esd fam firebird flac fluidsynth foomaticdb fortran gd gdbm gif gimp gimpprint gnome gpm gstreamer gtk gtk2 i8x0 imagemagick imlib ipv6 jack jack-tmpfs java jpeg kde ladcca ladspa libg++ libwww lirc mad mikmod mjpeg mmx motif mozcalendar mozilla mp3 mpeg mysql mythtv ncurses nls nptl nptlonly ogg oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline samba sdl sndfile spell sse sse2 ssl svga tcltk tcpd threads tiff transcode truetype truetype-fonts type1-fonts usb v4l v4l2 vorbis xine xml2 xmms xscreensaver xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY dragonfly ~ #
>Expected Results: >emerge cleanly or tell me there's something blocking. Sigh. The instructions don
>Expected Results: >emerge cleanly or tell me there's something blocking. Sigh. The instructions don´t tell you what you should do? Or what is the problem here, except for the fact that bug is duplicate of at least another 10 invalid bugs?
The check is now removed, have fun if you face collision-protect problems. Cheers, Ferdy
*** Bug 97550 has been marked as a duplicate of this bug. ***
